Enum value sync issue

(1) Share

Report

Posted on by Suren_G

252

Hi All,

We are facing an issue with Enum value sync in DB.

Scenario :

We created a new enum, ex., TestEnum with elements as below and deployed to the Tier 2 environment.

Enum value	Name
0	B
1	C
2	D

Later, we added a new element and changed the enum value as below and deployed again to the Tier 2 environment.

Enum value	Name
0	A
1	B
2	C
3	D

But the enum values in the standard - 'EnumValueTable' is not getting changed unless we manually delete the data for the particular EnumId and resync the data.

As we don't have provision to backend in Tier 2 environment, we are not able to proceed with this workaround.

Could someone please suggest your inputs on this issue!

Thanks!

I have the same question (0)

All responses (5)

Answers (0)

Waed Ayyad 9,039 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

Did you update the already-existing records, as some records will have wrong values?

Was this reply helpful? Yes No
Suren_G 252 on at

Like (0)

Report

Hi Waed,

Yes, we updated the exiting element name in the enum and added a new element. But the updated values are not syncing to the 'EnumValueTable' and it causes mismatches between UI and DB.

Thanks!

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

Like (0)

Report

Hi Suren,

In case you have an enumeration with predefined values, I wonder why you renumbered the values. Why didn't you add A with enum value 3? You can then still manage the order for the user starting with an A. In that case, you don't have this type of issue.

Was this reply helpful? Yes No
Kevin Xia Microsoft Employee on at

Like (0)

Report

Hi,

In this case, I agree with Andre's approach. At present, I don't know why this problem arises or how to solve it, so we can avoid this problem in another way. You can choose to add a new record instead of modifying it and re-editing it to meet your needs.

Best regards,

Kevin

Was this reply helpful? Yes No
Martin Dráb 237,880 Most Valuable Professional on at

Like (1)

Report

I've moved this thread from Dynamics AX forum, because several things suggest it's actually about F&O.

It seems you created a non-extensible enum and then you manually changed the meaning of value 2 from TestEnum::D to TestEnum::C. Then it's you who "caused mismatches between UI and DB".

Was this reply helpful? Yes No