This post is machine-translated. The original post in german language can be found here.
These post applies to following version:
Dynamics AX 2012
Dynamics AX 2012
|
|
|
|
|
|
This post is machine-translated. The original post in german language can be found here.
These post applies to following version:
Dynamics AX 2012
|
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:
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:
This has the advantage that, no matter on how many forms the display method is used, I do not have to worry about the caching there anymore.
Additionally, there is the property CacheDataMethod avaiable for form controls, which also can be used to activate caching. I prefer the variant using the attribute.