I think your trying to link the dates of one schedule to another, perhaps you want to copy it and do some mathematical calculation or transformation on the said dates. In P3 we can only have the customs data variable for users defined variable the rest are static variable which is internally defined by the program but we can access it but no change it value.
For custom data item we can copy it global change or by using the target schedule update in that way you can link two diffrent file provided they have identical Activity ID and from there you can do glabal changes for your custom date.
Th @tmp variable data can be use for global change and will reset when you each time you store data to it . But usually in P3 you do single step calculation at a time so by the time you reset @TMP variable you have already use the former value for another calculation. @TMP works as a temporary storage of data be it numeric, precision, Date, etc.
Member for
18 years 11 monthsRE: Global variables
I think your trying to link the dates of one schedule to another, perhaps you want to copy it and do some mathematical calculation or transformation on the said dates. In P3 we can only have the customs data variable for users defined variable the rest are static variable which is internally defined by the program but we can access it but no change it value.
For custom data item we can copy it global change or by using the target schedule update in that way you can link two diffrent file provided they have identical Activity ID and from there you can do glabal changes for your custom date.
Th @tmp variable data can be use for global change and will reset when you each time you store data to it . But usually in P3 you do single step calculation at a time so by the time you reset @TMP variable you have already use the former value for another calculation. @TMP works as a temporary storage of data be it numeric, precision, Date, etc.
Hope i made sense.
Regards