OPALE - 10.0 - Utilisation - MAPPING TRACEDATA/en
Différence entre versions
De MappingDoc
(Page créée avec « The following calculation gives us: ») |
|||
| Ligne 5 : | Ligne 5 : | ||
Format: LIB.FILE(FIELD)=VALUE | Format: LIB.FILE(FIELD)=VALUE | ||
| − | Level 1 of DB.MAPPING_TRACEDATA shows us the values of the fields once they | + | Level 1 of DB.MAPPING_TRACEDATA shows us the values of the fields once they have been assigned. |
Level 2 shows us the values of the fields when they are accessed. This allows you to have more detailed calculations for instance. | Level 2 shows us the values of the fields when they are accessed. This allows you to have more detailed calculations for instance. | ||
Version du 3 juin 2019 à 09:18
The MAPPING_TRACEDATA parameter recovers changes made to the fields.
MAPPING_TRACEDATA=1 recovers field changes
Format: LIB.FILE(FIELD)=VALUE
Level 1 of DB.MAPPING_TRACEDATA shows us the values of the fields once they have been assigned.
Level 2 shows us the values of the fields when they are accessed. This allows you to have more detailed calculations for instance.
Example:
The following calculation gives us:
DB.entier3 = $DB.entier1 -$DB.entier2
At level 1: DATA : .DB(entier3)=12
At level 2:
DATA : .DB(entier3)=(null)
DATA : .DB(entier1)=15
DATA : .DB(entier2)=3
DATA : .DB(entier3)=12
