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

RetrieveOptionSetRequest doesn't support retrieving option sets by MetadataId #111

Open
jordimontana82 opened this issue Sep 13, 2023 · 2 comments
Labels
enhancement New feature or request scope-messages

Comments

@jordimontana82 jordimontana82 added enhancement New feature or request scope-messages labels Sep 13, 2023
@KimBon
Copy link

KimBon commented Apr 4, 2024

@jordimontana82 we would like to unit test a method that uses RetrieveAttributeRequest, which seems a similar question like this. How would that be handled? This RetrieveOptionSetRequest seems to be for global optionsets only.

@jordimontana82
Copy link
Contributor Author

@KimBon that should work, here is a sample unit test for it:

https://github.com/DynamicsValue/fake-xrm-easy-messages/blob/c1f06f7f6257414d16ff5679af70b6943f62d544/tests/FakeXrmEasy.Messages.Tests/FakeMessageExecutors/RetrieveOptionSetRequestTests/RetrieveOptionSetRequestTests.cs#L10

You need to install the messages.

This issue I raised was wether Metadata might be referenced via a Guid (MetadataId) as opposed to the logical name, which is mostly for internal use in the framework. If you can use the logical name, then is not really an issue.

Here's some background info on metadata as well: https://dynamicsvalue.github.io/fake-xrm-easy-docs/quickstart/advanced/metadata/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request scope-messages
Projects
Status: To do
Development

No branches or pull requests

2 participants