Replies: 1 comment 1 reply
-
Agree @bwmodular . Got many people asking the same question.... |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I was caught out by something earlier today and thought it might be useful to discuss ways to help other users avoid the same trap.
I added a test to an existing project which so far had only used the Core FakeXrmEasy packages.
My new tests were testing some code which shares a record with a user.
The test threw this exception:
The organization request type 'Microsoft.Crm.Sdk.Messages.GrantAccessRequest' is not yet supported...etc.
but I knew that this was already supported in Version1, so I was confused.
I worked out quite quickly that this was because I hadn't included FakeXrmEasy.Messages (and pointed to this with the AddFakeMessageExecutors directive in my FakeXrmEasyTestsBase) and was able to resolve it and get the tests running.
I know that the CommercialUnsupportedException exception message is already quite long, but it might be worth adding some additional text to say 'Have you included FakeXrmEasy.Messages' in your project. Otherwise users who are new to FXE might genuinely think that this is not implemented in v2/3 and think that the framework is far less capable than it is....
Beta Was this translation helpful? Give feedback.
All reactions