Jordi

Currently the microsoft.* , system.* and runtime.* packages consume about 920 MB of hard disk space. This is multipled by each fake-xrm-easy* repository. By moving it one level up in...

AddMembersTeamRequestExecutor should validate the OOB limitation about Default Teams of Business Units: ErrorCodes.CannotAddMembersToDefaultTeam

1

This about implementing the above validation (CannotAddMembersToDefaultTeam) for that message. More background info on this great thread (which could be possibly included into the error message details). https://d365demystified.com/2018/12/06/d365-quick-tip-cant-add-members-to-the-default-business-unit-team/

RetrieveCurrentOrganisationRequest is missing

4

Add implementation for the above organisation request, that allows to retrieve information about the organisation you're currently connected to. https://learn.microsoft.com/en-us/dotnet/api/microsoft.crm.sdk.messages.retrievecurrentorganizationrequest?view=dataverse-sdk-latest

Update github actions to allow forks run their own analysis in their own sonar cloud account (free for OSS)

21

This is about updating GitHub actions to use repository_owner as opposed to the hardcoded DynamicsValue username. This would allow anyone to build their fork against their own SonarCloud account (which...

This issue was raised to provide mocks for the ServiceClient class, however, a much neater and simpler solution would be that the ServiceClient constructor could take an IOrganizationService interface, similar...

While FakeXrmEasy supports passing in SharedVariables in ExecutePlugin** methods via your own XrmFakedPluginContext instances, the current implementation of pipeline simulation ignore SharedVariables that could be passed between plugins. Some background...

Currently it throws a TypeAccessException as the new repository has not been added to the context by the time automatic registration begins.

https://learn.microsoft.com/en-us/dotnet/api/microsoft.crm.sdk.messages.targetfieldtype?view=dataverse-sdk-latest The other options allowed are based on field metadata, so that only fields that are valid for create, read or update are initialized. To implement the other field types...

https://learn.microsoft.com/en-us/power-apps/developer/data-platform/use-open-types?tabs=sdk

It would be good having a way of automatically creating entity records with prepopulated dummy data. This would speed up the test data needed for some tests. One idea is...