Unable to delete AOT objects from USR layer

(0) Share

Report

Posted on by Community Member

There are many USR objects on Classes in our AOT that we did not create and we cannot delete them. They appear to have been created when we loaded our Model database into the environment back in March. We just noticed it this week when we tried to import a USR class and could not.

When we compare the layers on the objects (SYS & USR) they are identical. We try to delete and receive no error, but the USR reappears each time. Looks like only Classes are affected.

More Info:

1) I can edit Classes that have no USR layer and create a USR layer object. It allows me to edit the Class and save without an error. It can then be deleted like normal.

2) Source Control is not enabled.

AX is acting like there's a flag set that says "don't allow objects to be edited in the USR layer for Classes".

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (0)

Denis Macchinetti 16,444 on at

Like (0)

Report

Hi Michael

I suggest you to apply the last kernel according to the your AX version.

blogs.msdn.com/.../overview-of-ax-build-numbers.aspx

In the past, I faced an similar issue with the Form Datasource node.

I have fixed with the Cumulative Update 7 of AX 2012 R2.

Was this reply helpful? Yes No
André Arnaud de Cal... 300,982 Super User 2025 Season 2 on at

Like (2)

Report

Hi Michael,

Sometimes the compiler or another part of the development environment creates objects in the usr layer. This should be fixed in CU7 for AX 2012 R2, but even today we have seen these objects.

The only way to remove them is to delete the usr model with help of e.g. axutil. If you have objects in the usr layer that should remain, you can create a new model in the usr layer and move those objects to the new model. You can also move the unwanted usr objects in a separate model and remove them.

Was this reply helpful? Yes No
Brandon Ahmad 2,465 User Group Leader on at

Like (0)

Report

form datasources also show this behavior. However, deleting did work for me so that I could compile.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Denis - Upgrading to the latest version is not an option for us at this time.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Andre - I tried your suggestion and moved the objects to a new model and deleted the model. It did not work. The objects came back after a data sync/compile.

I have created an incident with MS. They are looking into it. One thing they noticed is the issue follows the model store. They exported it and imported it into Contos and saw the same issue. I am considering loading the model store from my development environment. All the IDs are the same. I will see what MS comes up with 1st.

Was this reply helpful? Yes No
Denis Macchinetti 16,444 on at

Like (0)

Report

Hi Michael

You should apply only the last Kernel ( on all AX Components).

The Kernel hotfix doesn't change the Business Logic but only binary and executable files.

Microsoft for sure will ask you to apply the last Kernel Hotfix.

You can find at the link below.

blogs.msdn.com/.../overview-of-ax-build-numbers.aspx

Was this reply helpful? Yes No
rrizwann 675 on at

Like (0)

Report

HI Michael and Denis

I am facing same issue on my custom workflow I cannot delete ,edit and click this workflow and wanted to delete from AOT can you please tell me work around?

I am using AX 2012 R2 CU7.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

We are experiencing this same thing on 2012 R3 Cu13. Can someone tell me what they had to do to fix this issue?

Was this reply helpful? Yes No