Dynamics AX Blog - Posts from September 2016
These posts are machine-translated.
Currently, only posts from »September 2016« are displayed 
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
Dynamics AX Blog - Posts from September 2016These posts are machine-translated. Currently, only posts from »September 2016« are displayed
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The fact that display methods should be cached, when they are used in forms, is well-known. For this, a corresponding call should always be integrated into the init() method of a form datasource:
public void init() { super(); this.cacheAddMethod(tableMethodStr(DirPartyPostalAddressView,locationRoles)); }The fact that you can save this call in Dynamics AX 2012, if you set a corresponding attribute in the display method itself, was new to me: