Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EBGv2: OptionSetValues names is getting null #528

Open
rappen opened this issue Nov 21, 2024 · 1 comment
Open

EBGv2: OptionSetValues names is getting null #528

rappen opened this issue Nov 21, 2024 · 1 comment

Comments

@rappen
Copy link
Contributor

rappen commented Nov 21, 2024

After running the latest version, it appears that some Choices have been changed (which they are not, not even included in our unmanaged solution), and the names are being lost to null instead.

See changes here:
image

Snippet from the Default solution:
image

Ex 2:
image
image

Sorry, this environment has Swedish by default...
Sorry 2, I guess this should not blame the EBGv2, but I found the issues only through the result of the generated files.

Do you have any clues?


  • Deployment: Online
  • DB Version: 9.2.24103.216
  • Connection Controls Version: 1.2024.9.59
  • XrmToolBox Version: 1.2024.9.69
  • Tool Version: 2.2024.11.8
@daryllabar
Copy link
Owner

That's weird. The only change I made to the latest version was to allow for a backdoor approach to control nullables. The first example you show does not much because the int value doesn't match, so I think you're looking at the wrong option set.

Regardless the truth would be in the generated meta data. Update the tool to just generate the entity/option set that is causing you grief, and then configure the meta data to be serialized and see what it shows there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants