The enum that is specified in the input XML file does not exist in Microsoft Dynamics AX.

The enum that is specified in the input XML file does not exist in Microsoft Dynamics AX.

This question is answered

Hi,

In one of our ax2012 systems, I get the following error when trying to generate proxies.

The enum that is specified in the input XML file does not exist in Microsoft Dynamics AX.

This error is a CLRError which is thrown from 

generationResult = pg.GenerateProxies(tables.get_Keys(), classes.get_Keys(), enums.get_Keys(), #ProxiesNamespace, dir, language); in SysDevelopmentProxy\generateProxies

You also get the error if trying to compile a proxy vs project from Visual Studio.

Unfortunately this error contains no useful information, which makes it very hard to track. I'm not sure what this error is related to.

If anyone has seen this idea, or has any ideas, your thoughts would be most appreciative.

 

Regards

Tim

 

 

 

Verified Answer
  • The error is brought about by having an enum field on a table that extends an enum which does not exist on the AOT.  You will have to check all new fields you have added and check their proprety and make sure that if extending an enum that it exists.

    Hope this helpd, it fixed our problem and was able to install EP

    Tony

  • Hi Tony, LJ,

    We Opened the proxy project in Visual Studio and deleted objects to find out which was the effected object. (When you remove an object you must restart the AOS, otherwise it gets confused). Then look at object you found to be the culprit, and check the each enum exists in the object. This error should only occur for table fields with a missing enum on a field, in other cases when you have a missing enum, you should get a compilation error.

    Tim

All Replies
  • Hi Tim,

    I share your frustration, I am getting this while trying to deploy EP. In my situation it is being generated by the SysEPDeployment class.

    I have also noticed that my event log complains about the .NET BC not being found. Having the BC install or not does not change the outcome.

    Just curious, have you found a solution yet?

    Regards,

    LJ

  • Hi LJ

    I had the some problem in that not being able to install the EP, I deleted the VAR Model and then I was able to install the EP.

    I am still investigating why the error comes up when I import the VAR model again -

    Tony

  • The error is brought about by having an enum field on a table that extends an enum which does not exist on the AOT.  You will have to check all new fields you have added and check their proprety and make sure that if extending an enum that it exists.

    Hope this helpd, it fixed our problem and was able to install EP

    Tony

  • Hi Tony, LJ,

    We Opened the proxy project in Visual Studio and deleted objects to find out which was the effected object. (When you remove an object you must restart the AOS, otherwise it gets confused). Then look at object you found to be the culprit, and check the each enum exists in the object. This error should only occur for table fields with a missing enum on a field, in other cases when you have a missing enum, you should get a compilation error.

    Tim