Skip to content

General

56 results found

  1. Add ClassName Data Slug for Plugin Step Naming Templates

    I like the Custom Naming Template for Plugin Steps feature. However all of our plugin steps that run on for instance Update of a Contact Post-Operation are all named "Update - Contact - Post-Op" with no data slug listed in the settings to allow differentiation between them.

    This recommendation is to simply add a {className} (similarly named) that would be the class name of the plugin that the step is for. This would allow use to differentiate steps registered for different plugins on the same entity easier.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Admin →
  2. Support TypeScript to the same level as JavaScript

    TypeScript support currently is not as nuanced as JavaScript - OptionSets, Attribute Types, 'getAttribute("fieldname").getValue()' typing does not currently function.

    Support TypeScript to the same level as JavaScript:

    Xrm.Page.getAttribute("fieldname") auto-typing (i.e. determine what field this is - i.e. OptionSet, so that TypeScript can do Xrm.Page.getAttribute("new_dropdownfield").getOptions() or .getValue())
    Xrm.Page.getValue("fieldname").setValue() support.

    Currently, if those (and other attribute-specific) functions are used, they are not recognised by TypeScript, meaning Intellisense throws errors constantly as invalid functions or types.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. Allow connecting to CRM Online MFA using developer's own credentials

    The current implementation (with App ID + App Secret) to connect to environments where MFA is enabled assumes we can easily get App ID and Secrets.

    In highly secured environments, we have situations where these App ID and Secrets are created for specific reasons, for specific usages and cannot be shared by multiple users (e.g. devs + XRMToolkit). It would be helpful to have the ability to pop-up the SDK control for authentication so developers can use their own credentials to login with MFA (XRM Toolbox does this)

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. First letter of proxy class should be capital and ends with the word "Entity".

    For example: The "quote" proxy class would be "QuoteEntity". This way I can say QuoteEntity quote = new QuoteEntity(); This would conform to StyleCope.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. FilteredAttributes on registration of messages

    FilteredAttributes on registration of messages for plug-ins:

    It would be nice to have a possibility to choose which attributes are going to trigger a message.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Hello Kai, this is already possible in the current plugin registration tool. When you go to register a single step, or edit an existing one, as long as the message is a valid message that you can filter on then a box will appear allowing you to select attributes to filter the plugin execution.

  6. Handle .svg files for Unified Interface

    Currently SVG files don't have the xrmtoolkit menu to add as webresources to CRM. For Unified Interface, the entity icon only supports svg files.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. Add support for multi select option set on the proxy classes

    Starting from Dynamics 365 V9, Dynamics 365 has the new multi select option set, it seems XRMToolkit has yet supported this particular field on the proxy classes.

    It will be really helpful for developers to be able to cater for this fields as it will be used more from now on.

    3 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 →
  8. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. Ability to register service end point and web hook using plug in registeration tool

    Like native SDK plug in registration tool that allows registering for service end point and web hook; it would be nice to have the similar setup within XrmToolkit for Visual studio

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. Fix up "Auto format JavaScript code on download from CRM" to support ES6

    Some of our JavaScript code currently uses features that were introduced in ES6 and ES2015, these include arrow functions and template literals.

    When we have the "Auto format JavaScript code on download from CRM" enabled in the XrmToolkit Options it breaks our code.

    The formatting adds a space between arrow functions, so "=>" becomes "= >".

    Additionally, new lines and spaces are added within strings created using template literals which completely breaks them.

    I'd be happy to provide a video demonstrating this if necessary.

    Thanks!

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. Use same case as default namespace on generated proxy classes

    I have a project with the namespace "com.crengland.services.Web.CrmApi.Xrm" but XrmToolkit always capitalizes the first character of the namespace when generating proxy classes. I have to manually replace the namespace in generated proxy classes to fix this issue.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. Improve SSRS report publishing

    Publishing SSRS reports sometimes does not reset the data source to the default MSCRM_DataSource in the CustomReports folder; it must be manually changed by connecting to Report Manager and resetting it there. Also, new reports in CRM do not get a "Display In:" setting of "Reports area", requiring one to find the report in the "All reports" view and set this before it will appear in the "My Reports" view; it would be nice to automatically apply these settings by default.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. Add a possibility to switch between ogranisation

    Add a possibility to switch between different organisations so that if you want to publish a bug fix to test instead of dev without opening a new VS Solution.

    1 vote
    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 →
  14. Allow Integrated Windows Authentication

    No need to type in the current credentials.. Use the credentials of the computer who is already logged in.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. Move entity/message names to separate file instead of in BasePlugin.cs

    At this moment the BasePlugin.cs combines both logic as well as the string constants for entity/message names.
    If you decide to tweak the BasePlugin.cs (I added OrgServiceAs Admin user for example) and you refresh the entity/message names, it throws away your changes.

    Either only update the entity/message names or move them to a separate file

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. Filenames based on logicalname

    Option to use the logicalname(actual name) for the files created instead of the Name/Display Name.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
1 3 Next →
  • Don't see your idea?

General

Categories

Feedback and Knowledge Base