Map evolving to a table

(0) Share

Report

Posted on by Kenny Saelen

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

I have the same question (0)

All responses (3)

Answers (0)

Community Member on at

Like (0)

Report

RE: Map evolving to a table

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.

Was this reply helpful? Yes No
Suggested answer

Kenny Saelen on at

Like (2)

Report

RE: Map evolving to a table

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.

Was this reply helpful? Yes No
Suggested answer

Logger 60 on at

Like (0)

Report

Map evolving to a table

The solution to prevent such corruption :

https://github.com/KozlovPavel677/AxTableTypeChangeFix

Some additional simple fix to correct corrupted map/view :

https://axforum.info/forums/showthread.php?p=426156#post426156

This scripts accounts for layer of table.

Was this reply helpful? Yes No