General
56 results found
-
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.
-
Global Option Set Proxy
There should be an easy way to add global option sets as proxy classes. Currently when you generate a salesorderdetail or quotedetail or opportunityproduct as a proxy class, each one contains its own value for the GlobalOptionSet called eProductType (note that we use CRM Project services).
In order for me to create an interface to work with all 3 entities and the Product Type field, i first need to replace the enum in each file with the generic version that I created outside of each file. Then i can apply an interface that exposes this field when working with generic…
9 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
-
Easily update all proxy classes
Currently, there is no easy way to update all the existing proxy classes (with their respective option sets). Right now I have to select all the class files in the solution explorer, right click, then click 'CRM -> Regenerate...'
Maybe there could be an option group called 'Proxy Classes' in the context menu for the project where you can either add proxy classes or regenerate all
14 votesThis has been implemented in v7 which was just released. For more information on this release see here: https://xrmtoolkit.com/WhatsNew/WhatsNewInV7
-
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
-
Add Support for Source Control - Store Plugin Config and CRM Links as a File in the Project
When working in large teams on large projects, one might not know how each plugin step should be configured. Also, linking files that are newly downloaded from TFS is tedious.
This metadata should be stored in a project file and shared with the team via Source Control VSTS (TFS) or Git.
11 votesThis is already supported. See the documentation here: https://xrmtoolkit.com/General/XrmToolkitFiles
-
Connecting to CRM Online instances where authentication is MFA.
If the CRM instance implements MFA, the XRMToolkit fails to connect to the CRM Instance. Need to have different Authentication types enabled for XRMToolkit.
18 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
-
Can't null an OptionSet using ProxyClasses
Setting a OptionSetValue to null/empty is not possible using ProxyClasses?
Trying:
entity.SomeOptionSet_OptionSetValue = null ; //and that has no effect, is just ignored
entity["SomeOptionSet"] = null ; //works just fine
Why?
6 votesThis will be fixed in the next minor release v5.0.5.
-
Allow relative Reference Directories for ILMerge
When using ILMerge for project, when Override CRM Reference Directory is used, it uses absolute directory locations and thus every developer must add their own reference directories.
Would be nice if we could use relative paths to, for example, reference dlls from nuget packages.
11 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
-
Support VS2015 Shared Projects
Be able to add shared files (such as proxy classes) into a VS2015 Shared Project, so that they can be managed in one place, without having to resort to building a DLL and using ILMerge
45 votesThis has been implemented in v7 which was just released. For more information on this release see here: https://xrmtoolkit.com/WhatsNew/WhatsNewInV7
-
Support multi select of C# projects to publish all at once
With a solution structure, where every plugin has an own visual studio project its very hard to publish multiple plugins at once. (e.g. when a method in the base class has been changed)
Please support multi selection of C# projects, like on webresources by "Right click" > "CRM" > "Build and publish".Thanks,
19 votesThis has been implemented in v7 which was just released. For more information on this release see here: https://xrmtoolkit.com/WhatsNew/WhatsNewInV7
-
Support Visual Studio 2017
The current plugin doesn't work with Visual Studio 2017 RC. As we're planning to move to VS 2017 on release, and have already started evaluating it, it would be nice to have VS 2017 support in XrmToolkit.
183 votesV5 has been officially released which includes support for Visual Studio 2017 and Dynamics 365. For more information see the website: https://xrmtoolkit.com/WhatsNew/WhatsNewInV5
Thanks everyone for your patience and feedback during the beta testing!
-
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 voteThis should be the case with v7 as it uses existing names when regenerating classes/enums.
-
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 votesSee comment for details.
-
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.
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 -
Ensure IntelliSense Fully Works Alongside ReSharper
The attribute intellisense didn't seem to work unless I suspended ReSharper. (using ReSharper 2016.2.2).
13 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
-
Show custom actions in the "Message Event" list when creating new plugins
Currently, only system messages are available when creating/registering new plugins (e.g. Create, Save, Update, etc.). Users should be able to select from active custom actions that have already been created as well. Microsoft's plugin registration tool currently supports this.
11 votesThis should already be the case… but you may need to close and re-open Visual Studio in some instances. This will be improved in v7 such that they will show up immediately after creating new ones in CRM.
-
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.
85 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.
-
v4 - Default the name of the of plugin step when registering
Right now when you register a plugin step the name is blank. I suggest that name to be default to something.
for example if the Plugin is 'MyPlugin' and the Message is 'Update' and the entity is 'Opportunity' then default the plugin name to 'MyPlugin - Update - Opportunity'
A configurable default would be nicer (as I'm sure there are a lot of different naming standards out there)
3 votesThis has been implemented in v7 which was just released. For more information on this release see here: https://xrmtoolkit.com/WhatsNew/WhatsNewInV7
-
CRM 2016
Is CRM Solution manager supported for CRM 2016?
10 votesFor anyone interested, a beta of v4 is available here: http://crmsolutionmanager.com/downloads/XrmToolkit.vsix
Please note that the name is being changed from CRM Solution Manager to XrmToolkit. This is an exciting release as this version has been built from the ground up to better facilitate the ability to add new features more quickly and to take advantage of many of the language improvements in C# over the last several years.
Even though this is a beta version it has been tested and found to be quite stable. If you run into any issues, please contact support@crmsolutionmanager.com. Any links that point to the new XrmToolkit.com domain do NOT currently work. The new site is still being updated with the new features and enhancements of v4.We do not have any documentation on the new features yet but a list of some of the major enhancements are:
• Proxy Classes now derive from…
-
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 voteHi Kevin, the ability to modify the majority of the different report properties (including the ability to set the ‘Display In’) is available in v4 that was released today.
- Don't see your idea?