-
Notifications
You must be signed in to change notification settings - Fork 69
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
Early-bound "Responses" for messages have incorrect capitalization of attributes #519
Comments
Are all actions getting generated this way for you? Can you generate your metadata and submit that so I can see what's going on? |
I'm a bit concerned sharing the whole metadata for this organization, as it's not "mine". I can, however, pick the custom action definition from the metadata, which is all that should be relevant. I've tested this operation with another custom action I've just created and it's like before. For a moment I thought this may have something to do with Metadata minimized to sample action:
Resulting early bound cs file:
|
Tool and Version
EarlyBoundGenerator V 2.2024.9.11
Describe the bug
Using Early Bound Generator V2 for custom messages produces incorrect attribute names in between getter / setter.
See following auto-generated code for a custom action response class:
The
get
portion of theResultCustomerAssetType
is referencing field nameresultCustomerAssetType
(correct), while theget
portion is referencing the fieldResultCustomerAssetType
(incorrect - will never be set).Obviously these field strings need to match the actual parameters of the action in CRM in terms of capitalization (in this case the property in Dynamics starts with a lowercase).
To Reproduce
Generate early bounds for a custom action.
Expected behavior
Field getters and setters should use the same field name string.
The text was updated successfully, but these errors were encountered: