Should require minimal change - new compile target. Client only, leave aside workflow & plugins etc.7 votes
Support PCF development which currently requires a lot of additional scripting to build/publish into CDS/XRM. This looks set to replace replace custom web resources so would be an appropriate progression for the product.
May be worth considering a change of name to CDS or PowerApps Toolkit?2 votes
Is a site license possible to purchase?1 vote
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
Sometimes when using ILMerge, the strong name is not valid when the dll is created. It would be a nice feature to validate the strong name first before uploading. And if the strong name is not valid, automatically resign the dll to fix the issue.
1.) Run sn -vf .dll
2.) Confirm that the dll is either a delay or test signed
3.) Run sn -R .dll *.snk
4.) Confirm that the dll is now valid1 vote
We would like to have crm data model to be kept in TFS including entities and fields. We want to track/version any changes on the data model, associate these changes with proper workitem in source control.2 votes
In our environment warnings are generated during deployment if any public or protected class, method, or property has no summary and param comments. We use Swagger which utilizes these comments.
/// Gets the error string.
/// <returns>The error string.</returns>
/// <param name="attributeName">Attribute name.</param>
/// <param name="defaultErrorType">Default error type.</param>
protected override string GetErrorString(string attributeName, BaseProxyClass.eErrorType defaultErrorType)
return defaultErrorType == BaseProxyClass.eErrorType.Text ? TextError : NumberError;
A light versjon that only support Javascipt/TS with Vistual Studio Code - generating intel. fiels for Js/TS and with publish to CRM funksjon.
- more if you like :)
similar to the webresources editing capabilities it would be very handy to be able to download edit and publish ms portal web pages and templates from visual studio.4 votes
I would like the possibility to register a plugin as data provider. Data providers are used in virtual entities.6 votes
It would be nice if XrmToolkit supported the concept of versioning workflow assemblies in Dynamics. If you increment the major or minor build number of a workflow assembly, you can register a new copy of that workflow assembly with that new version and then switch over the workflows to the new version at your leisure. Here's an article on how it works: https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/workflow/update-custom-workflow-activity-using-assembly-versioning7 votes
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.
Like native SDK plug in registration tool that allows registering for service end point and web hook; it would be nice to have the similar setup within XrmToolkit for Visual studio2 votes
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.
Ensure correct DateTime operations. Now Dynamics CRM supports two mode of working with dateTime attributes.
With or without UTC conversion.
It would be nice if generated proxy will take it into consideration.5 votes
I know the ToolKit uses the Plugin Reg Tool to do most of the work, but incorporated in Visual Studio. One feature of the Plugin Registration Tool that isn't with the ToolKit is using the Plugin Profiler. I assume you know what it is, but just in case, it's a solution for CRM that comes with the sDK/Plugin Registration Tool (PRT), from the PRT you can install the solution into your CRM solution, and once installed you can replay plugin messages, workflows, and then by attaching visual studio to it, you can debug. Seems like this would be a great feature for the toolkit.
I know the ToolKit uses the Plugin Reg Tool to do most of the work, but incorporated in Visual Studio. One feature of the Plugin Registration Tool that isn't with the ToolKit is using the Plugin Profiler. I assume you know what it is, but just in case, it's a solution for CRM that comes with the sDK/Plugin Registration Tool (PRT), from the PRT you can install the solution into your CRM solution, and once installed you can replay plugin messages, workflows, and then by attaching visual studio to it, you can debug. Seems like this would be a great…25 votes
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 ILMerge43 votes
As a developer, I'm using at least two laptops for developing software. I would love to have an option to transport my license when I'm developing. Now, I need tot think about activating the license on a virtual machine and move the virtual machine from one to another.75 votes
We sometimes have multiple developers working on same webresources. Ability to download the latest from CRM before start of edit and to compare server version with the original downloaded version before publish will allow us to know if some one else have make script changes while I am working on a file. This will prevent developers overwriting each others changes. Comparing local and server files manually each time you modify is not productive.18 votes
- Don't see your idea?