(https://www.nuget.org/packages/Microsoft.Powerplatform.Cds.Client.Dynamics)

Should require minimal change - new compile target. Client only, leave aside workflow & plugins etc.

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?

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

    }

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,
Nicolas

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

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.

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;

}

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 :)

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.

When you want to create an interface for a class you can use the helper "extract interface" on the class definition. This does not copy the leading comments used with tools such as Swagger; i.e. the comment block created with the three forward slashes ///

For example:

    /// <summary>

    /// Configuration manager

    /// </summary>

    protected readonly IConfigurationKeyManager _configurationKeyManager;

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

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

Generate POCO or DTO early binding classes which do not have any references to the SDK. Any 1:n relationships are created as Property LIST<MyEntity>. Any Optionsets are generated as enums in separate file so there are no duplicates (i.e. status and statusReason ). The ability for these POCO classes to then generate an XSD without error. At run time AutoMapper could map from POCO to ProxyClasses

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

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.

Connecting to online instances of D365 can be a little slow so waiting for this step to complete before compiling and then uploading assembly/code is time consuming. I suggesting starting the connection attempt and building the project (plugin) at the same time, once they are both complete, upload. This will save 10-15 seconds per publish which happens a ton of times over the course of a work day.

Hi Team,
I have updated to the latest version of xrmtoolkit from version 5.1.0.0
Publishing loader message pop-up is shifted to the right of the screen instead of center of screen. Although minor but could be corrected in the upcoming versions.
Thanks,
Anubhav

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.

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.