General
56 results found
-
PolySharp Integration
Integrate PolySharp which allows to use features of C# 11 while still being on .net 4.6.2 and C# 7.3.
Reference & install guide: https://itmustbecode.com/dataverse-plugins-unlock-the-latest-c-features-with-polysharp/6 votes -
Support for Dependent Assembly plug-ins
Microsoft is introducing Dependent Assemblies (currently in preview), which will take over functions of ILMerge (which is deprecated) and can be used in Plugins to load dependent assemblies. More on the topic: https://docs.microsoft.com/pl-pl/power-apps/developer/data-platform/dependent-assembly-plugins
10 votesIf you would like to test out the preview of v8, you can use one of the links here:
- https://xrmtoolkit.com/downloads/xrmtoolkit_8_0_1_0.vsix (VS2017/19)
- https://xrmtoolkit.com/downloads/xrmtoolkit.x64_8_0_1_0.vsix (VS2022)
Please note that there is not any documentation yet for any new features. You can only request a trial license at this point after installing the new version. However, the trial duration is for 120 days currently until v8 is released. Please submit any issues via the regular support options and not directly to this suggestion.
-
Support Visual Studio 2022
Visual Studio 2022 is coming soon and currently available as Preview 2.1. Is XRMToolkit going to be supported?
40 votesIf you would like to test out the preview of v8, you can use one of the links here:
- https://xrmtoolkit.com/downloads/xrmtoolkit_8_0_1_0.vsix (VS2017/19)
- https://xrmtoolkit.com/downloads/xrmtoolkit.x64_8_0_1_0.vsix (VS2022)
Please note that there is not any documentation yet for any new features. You can only request a trial license at this point after installing the new version. However, the trial duration is for 120 days currently until v8 is released. Please submit any issues via the regular support options and not directly to this suggestion.
-
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 voteImplemented in v7
-
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 -
Add support for Dynamics 365/DataVerse portal assets
Please add the ability to modify portal assets similar to the way that you can download/update/publish web resources.
17 votesAn initial implementation has been completed and you can test this out in the following build: https://xrmtoolkit.com/downloads/xrmtoolkit_7_0_4_5.vsix.
You can add a new portal project from the solution level: ‘D365 → Add New Project → New project from Portal Website’.
Please reach out to support if you find any issues.
-
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 votesThis has been implemented in v7 which was just released. For more information on this release see here: https://xrmtoolkit.com/WhatsNew/WhatsNewInV7
-
Support for Powerapps Component Framework (PCF Control)
Support PCF development which currently requires a lot of additional scripting to build/publish into CDS/XRM. This looks set to replace replace custom web resources so would be an appropriate progression for the product.
May be worth considering a change of name to CDS or PowerApps Toolkit?
18 votes -
Support new .net Core Client
(https://www.nuget.org/packages/Microsoft.Powerplatform.Cds.Client.Dynamics)
Should require minimal change - new compile target. Client only, leave aside workflow & plugins etc.
15 votesXrmToolkit will now not try to install the other SDK NuGet package if it detects that the newer SDK is already installed. Perhaps when the new SDK is officially released we can provide the option to choose which package to install by default (when nothing is installed yet).
-
Nuget packages for XrmToolkit
Is there some repository nuget where xrmtoolkit libs can be found?
I try to automate the build of my crm project trough azure devops pipeline but it always complaining about this reference not found... SS.Crm.linq
Best regards,
Nicolas8 votesThis has been implemented in v7 which was just released. For more information on this release see here: https://xrmtoolkit.com/WhatsNew/WhatsNewInV7
-
Provide option to use ILMerge via NuGet
Currently we have to provide the full path to ILMerge.exe in the options menu. Since the only way to get new versions of ILMerge is to download the NuGet package from https://www.nuget.org/packages/ilmerge/ extract it manually and overwrite the files in the path given.
So my idea was to give the option to use ILMerge via NuGet. Means your extension would check from time to time if there are never versions of the package available and will download and extract it to the path next to the SDK files.
9 votesXrmToolkit has taken a direct dependency on ILMerge in the next minor version (6.3) which will be published shortly. You will no longer be required to download it manually. In the mean time you can try the following build: xrmtoolkit.com/downloads/xrmtoolkit_6_2_0_8.vsix which also has the fix.
-
Allow setting of all properties on Proxy Classes
When using a projection to get only certain fields from an entity via a LINQ query, allow setting read-only properties such as CreatedOn and FullName (on the Contact entity).
For example, the below query will not build because CreatedOn currently allows only get. I propose adding a setter for it as well.
var q = from p in ctx.CreateQuery<Account>() orderby p.Name select new Account { Id = p.AccountId, AccountId = p.AccountId, Name = p.Name, CreatedOn = p.CreatedOn }4 votes -
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 voteThis will be fixed in the next minor version (6.3).
-
Support for VS2019
VS 2019
20 votesYou can try out the beta of V6 by installing the following: https://xrmtoolkit.com/downloads/xrmtoolkit_6_0_0_11.vsix
To learn about what’s new see here: https://xrmtoolkit.com/WhatsNew/WhatsNewInV6
Please report any issues to support@xrmtoolkit.com
-
edit and publish ms portal web templates / pages from visual studio
similar to the webresources editing capabilities it would be very handy to be able to download edit and publish ms portal web pages and templates from visual studio.
7 votesThis has been added to the newly released v7.
-
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 votesYou can try out the beta of V6 by installing the following: https://xrmtoolkit.com/downloads/xrmtoolkit_6_0_0_11.vsix
To learn about what’s new see here: https://xrmtoolkit.com/WhatsNew/WhatsNewInV6
Please report any issues to support@xrmtoolkit.com
-
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 votesThis has been released as part of v7.
-
Provide NamingServiceExtension for proxy classes
Currently it is not possible to adapt the name of proxy classes during generation.
Please provide an extension to provide custom names for proxy classes and properties.Some generated names does not fit our naming conventions. For example special chars in german ("ß", "ä","ö" ...) or properties which will start in lower case or underscores in names.
It would be awesome to have the possibility to extend the INamingService implentation of XrmToolKit.
67 votesThis has been implemented in v7 which was just released. For more information on this release see here: https://xrmtoolkit.com/WhatsNew/WhatsNewInV7
-
Allow Integrated Windows Authentication
No need to type in the current credentials.. Use the credentials of the computer who is already logged in.
1 voteReleased as part of v6.1.0.0
-
Filenames based on logicalname
Option to use the logicalname(actual name) for the files created instead of the Name/Display Name.
1 voteThis is actually supposed to the be the default behavior. A bug was introduced at some point causing this to be broken. This will be fixed in the next minor update.
- Don't see your idea?