Skip to content

General

I suggest you ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

53 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)
    Close
    Close
    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)
    Close
    Close

  2. Add ability to use NPM for Web Resources, as well as unit tests

    Nodejs projects natively use npm as the package manager, which works better with TypeScript (in my experience at least). Unit testing would be made easier as well. Those that would rather use nuget should be able to use .NET Core projects, which also includes native TypeScript unit test support as described in the documentation:

    https://docs.microsoft.com/en-us/visualstudio/javascript/unit-testing-javascript-with-visual-studio?view=vs-2019&tabs=mocha

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  3. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  4. 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)
    Close
    Close
    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)
    Close
    Close

  5. plugin link

    When I build & publish, the assembly gets added to the chosen solution automatically.

    I have multiple project for different assemblies – and sometimes I by mistake build/publish the wrong one. Sometimes changes include other base assemblies, that are already added to different solution. But when developing, I must build & publish that particular assembly too without changing solution context – and boom, it gets added to solution.

    Usually I notice when I export solution with packager and then I go to CRM, remove dll and export again. Somehow I even missed that (ahh, everything in that solution must be…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  6. Being able to override the default 1033 language, when generating option sets.

    Used when showing a list of options from CRM, where you don't want languages mixed up.

    Like you can with early bound generator, found on XrmToolBox.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  7. Add support for Custom Page

    Custom page and canvas app are similar thing to web resources that can be downloaded.

    Thanks.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  8. Automatically validate strong name

    Sometimes when using ILMerge, the strong name is not valid when the dll is created. It would be a nice feature to validate the strong name first before uploading. And if the strong name is not valid, automatically resign the dll to fix the issue.

    1.) Run sn -vf *.dll
    2.) Confirm that the dll is either a delay or test signed
    3.) Run sn -R *.dll *.snk
    4.) Confirm that the dll is now valid

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  9. Provide a Guideline for Dependent Plugin Assemlies

    Could you please so kind to provide a guideline how you planed to work with Dependent Assemblies in Version 8.2?

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  10. Improvements to Development of Dependent Assembly Plugins (Plugin Package)

    When exporting a solution with a plugin package component, the pluginpackageid isn't exported. This cause an issue where importing the solution will generate an unique pluginpackageid per environment.

    XrmToolkit uses 'PluginAssemblyPackageId' to match plugin packages based on pluginpackageid. This can cause an issue when using the same plugin package across multiple environments.

    Ideally we would like XrmToolkit to match plugin package based on the name rather then the pluginpackageid.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  11. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  12. Create VS Project for new Power Pages Solution

    Ability to create VS project from new Power Pages portals. Currently can only select Power Apps Portals.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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)
    Close
    Close

  13. 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)
    Close
    Close
    You have left! (?) (thinking…)
    3 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)
    Close
    Close
1 3 Next →
  • Don't see your idea?

General

Categories

Feedback and Knowledge Base

(thinking…)