Dynamics AX Blog - Posts from Oktober 2012
These posts are machine-translated.
Currently, only posts from »Oktober 2012« are displayed 
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
Dynamics AX Blog - Posts from Oktober 2012These posts are machine-translated. Currently, only posts from »Oktober 2012« are displayed
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
If you include the SysOperationInitializable class in a data contract using the implements command, the method initialize() gets available and can be overwritten.
This method can be used to initialize variables within the data contract. However, this method is only called as long as no usage data is found or it is not activated.
class TutorialSysOperationDataContract
implements SysOperationInitializable
{
date dialogDate;
}
public TransDate parmDialogDate(TransDate _dialogDate = dialogDate)
{
dialogDate = _dialogDate;
return dialogDate;
}
{
dialogDate = systemDateGet() - 365;
}