Instead provide your "tools" as XrmToolbox plugin for paying customers, if the tools you sell offer a reasonable extra value compared to those already available in XrmToolbox.

Rather focussing on things XrmToolkit differentiates from any other tool.

Login. See the invoices, license count and license id of licenses my company has purchased so i can easily transfer license if staff leave our organisation.

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

it would be great if OrganizationServiceContext could be used like early bound class's with "Crm Service Util" or Entity Frameworks

how i imagine using

create OrganizationServiceContext then use the context to query (like ef or the context created when generating early bound class's with "Crm Service Util")

update multiple entities using the awesome smart change tracking

run a single context.SaveChanges() (like ef or "Crm Service Util" but with the smart change tracking keeping track of what needs changing saving)

Sometimes you don't know how the form will look like when you code, and then you might want to code defensively, could it be possible to have an execution context that allows us to do this, ie.

function OnFormLoad(executionContext: XrmBase.ExecutionContext) {
var firstNameAttribute = executionContext.getFormContext().getAttribute("firstname");
if(firstNameAttribute != null) firstNameAttribute.getValue();
}

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?

Is a site license possible to purchase?

We would like to have crm data model to be kept in TFS including entities and fields. We want to track/version any changes on the data model, associate these changes with proper workitem in source control.

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

A light versjon that only support Javascipt/TS with Vistual Studio Code - generating intel. fiels for Js/TS and with publish to CRM funksjon.

• more if you like :)

In our environment warnings are generated during deployment if any public or protected class, method, or property has no summary and param comments. We use Swagger which utilizes these comments.

For Example:

/// <summary>
/// Gets the error string.
/// </summary>
/// <returns>The error string.</returns>
/// <param name="attributeName">Attribute name.</param>
/// <param name="defaultErrorType">Default error type.</param>
protected override string GetErrorString(string attributeName, BaseProxyClass.eErrorType defaultErrorType)
{
if (_errorStrings.ContainsKey(attributeName))
{
return _errorStrings[attributeName];
}
return defaultErrorType == BaseProxyClass.eErrorType.Text ? TextError : NumberError;
}

It would be nice if XrmToolkit supported the concept of versioning workflow assemblies in Dynamics. If you increment the major or minor build number of a workflow assembly, you can register a new copy of that workflow assembly with that new version and then switch over the workflows to the new version at your leisure. Here's an article on how it works: https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/workflow/update-custom-workflow-activity-using-assembly-versioning

I would like the possibility to register a plugin as data provider. Data providers are used in virtual entities.

It would be great to be able to select Actions and Views to automatically generate their own proxy classes. For Actions, it would generate a strongly-typed proxy that accepted the typed parameters and returned the output parameters. For Views, it would generate a proxy that lets you quickly get results from System Views on each entity by just querying that View proxy. This way you could quickly model queries in Dynamics in the Advanced Find and then easily reference them in code.

Ensure correct DateTime operations. Now Dynamics CRM supports two mode of working with dateTime attributes.
With or without UTC conversion.

It would be nice if generated proxy will take it into consideration.

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.

We sometimes have multiple developers working on same webresources. Ability to download the latest from CRM before start of edit and to compare server version with the original downloaded version before publish will allow us to know if some one else have make script changes while I am working on a file. This will prevent developers overwriting each others changes. Comparing local and server files manually each time you modify is not productive.

Should be able to call an API to publish a crm asset or plugin/workflow assembly to the CRM organization taking into account all the XrmToolkit configuration information.

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.