1,531
Hi Friends,
After I applied CU13 for AX2012, I compile it, got errors most like 'variable not declared', 'marco doesn't exist', or 'The wrong number of arguments has been specified for the method'.
I have looked the code, those errors are merited, but, I just can't imagine it's the real problem from CU13.
Anybody has same problem?
*This post is locked for comments
Hi Nikolaos,
Thanks for your response, I want to follow up with a question when merging code, we have vendor's code in VAR layer, our own code in CUS layer, we need to make change in VAR code for CU13, vendor is not going to help us on this since contract is long over, should I move the change to CUS layer as best practice?
The problem is that you haven't merged the new SYP code into your customization layer. You must do that for all objects that exist on SYP and your customization layer (var, cus, usr).
When you customize a standard method, the method is copied to your customization layer. Now if Microsoft changes it on SYP layer (and you get it with the CU package), the change is not visible since your customization layer version overlayers it. Now, if any other method is trying to use a variable that is hidden in such way, it will obviously cause a compiler error.
So you must compare syp vs your customization layer and merge all such changes to the highest layer. This is a crucial part of any CU update.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,269
Super User 2024 Season 2
#2
Martin Dráb
230,198
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
