General
52 results found
-
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 -
17 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 -
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 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.×.
-
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
- Don't see your idea?