The d365-cli from hso-nn

Support for File attributes in Model

Add support to read/write attributes of type File in the generated models.

Microsoft documentation: https://docs.microsoft.com/en-us/powerapps/developer/data-platform/file-attributes

css files arent build during dev build

Generating dashboards result in error with guids

Generating dashboards result in error with guids:

Quote enum Status Code Duplicate value

Handle duplicate values in enums, for example quote status enum:

Implement Power Apps ESLint

See: https://community.dynamics.com/blogs/post/?postid=f7ccd6a1-b176-44b0-96c2-fe5939eb24b7

https://www.npmjs.com/package/@microsoft/eslint-plugin-power-apps

Support single quote in view names

Reproduction:
Generate model for Incident entity -> View My Team Members' Resolved Cases

Wiki: installation instructions

Mention NodeJS version (LTS version)
ESLint plugin not referening to github, but mention it should be installed as VS Code Extension
Visual Studio Code: mention that the change of settings should be done in the global and not in your own workspace

Wiki: Fiddler installation/configuration update

Wiki: Fiddler installation/configuration update.
Make sure texts are correct (especially the *). Also add screenshots to make clear.

Types in Model files should be prefixed

Types in Model files should be prefixed.

Too often equal names in different entities. Example: Account, Contact

Support regenerate command

Force Update

Create an option to force updates, even when there is nothing changed...

Support separate solution to generate from

In crm.json something like
'solution_name_generate'

and current 'solution_name' or rename to 'solution_name_deploy'

Add command line options for all commands

Make it possible to use command line options for alle commands

FormContext getControl support

The FormContext already supports getAttribute. Please support getControl as in example below.

export class AccountForm extends AccountFormContext {
    static async onLoad(executionContext: Xrm.Events.EventContext): Promise<void> {
        const formContext = executionContext.getFormContext();
        
        // Already supported
        const accountNameAttribute = AccountForm .getAccountNameAttribute(formContext);
        
        // Not supported yet / Enhancement
        const accountNameControl = AccountForm .getAccountNameControl(formContext);
    }
}

Environment Variable util

Please provide util Entity for 'environmentvariabledefinition' like there is for 'Annotation'.

More info:

Wiki: Deploy documentation

Mention at the deploy wiki part that npm run build:prod is needed before deploy can be done (just like is mentioned on README page)

Formcontext typings

Support form typings as in XrmDefinitelyTyped

const formContext: Account.Form.Main = executionContext.getFormContext();

Deploy command should check for dist folder

Validate dependencies like NodeJS 14 (LTS)

Create should make clear that 'D365 Solution name' is the unique name ('Name' column)

Support FormattedValue in Model

comment incorrect for adding onload method on forms

// hds.dm.SharePointStorageConfiguration.SharePoint Storage Configuration Info.Form.onLoad

contains whitespaces

Update deprecated packages

When creating a new project using the CLI you will get several warnings for outdated/deprecated packages. Please keep the required packages up to date.
Let's try to keep away from vulnerabilities.

npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated @babel/[email protected]: 🚨 This package has been deprecated in favor of separate inclusion of a polyfill and regenerator-runtime (when needed). See the @babel/polyfill docs (https://babeljs.io/docs/en/babel-polyfill) for more information.
npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm WARN deprecated [email protected]: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.

added 1196 packages, and audited 1197 packages in 60s

103 packages are looking for funding
  run `npm fund` for details

51 vulnerabilities (2 low, 42 moderate, 7 high)

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.

FormContext should return Enum type instead of number for OptionSets

Translation not working in HTML Webresources

Translation not working in HTML Webresources where form has nog translation

PowerApps Component Framework (PCF) support

Please add support for generating, publishing and debugging PCF Controls.

executeAction using generic type for return

executeAction using generic type for return.
Update wiki example as well (no unknown needed anymore)

public static async executeAction<D>(actionName: string, data?: unknown, entityLogicalName?: string, id?: string): Promise<D> {
        if (entityLogicalName) {
            return this.executeBoundAction(actionName, data, entityLogicalName, id);
        } else {
            return this.executeUnboundAction(actionName, data);
        }
    }