General
44 results found
-
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
-
Execute publish and connection in parallel
Connecting to online instances of D365 can be a little slow so waiting for this step to complete before compiling and then uploading assembly/code is time consuming. I suggesting starting the connection attempt and building the project (plugin) at the same time, once they are both complete, upload. This will save 10-15 seconds per publish which happens a ton of times over the course of a work day.
4 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 CalculateRollup function to early binding of a rollup field.
It would be great if I could Execute a CalculateRollupRequest if the field is a rollup field. Currently I have to extend the proxy class and so I could call the function. It could work similar to how lookup fields can RetrieveProxy<T> i.e. contactRecord.new_rollupfield.Rollup(OrganizationService) would execute the function.
2 votes -
Have an option to automatically disable work flows when publishing new ones
Straight forward instead of manually having to deactivate all of these workflows. Maybe there's a way to remotely deactivate them publish and reactivate them.
1 vote -
Enhance the Picklist Attribute Intellisense Feature to use a constant to represent the numeric value for the SetValue method.
The current intellisense feature for picklist attribute will generate something like this.
Xrm.Page.getAttribute("new_dropdownfield").setValue(912210002);The value 912210002 makes it less readable for future maintenance. A suggestion is to rather do the following.
Xrm.Page.getAttribute("newdropdownfield").setValue(PicklistAOption1);Define PicklistA_Option1 in the same file automatically or in an enumerations.js file that can be include.
As part of the Web Resource Minification remove this reference.4 votes -
Add unit testing mock ability
Add the ability to easily create/test plugins and other code. Something similar to https://github.com/daryllabar/XrmUnitTest or https://dynamicsvalue.com/home
4 votes -
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…
29 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 -
More verbose publishing errors
When publishing, there is just generic errors. It should be specific to the file if that's possible.
Otherwise someone would have to go through each file individually to figure out which is the culprit. (time consuming, especially if there are many resources)
Example:
[XrmToolkit v5.1.0.0] -- <Error> -- 07/09/2017 1:56:19 PM -- Errors were encountered during the publish process:
Errors:
Unable to update the file in CRM: Object reference not set to an instance of an object.
Unable to update the file in CRM: Object reference not set to an instance of an object.
Unable to update the file in…2 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 -
Pretty print the sitemap xml
...so that when I commit it to source control, I can use standard diff tools to review changes
4 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 -
publish on Build instead of Save
I tried using the option to auto-publish on Save, but I actually save a lot (because VS crashes hurt) and only want to incur the publish delay when things are in a particularly good state. In other development this is when I do a Build, and I do build my CRM client scripts (Typescript ftw), so my ideal would be for a build to publish files changed since the previous build. Slightly less ideal but still good: publish all of the project's checked-out files. Worst case, manually flagging files to publish works, too.
5 votes -
14 votes
-
Remember 'DO NOT LINK' option and allow link option/target to be changed
I use 3rd party libraries with intellisense files and need to be able to permanently mark these as not linked to CRM.
In other instances I need to be able to correct the link eg. created a new instance instead of linking to an existing instance in CRM or vice versa.
0 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 -
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.
-
Feature comparison
I would like to see a feature comparison of your product vs other tools/SDK options available
1 vote -
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
- Don't see your idea?