General
54 results found
-
Support for solution packager to extract files into the project
Add support for solution packager to extract files into the project after a publish to CRM - make it optional during a publish. Currently this would need to be done via creating build scripts and updating the targets. It would be nice if this was built in to CRM Solution Manager and could be controlled by the UI.
78 votes -
add javascript calls to crm forms
Provide the ability to add javascript calls to crm forms directly from visual studio.
43 votes -
Editor to allow bulk editing of entity attributes
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 votesThis feature will be added to v5.×.
-
Support Plugin Profiler
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…
30 votes -
CRM Chart Editor
CRM Chart Editor (GUI) that would allow you to edit all the properties of a chart without manually editing the XML.
18 votes -
Compare webresouces - advise stale copy before publish
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 -
17 votes
-
Support versioning of custom workflow assemblies
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-versioning
14 votes -
New versjon for Vistual Studio Code (Js/Ts functions + publish)
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 :)
14 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 votesThe 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.
-
Support for CRM Developer Toolkit Packaging project
I know there is a ton of overlap between the CRM Solution Manager and the CRM Developer Toolkit.
If I develop a solution that has a Packaging project from the developer toolkit, I can ensure other CRM developer can deploy customizations. The only problem is that I can't right click an Web Resource in the Packaging project and quickly publish to CRM using the CRM Solution Manager.
10 votes -
Add a method to proxy classes to lookup option set values via string
It would be nice if the the ExtensionMethods or some other feature in the BaseProxyClass would return an option set value via text based on the [Description] in the enum. Perhaps this already exists but, I did not see it in the documentation.
Something like
OptionSetValue ov = new OptionSetValue(ExtensionMethods.GetOptionSetValue("Active"));9 votes -
CRM data model in source control
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.
9 votes -
Ability to register plugin as data provider
I would like the possibility to register a plugin as data provider. Data providers are used in virtual entities.
8 votes -
Drop idea "D365 Tools Window" - not re-inventing XrmToolbox concept
Instead provide your "tools" as XrmToolbox plugin for paying customers, if the tools you sell offer a reasonable extra value compared to those already available in XrmToolbox.
Rather focussing on things XrmToolkit differentiates from any other tool.
8 votes -
Possibility of generating ProxyClasses with Properties-class only
Some Proxy Classes can be very large (eg. SystemUser - around 1.5MB) causing the assembly to grow quite significantly, but they can have very limited usage in the actual plugins / workflows, eg. only for strong typing attribute names inside a Fetch Xml or a Query Expression.
I would like it to be possible to have an option when adding a Proxy Class to a project to make it "Strong Typing only" and have just the ProxyClass with the inner Properties class generated to keep it small in size.
I would also like regenerating of such Proxy Class to update…
7 votes -
Ensure correct DateTime operations
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.
6 votes -
Add Entity Metadata and Lookup values as Javascript Class
Create Javascript/Typescript classes containing entity metadata and lookup values that can be added to a Form and referenced for intellisense.
6 votes -
Add Entity Metadata Repository Instead of hardcoded metadata information inside proxy classes, it would be awesome to provide this informati
Add Entity Metadata Repository
Instead of hardcoded metadata information inside proxy classes, it would be awesome to provide this information inside a repository.Something like:
var entityRepositoryItem = MetadataRepository.GetEntity(param entity);
var attributeItem = entityRepositoryItem.GetAttribute(string name);Console.WriteLine(attributeItem.Max Length);
Console.WriteLine(attributeItem.Logicalname);
...6 votes -
Add Actions and Views to generated proxy classes
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 votesV7 was just released which includes support for generating proxy classes for ‘Actions’. For more information on this release see here: https://xrmtoolkit.com/WhatsNew/WhatsNewInV7
- Don't see your idea?