Skip to content

General

47 results found

  1. 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…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 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…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
1 3 Next →
  • Don't see your idea?

General

Categories

Feedback and Knowledge Base