web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

After full compile, can't delete CUS layer from object

(0) ShareShare
ReportReport
Posted on by 3,155

After doing a full compile in AX 2012 R2 CU6, I have a few objects that have suddenly appeared with CUS layer modifications.

When I try and hit 'Delete', the 'bold' of the object disappears briefly, and the reappears.  The layer wasn't deleted.

I tried moving it to a 'TEST' model and then deleting the model via axutil.  Didn't work.

I have installed the latest kernel update.  Did  not fix it.

I can't seem to get these objects to delete.  This appears to have started when I turned on / started using TFS in the environment.  Other environments (PROD and NON-PROD) that don't use TFS, seem to be fine.

*This post is locked for comments

I have the same question (0)
  • Brandon Ahmad Profile Picture
    2,465 User Group Leader on at
    RE: After full compile, can't delete CUS layer from object

    [quote user="bRradlyJames"]

    After doing a full compile in AX 2012 R2 CU6, I have a few objects that have suddenly appeared with CUS layer modifications.

    When I try and hit 'Delete', the 'bold' of the object disappears briefly, and the reappears.  The layer wasn't deleted.

    I tried moving it to a 'TEST' model and then deleting the model via axutil.  Didn't work.

    I have installed the latest kernel update.  Did  not fix it.

    I can't seem to get these objects to delete.  This appears to have started when I turned on / started using TFS in the environment.  Other environments (PROD and NON-PROD) that don't use TFS, seem to be fine.

    [/quote]

    I feel your pain and believe it or not, this makes a lot of sense -- not for the right reasons.  However, after having walked into over 40 something implementations, you see this thing quite often.   Now, for the next part..  So, I mentioned that hotfixes have dependencies as well as TFS.  Hopefully, I can save you a lot of time before you go through what most of us went through when we first brought TFS to an AX implementation in that dependencies are sometimes missing from certain elements and those dependencies don't merge correctly  

    The quickest way to fix this is to take the problematic root element which you've now traced to something in HCMWorker.  Then, try to export your model from TFS and compile it.  The stuff it complains about -- the parts of the form, are the stuff that you need to bring down to the cus layer and add to version control.  That will fix it if it is a version control issue.  

    I got a script I can post for compiling the model and running this test but I won't have access to it until I get home this weekend.  I'll post it then if it is still a headache.  

    If it isn't TFS though, say a hotfix from Microsoft or some Var, that's a little different but still similar.  Usually, it means that you are missing other code from another dependent hotfix (in the case of Microsoft) or that someone messed up an upgrade (classic with many var packages).  

  • b_radlyjames Profile Picture
    3,155 on at
    RE: After full compile, can't delete CUS layer from object

    Brandon,

    Appears you are right.  I've narrowed it down to Tables: HcmWorker, LogisticsElectronicAddress, LogisticsPostalAddress, ContactPerson, and DirPersonName.

    I think it's HcmWorker.  The new errors that show up (all in forms), appear to be related to 'Worker' in some form or another.

  • Suggested answer
    Brandon Ahmad Profile Picture
    2,465 User Group Leader on at
    RE: After full compile, can't delete CUS layer from object

    This is actually pretty common. It often has to do with element dependencies -- sometimes customized and at other times in hotfixes.

    Move the relevant objects into a model. Export it. Try the axutil Del layer command. Import the model back in. That usually fixes it.

  • b_radlyjames Profile Picture
    3,155 on at
    RE: After full compile, can't delete CUS layer from object

    An update to this craziness:

    TFS may not be the culprit.  In order to get around this, I exported the Shared Project XPOs from my TFS 'Merged' environment and imported them into an environment that was refreshed from PRODUCTION a few days ago.  So compiling was fine.  After importing the XPOs, the 6 phantom (forms) showed up as compile errors.

    Looks like something I checked into TFS may be causing this issue.

    I will be importing XPOs one at a time and then compiling after each one.  Hopefully this will narrow down which one is, potentially, causing the issue.

  • b_radlyjames Profile Picture
    3,155 on at
    RE: After full compile, can't delete CUS layer from object

    I have determined that this has something to do with using TFS in R2 CU6.

    I restored the model store from my PROD environment and everything compiled just fine. Once I turned on TFS and did some 'Synchronize' on the 'CUS model', did a full compile, and now 4 objects (Forms) have spit out.  They are different than the objects I got when I did this before.

    Will keep on looking...

  • b_radlyjames Profile Picture
    3,155 on at
    RE: After full compile, can't delete CUS layer from object

    Vilmos,

    I am on CU6.  Although similar issue, mine are in the CUS layer.  These suggestions don't work.

  • Vilmos Kintera Profile Picture
    46,149 on at
    RE: After full compile, can't delete CUS layer from object

    See if the root cause mentioned in the topic is applicable for you, also there are some suggestions around that.

  • b_radlyjames Profile Picture
    3,155 on at
    RE: After full compile, can't delete CUS layer from object

    Vilmos,

    Thanks for the reply.  I am on CU6 so I don't use axbuild.  

  • Suggested answer
    Vilmos Kintera Profile Picture
    46,149 on at
    RE: After full compile, can't delete CUS layer from object

    This is a known issue, have a look at this topic. It was supposedly improved from CU7 application patch and kernel hotfix.

    community.dynamics.com/.../117935

    Sometimes axbuild creates these ghost objects, only way to remove them is by uninstall-axmodel, then doing a regular compile on the problematic objects and their parents within the AX client.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Community Member Profile Picture

Community Member 4

#2
Guy Terry Profile Picture

Guy Terry 2 Moderator

#2
Nayyar Siddiqi Profile Picture

Nayyar Siddiqi 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans