OPALE - 10.0 - Utilisation - MAPPING TRACEDATA/en
Différence entre versions
De MappingDoc
(Page créée avec « Level 1 of DB.MAPPING_TRACEDATA shows us the values of the fields once they were assigned. ») |
(Page créée avec « Level 2 shows us the values of the fields when they are accessed. This allows you to have more detailed calculations for instance. ») |
||
| Ligne 7 : | Ligne 7 : | ||
Level 1 of DB.MAPPING_TRACEDATA shows us the values of the fields once they were assigned. | Level 1 of DB.MAPPING_TRACEDATA shows us the values of the fields once they were assigned. | ||
| − | + | Level 2 shows us the values of the fields when they are accessed. This allows you to have more detailed calculations for instance. | |
Exemple : | Exemple : | ||
Version du 3 juin 2019 à 09:14
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 were assigned.
Level 2 shows us the values of the fields when they are accessed. This allows you to have more detailed calculations for instance.
Exemple :
Le calcul suivant nous donne :
DB.entier3 = $DB.entier1 -$DB.entier2
Au niveau 1 : DATA : .DB(entier3)=12
Au niveau 2 :
DATA : .DB(entier3)=(null)
DATA : .DB(entier1)=15
DATA : .DB(entier2)=3
DATA : .DB(entier3)=12
