Announcements
Ik have a standard R3 with no hotfixes. From there on we started cutomizations.
This morning a did a full compile using the AXBuild tool and no errors were reported. Then the CIL compile also finished with no errors, but when confirming a purchase order, stack traces occured on the FormLetterService class.
When manually compiling the service class, it seems that there are indeed X++ errors... and more specifically table assignments that fail. After a while I noticed that the FormLetterParmTable map (SYS) was missing in my environment. Taking a look at the Tables node in the AOT learned that apparently the map 'thinks' it is a table because I suddenly see it amongst the tables.
Any idea how this can happen?? (And for the record, I often suspect the AXBuild tool might be the culprit...)
*This post is locked for comments
Meanwhile I solved the issue by updating the ModelElementData table. I went ahead and fetched the Properties field value from a valid environment. Then I update ModelElementData with the correct Properties hex string and restarted the AOS, solved the issue.
Hi,
There was a similar thread recently: Error during data dictionary synchronization: Table mistaken for View. Looks like a bug in the management util or SQL stored procedures responsible for modelstore.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 290,802 Super User 2024 Season 2
Martin Dráb 229,133 Most Valuable Professional
nmaenpaa 101,154