Distribution folder structure changed

Since 6.0.0 the distribution folder will contain folder per entity and that folder will contain a javascript file per form.
This is a braking change, having low impact but needs some manual changing the form onload.

hso-d365 update prevents downgrad

When doing update while project has higher cli version it will show a warning

hso-d365 update

ADAL migrated to MSAL

ADAL is upgraded to MSAL.
You need to update your project:

    hso-d365 update

Differences:

1. No more progress logging in browser, but in console
2. Only a browser tab when need for logging in
3. A .msalcache.json file will be added runtime in Webresources folder (.gitignored)

CLI Version check

On root level there is a crm.json having a version field now.
This one will be used to compare with current CLI version. Having this, both the programmer and project will be encouraged(forced) to update the project and/or cli.

Entity typings

A typings file will be generated in the entity root folder. d.ts.

• It will show intellisense
• It will know the return type
• It will have a build failure when using invalid name

const formContext: Account.Information = executionContext.getFormContext();
const nameControl = formContext.getControl('name');

Dart Sass

Using Dart Sass instead of Node Sass

Node >= 14

Node forced to be >= 14 to prevent problems

Generic type support for executeAction

Generic type support for executeAction makes the strange unknown parsing not needed.

const result = await WebApi.executeAction('FindLocation', locationData) as unknown as FindLocationResult; // Before
const result = await WebApi.executeAction('FindLocation', locationData) as FindLocationResult; // Now

Support FormattedValue in Model

The generated model will contain FormattedValue and other formatting as well.

You need to update your project

hso-d365 update

Support for separate solution to generate from

Before there was only one solution to generate from and deploy to. However a lot of projects use a separate solution to put all webresources in. In that case the generate should happen on another solution as the deploy. This is implemented in this version.

You need to update your project by:

hso-d365 update

Or manual change tools/crm.json

From

solution_name: "x"

To

solution_name_deploy: "x",
solution_name_generate: "x or y"