The current implementation (with App ID + App Secret) to connect to environments where MFA is enabled assumes we can easily get App ID and Secrets.
In highly secured environments, we have situations where these App ID and Secrets are created for specific reasons, for specific usages and cannot be shared by multiple users (e.g. devs + XRMToolkit). It would be helpful to have the ability to pop-up the SDK control for authentication so developers can use their own credentials to login with MFA (XRM Toolbox does this)3 votes
The description was changed to remove the ‘with SDK Control’. The connection dialog and connection logic is being completely re-written in the next major version to be able to support all the current connection scenarios with D365. That being said, you should be able to handle all scenarios currently by using the ‘Connection String’ option. This is not ideal however and so all supported connection scenarios will be addressed in the next major version.
Is there some repository nuget where xrmtoolkit libs can be found?
I try to automate the build of my crm project trough azure devops pipeline but it always complaining about this reference not found... SS.Crm.linq
This will be part of v7. All Microsoft.CrmSdk references will be added via their respective NuGet packages and any XrmToolkit references will have a published NuGet package as well.
When using a projection to get only certain fields from an entity via a LINQ query, allow setting read-only properties such as CreatedOn and FullName (on the Contact entity).
For example, the below query will not build because CreatedOn currently allows only get. I propose adding a setter for it as well.
var q = from p in ctx.CreateQuery<Account>()
select new Account
Id = p.AccountId,
AccountId = p.AccountId,
Name = p.Name,
CreatedOn = p.CreatedOn
This will be included in the next major version.
It would be great to be able to select Actions and Views to automatically generate their own proxy classes. For Actions, it would generate a strongly-typed proxy that accepted the typed parameters and returned the output parameters. For Views, it would generate a proxy that lets you quickly get results from System Views on each entity by just querying that View proxy. This way you could quickly model queries in Dynamics in the Advanced Find and then easily reference them in code.6 votes
The ability to create custom action proxies will be part of v7. Views will be considered but perhaps won’t make it in time for v7.
Currently it is not possible to adapt the name of proxy classes during generation.
Please provide an extension to provide custom names for proxy classes and properties.
Some generated names does not fit our naming conventions. For example special chars in german ("ß", "ä","ö" ...) or properties which will start in lower case or underscores in names.
It would be awesome to have the possibility to extend the INamingService implentation of XrmToolKit.67 votes
This will be part of v7.
Be able to add shared files (such as proxy classes) into a VS2015 Shared Project, so that they can be managed in one place, without having to resort to building a DLL and using ILMerge45 votes
Support deploying to CRM by providing an API that would support using from a command line or from a .Net app.
Should be able to call an API to publish a crm asset or plugin/workflow assembly to the CRM organization taking into account all the XrmToolkit configuration information.11 votes
The initial version of this has been released in v5. It supports merging (ILMerge) of plugin assemblies and publishing them to CRM. A future release will include the ability to deploy other assets, ie web resources etc.
Currently, there is no easy way to update all the existing proxy classes (with their respective option sets). Right now I have to select all the class files in the solution explorer, right click, then click 'CRM -> Regenerate...'
Maybe there could be an option group called 'Proxy Classes' in the context menu for the project where you can either add proxy classes or regenerate all14 votes
This will be part of v7. You will be able to right click on a folder and select ‘Download files from CRM’. This will download (in the instance of Proxy classes ‘Regenerate’) all the items that are linked in that folder and any sub-folders.
With a solution structure, where every plugin has an own visual studio project its very hard to publish multiple plugins at once. (e.g. when a method in the base class has been changed)
Please support multi selection of C# projects, like on webresources by "Right click" > "CRM" > "Build and publish".
This will be included in v7.
Right now when you register a plugin step the name is blank. I suggest that name to be default to something.
for example if the Plugin is 'MyPlugin' and the Message is 'Update' and the entity is 'Opportunity' then default the plugin name to 'MyPlugin - Update - Opportunity'
A configurable default would be nicer (as I'm sure there are a lot of different naming standards out there)3 votes
Thanks for the suggestion! This has been implemented in v4.3 based on a hard coded algorithm. We agree that using a template would be great and so until this portion is implemented we’ll keep the status set to ‘started’.
Grid-like editor to allow bulk editing of attributes. Also allow editing all aspects of individual attributes. Allow pushing all changes to CRM at one time after all edits have been made.30 votes
This feature will be added to v5.×.
- Don't see your idea?