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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / New ENUM element added...
Microsoft Dynamics AX (Archived)

New ENUM element added to Base Enum InventAccountTypeInvent is disabled

(0) ShareShare
ReportReport
Posted on by Retha 1,457

I have added a new enum element to InventAccountTypeInvent, called DeadstockAdjustment (Label Deadstock adjustment).

I also added it to Base Enums LedgerPostingType and InventAccounType and have changed the methods on table InventPosting that references these base enums.

I stepped through the INIT method of form InventPosting as well but nowhere can I find the reason why my new enum element is greyed out. See below. This radiobutton control just taste that the Enum Type is InventAccountTypeInvent with no special methods. So it should show my element as enabled same as the others. Any help on why this is happening and how to correct it, is much appreciated.

*This post is locked for comments

I have the same question (0)
  • Ajit Profile Picture
    Ajit 8,755 on at

    We can't see the uploaded screen shot by you. Please use rich formatting and upload image again.

  • Retha Profile Picture
    Retha 1,457 on at

    As you can see in this screenshot the element I added to the base enum is greyed out. Do I miss some more setup for it before it will be enabled ?

  • Retha Profile Picture
    Retha 1,457 on at

  • Retha Profile Picture
    Retha 1,457 on at

    The screenshot doesn't want to show even if I choose rich format. Anyways it is just a screenshot of the form in Inventory Management -> Setup -> Posting -> Posting and the Inventory tab

  • Verified answer
    Ajit Profile Picture
    Ajit 8,755 on at

    I just tested for you and it worked fine for me. I just added enum element. Please review the element properties, are you using conutryRegionCode there?

    5226.Enum.jpg

  • Retha Profile Picture
    Retha 1,457 on at

    Hi Ajit

    I just deleted my element and re-added it. We do not have country region codes. I fill in the Name, label and it defaults the enumValue to 102. That's it and it still greys out my element.

    I see you have the Rounding-Loss and Rounding-Profit greyed out. Mine is not greyed out. It is elements for the Russian country region. We did not turn on the Russian specific codes.

    I checked under System Administration -> Setup -> Licensing -> License configuration and under the Country/regional specific features the only check boxes ticked off are Multiple countries/regions and United States. So the Russian elements should be enabled. They have codes 100 and 101. 

    I have before changed the enum value for my element to less than 100 to be before the Russian elements but it was still disabled afterwards. Do you think it is these Russian code logic that I my problem? I read somewhere there is a way to disable them. Yours are disabled. I'll search for that post and apply the suggestion and see if that will help. Because I'm at a loss here, why does it work when you add it but it doesn't when I add it.

  • Retha Profile Picture
    Retha 1,457 on at

    I mean the Russian elements should be disabled.

  • Retha Profile Picture
    Retha 1,457 on at

    You won't believe it Ajit. I applied this: community.dynamics.com/.../171773 and the 2 Russian elements are now greyed out and my element is enabled. What does catch weight have anything to do with my new element?

  • Ajit Profile Picture
    Ajit 8,755 on at

    That's weird

  • Verified answer
    Retha Profile Picture
    Retha 1,457 on at

    That is weird. I showed it to my boss and she thought I should add the same configuration key that is on base enum InventAccountType to InventAccountTypeInvent and see that doesn't fix it. I unchecked the Catch Weight, synchronized the DB and added the configuration key LogisticsBasic to the base enum properties as she suggested. It went back to disabling my element and enabling the Russian elements.

    Out of frustration I decided to use <Alt>+ <ArrowUp> to move my element above the 2 Russian elements and volla, now my element is enabled as well. We will not turn on the Catch Weight configuration feature in case it brakes something else. The 2 Russian elements can stay enabled, it errors out anyways if one try to check the radio button.  Microsoft has a weird bug here on AX 2012 R3 cu12 (our version). Thanks for your help.

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…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans