We had extended in the past LedgerPostingType (some PAC*, and some TS*) with several custom enum values, From 10.0.45, Microsoft add a couple of new values, exceeding the 255 limit. This caused issues with Management Reporter. Microsoft addressed the issue by enabling the flight DbSyncEnable32bitEnumCreation, which resolved the problem.
We have removed our custom enum values from the extension right now. But now we have a new problem on a Ledger reports > An exception of type MetadataException has occurred while performing the operation.
Checking DB, out or old enum values are still present in EnumValueTable.
We don't open right now a support ticket, we can do of cours, meanwhile we try in DEV enviroment to delete old values and sync data and the problem has been resolved.
But checking the table after sync, our values, leave the gap on sequence, and this is good, but the standard values over 255 are reassigned to lower values. We don't have transaction on that values.
Has anyone experienced similar issues with LedgerPostingType. Is there a safe or recommended approach to clean up obsolete enum values, after moving past the 255 limit and enabling 32-bit enums?
Sorry if not so clear, but if any one experience this know what i talking about.
Diego
