Microsoft.PowerApps.CLI 1.9.8

Learn more about Target Frameworks and .NET Standard.

• .NETStandard 2.0

  • System.ComponentModel.Composition (>= 5.0.0)

Please make sure to update your Microsoft Power Platform CLI to the latest version and take advantage of all the latest capabilities by following https://aka.ms/PowerPlatformCLI.
If you are a new user please install the Power Platform CLI directly from here: https://aka.ms/PowerPlatformCLI

1.9.8:
- pac solution pack|unpack: add support for modern SiteMap
- pac admin module, all verbs: new parameter --environment that allows to specify url or env ID as its value (deprecating --environment-id and --url)
- pac CLI for Windows now runs on .NET 4.8
- new verb: pac solution delete
- Updated MSAL to 4.35
- pac solution unpack: don't delete existing files (unless forced with --AllowDeletes)

- paportal module:
 - Populate the deployment profile after reading entity data from files
 - Generate unique display names on encoded value
 - Create annotations with name same as webfiles

1.9.4
- pac auth create --kind Dataverse: interactive login for username/password is now also supported on macOS and linux
- pac auth create: renamed --kind to Dataverse (older CDS kind name is still accepted)
- pac canvas: updated to latest PowerApps-Language-Tooling library 0.3.8-preview
- pac plugin init now generates strong-name key without sn.exe from VisualStudio
- pac solution create-settings to extract connection references & environment variables from solution
- pac solution pack|unpack: SolutionPackager is now integrated into pac CLI and works on all 3 supported OS;
 SoPa no longer needs to be installed via separate nuget package
- all verb parameters that accept file or folder paths now have consistent handling of absolute and relative paths
- Fixes:
 - pac admin list properly paginates all environments in tenant
 - pac package deploy: report parse error when reading deployment config file
 - pac paportal: Fixing website id not found error
 - pac pcf init & pac plugin init also support optional --outputDirectory
 - pac solution list now supports Dataverse authentication profile with AppID/SPN too
 - pac solution (all verbs): properly surface the returned service side error to user (in raw form)

1.8.6
- pac admin status no longer stumbles over no longer existing environments
- pac canvas using latest MS.PP.Formulas.Tools 0.3.6-preview library
- pac paportal improvements:
 - Upload of portal data running in parallel threads
 - Support a tag based deployment profile for upload
 - Replace all string based primary key references with schema based primary key.
 - Improved error reporting during parallel execution and when encountering YAML errors
- pac pcf init also runs npm install to get the new PCF project fully initialized
- pac solution check to submit solution.zip to PowerPlatform Checker endpoint
- pac solution version applies version to solution.xml found
- rename to "Power Platform CLI" in user facing friendly names; the executable still remains named as 'pac.exe';
 no rename planned for nuget package names
- Updated SolutionPackager with localization support for solution aware entities

1.7.4:
- new module paportal to list, download and upload PA Portals
- new module canvas to pack and unpack PowerApps .msapp files
- added new verb: pac solution add-license
- pac package deploy correctly handles relative paths for --package argument
- fix error when trying to delete expired auth profile (pac auth delete)

1.6.6:
- fix broken Dataverse authentication when using appId/tenantId/clientSecret
- new retry logic for calls to Dataverse API
- cross platform support for project templates
- update to latest Microsoft.PowerPlatform.Dataverse.Client 0.4.11
- reintroduced --convert-to-managed argument for "solution import" command

1.5.2:
- New and updated CLI modules and commands:
 - "pac admin": PAC Admin module to work with your Power Platform Admin account. You can create, backup, reset, list, restore, copy and delete environments.


1.4.4
- PCF ControlManifest versioning
 - can now accept an argument for specifying filename for file tracking strategy
 - can accept path as an argument
- Localization updates for CLI
- New and updated CLI modules and commands:
 - "pac package" CLI support to create, build and push package
 - "pac auth create" now supports username/password without interactive prompt
 - "pac auth create" now supports SPN authentication
 - Increased character limit for auth profile name from 12 to 30
 - "pac solution import/export" now have support for async
 - "pac solution upgrade" CLI support to upgrade the solution
 - "pac solution list" CLI support to list all solutions in a CDS organization
 - "pac solution version" CLI support to increment patch version for solutions
- CLI now has refreshed icons

1.3.6
- PCF ControlManifest versioning:
 - persist patch version strategies using gittags, tracking file
 - can push gittags patch versions using PAT

1.3.5
- PCF ControlManifest versioning can now automatically increment patch version using git tags to store previous versions:
   pac pcf version --strategy gittags

1.3.1:
- New verb to modify PCF control’s patch version:
   pac pcf version --patchVersion 4
- update to latest CrmServiceClient 9.1.0.42 (Microsoft.CrmSdk.XrmTooling.CoreAssembly)


1.2.6:
- update to latest CRM SDK versions

1.1.6:
- New and updated CLI modules and commands:
 - "pac plugin init": create a new CDS plugin class library from a template
 - "pac solution add-reference": you can now add references to plugin projects created using "pac plugin init." When your solution (cdsproj) is built, it will also build your plugin projects and copy the output DLLs into your solution zip.
 - "pac solution clone": create a solution project based on an existing solution in an organization
- CLI is now localized in the 44 languages supported by Dynamics365/CDS

1.0.6:
- "pac solution init" will now convert publisher prefix to lower case
- Argument short names now require only a single dash
- Projects that share the same name as the cdsproj cannot be added as a referenced project
- Various bug fixes for "pac auth" commands
- Various bug fixes related to project paths that include whitespace
- "pac pcf push" command will no longer attempt to delete the temporary solution

0.4.3:
- New CLI modules and commands:
 - "pac auth": supports managing OAuth profiles to authenticate with CDS organizations
 - "pac pcf push": import a PCF control into a CDS organization
 - "pac org": first CDS organization command; for now, only "who-am-I" is supported
- PCF project template now uses a minimum version of 1.2.0 for @types/powerapps-component-framework

0.3.4:
- CLI arguments have optional shorted aliases
- Unified naming and spelling of parameters, e.g. --publisher-prefix and --publisher-name
- Consistent version showing for CLI and its nuget packages

0.2.71:
- PowerApps CLI and PCF are localized for: English, French, German, Japanese, Spanish
- Updated MSI registry path to: Software\Microsoft\PowerApps CLI\Installed
- Improved error messaging in the CLI launcher
- Updated help descriptions

0.2.59:
- PCF build output enhancements include:
 - Colorization
 - Timestamps
 - Formatting updates
- PCF build now produces formal error codes in conjunction with error messages
- A .gitignore file is added for all newly created CDS solution projects
- We are also enabling clean target for Solution projects

0.1:
- initial set of capabilities for custom control development using the PowerApps Component Framework (PCF).