General

  1. 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

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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…

    26 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Add StringLengthAttributes to string properties of auto generated classes.

    Would it be possible to add StringLengthAttributes to string properties of auto generated classes? The length should reflect the maximum length of the CRM field.

    https://msdn.microsoft.com/en-us/library/system.componentmodel.dataannotations.stringlengthattribute(v=vs.95).aspx

    It would help much, because right now setting a value that is to long for CRM does not raise an exception but just leaves to field empty in CRM (nothing is saved).

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Acces to XrmToolkit on multiple instances(2) with one license.

    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.

    83 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  11. 12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    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.

  15. Feature comparison

    I would like to see a feature comparison of your product vs other tools/SDK options available

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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.

    77 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  18. add javascript calls to crm forms

    Provide the ability to add javascript calls to crm forms directly from visual studio.

    43 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
2 Next →
  • Don't see your idea?

General

Categories

Feedback and Knowledge Base