microsoft / powerplatform-build-tools Goto Github PK

Power Platform Build Tools automate common build and deployment tasks related to Power Platform. This includes synchronization of solution metadata (a.k.a. solutions) between development environments and source control, generating build artifacts, deploying to downstream environments, provisioning/de-provisioning of environments, and the ability to perform static analysis checks against your solution using the PowerApps checker service.

License: MIT License

JavaScript 12.75% Shell 0.01% Batchfile 0.01% TypeScript 84.93% C# 2.30%

azure-devops azure-devops-extension ci-cd dataverse powerplattform

powerplatform-build-tools's Introduction

Power Platform Build Tools

Learn more about the Build Tools here.

Each tasks wraps the existing Power Platform CLI.

High level architecture

Feedback & Questions

Please use the issues tracker in the home repo: https://github.com/microsoft/powerplatform-build-tools/issues

Community Office Hours

We hold monthly office hours (every 3rd thursday of the month) where you can ask specific question to the product team.

See additional details in COMMUNITY OFFICE HOURS

Contributing

This project will welcome contributions in the near future. At this stage, we're not ready for contributions, but do welcome your suggestions via this repository's issue tracker.

See details in CONTRIBUTING

Code of Conduct

See details in CODE_OF_CONDUCT

Security issues

Please report any security concerns or issues as described in this SECURITY document.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.

powerplatform-build-tools's People

Contributors

Stargazers

Watchers

powerplatform-build-tools's Issues

Download Portal does not have option to exclude tables

The PAC CLI download portal includes.

   --excludeEntities           Comma separated list of entity logical names to exclude downloading (alias: -xe)

This is a huge security risk as site settings such as "Authentication/OpenAuth/Microsoft/ClientSecret" that contain secret values would be stored in source control.

Bearer Token Expiring During Solution Import since v0.0.82

Hi all,

We cannot succesfully import our Solution... It appears it's a bug introduced after 0.0.77 (as that version 0.0.77 was working last week).

Our solution takes over an hour to import (but usually < 1.5 hrs).
We are running Async and not publishing as part of the import.
What it seems like to me is that the bearer token is not being refresh when imports are longer than an hour (some builds have failed between 1hr and 1.5hrs).

Options being used:

solution import --path xxxx.zip --async true --import-as-holding false --force-overwrite false --publish-changes false --skip-dependency-check false --convert-to-managed false --max-async-wait-time 240 --activate-plugins true --settings-file xxx.json'

Important parts of the log:

Task : Power Platform Import Solution
Description : Power Platform Import Solution
Version : 0.0.84
Author : Microsoft

....

Solution Importing...
Waiting for asynchronous operation 6c33d1fd-fafa-ec11-82e6-002248186ad1 to complete with timeout of 04:00:00
Processing asynchronous operation... execution time: 00:00:00 and 1% complete
Processing asynchronous operation... execution time: 00:00:04 and 2% complete
Processing asynchronous operation... execution time: 00:00:08 and 3% complete
Processing asynchronous operation... execution time: 00:00:12 and 4% complete
Processing asynchronous operation... execution time: 00:00:16 and 5% complete
Processing asynchronous operation... execution time: 00:00:20 and 6% complete
Processing asynchronous operation... execution time: 00:00:24 and 7% complete
Processing asynchronous operation... execution time: 00:00:28 and 8% complete
Processing asynchronous operation... execution time: 00:00:32 and 9% complete

....

Processing asynchronous operation... execution time: 01:11:43 and 100% complete
Processing asynchronous operation... execution time: 01:11:47 and 100% complete
Processing asynchronous operation... execution time: 01:11:51 and 100% complete
Processing asynchronous operation... execution time: 01:11:55 and 100% complete
Processing asynchronous operation... execution time: 01:11:59 and 100% complete
Processing asynchronous operation... execution time: 01:12:03 and 100% complete
Processing asynchronous operation... execution time: 01:12:08 and 100% complete
Processing asynchronous operation... execution time: 01:12:12 and 100% complete
Processing asynchronous operation... execution time: 01:12:16 and 100% complete
Processing asynchronous operation... execution time: 01:12:20 and 100% complete
Microsoft PowerPlatform CLI
Version: 1.15.10+g15dc5d3

Error: The HTTP request is unauthorized with client authentication scheme 'Anonymous'. The authentication header received from the server was 'Bearer authorization_uri=https://login.microsoftonline.com/xxxx/oauth2/authorize, resource_id=https://xxxx.crm6.dynamics.com/'.
The HTTP request is unauthorized with client authentication scheme 'Anonymous'. The authentication header received from the server was 'Bearer authorization_uri=https://login.microsoftonline.com/xxxx/oauth2/authorize, resource_id=https://xxxx.crm6.dynamics.com/'.
The remote server returned an error: (401) Unauthorized.

Publish always runs into timeout 4 Minutes

The publish step generally leads to a timeout.

Publishing All Customizations...
Microsoft PowerPlatform CLI
Version: 1.18.4+g1a00e63

Error: The request channel timed out while waiting for a reply after 00:04:00. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.
The HTTP request to 'https://xxxxx.crm4.dynamics.com/XRMServices/2011/Organization.svc/web?SDKClientVersion=9.2.47.9489' has exceeded the allotted timeout of 00:04:00. The time allotted to this operation may have been a portion of a longer timeout.
The operation has timed out

Even though the timeout is set to 0 (infinite) or 10 or 20. The setting does not have any effect.
So we use continue on error, but its not the best solution.
Is there a global timeout which ovverrules this setting?

Problem Unpacking Solution using PP 2.0 Tools

Hi folks - I'm having issues all of the sudden with unpacking my solution. A couple of oddities: this use to work without any issue and now for all of my pipelines using similar code, it's having an issue on the unpack step finding the file; additionally, this step works fine when using v0.0 of the task. First time Git user, so please talk to me like I'm a 3rd grader. Appreciate any help!

create set-connection-variables task to return data from service connection

The repo below has a task that creates a Dataverse connection string to the Environment based on the provided Service Connection and stores it in a pipeline secret variable. Having such a inbuilt capability inside the Power Platform Built Tools would prevent the need to maintain the same credentials twice to support script tasks that need to connect to the same Dataverse environment using tools such as Xrm.Data.PowerShell and others that support the connection string format.

https://github.com/remyblok/PowerPlatformBuildToolsEx

WhoAmI already validates the connection and sets additional variables such as BuildTools.EnvironmentID. I am proposing extending WhoAmI task to support returning additional values.

Asyncrhonous status showing % Complete incorrectly

The displayed progress for Asynchronous actions is not displaying the % complete correctly.

[ 'Solution Importing...' ]
[ 'Waiting for asynchronous operation d168bc76-052f-ed11-9db1-0022480b1b2c to complete with timeout of 05:00:00' ]
[ 'Processing asynchronous operation... execution time: 00:00:00 and 0.00% complete' ]
[ 'Processing asynchronous operation... execution time: 00:00:04 and 0.02% complete' ]
[ 'Processing asynchronous operation... execution time: 00:00:08 and 0.05% complete' ]
[ 'Processing asynchronous operation... execution time: 00:00:12 and 0.07% complete' ]
[ 'Processing asynchronous operation... execution time: 00:00:16 and 0.09% complete' ]
[ 'Processing asynchronous operation... execution time: 00:00:20 and 0.11% complete' ]
[ 'Processing asynchronous operation... execution time: 00:00:24 and 0.14% complete' ]
[ 'Processing asynchronous operation... execution time: 00:00:28 and 0.16% complete' ]
[ 'Processing asynchronous operation... execution time: 00:00:32 and 0.18% complete' ]
[ 'Processing asynchronous operation... execution time: 00:00:37 and 0.21% complete' ]
[ 'Processing asynchronous operation... execution time: 00:00:41 and 0.23% complete' ]
[ 'Processing asynchronous operation... execution time: 00:00:45 and 0.25% complete' ]
[ 'Processing asynchronous operation... execution time: 00:00:49 and 0.27% complete' ]
[ 'Processing asynchronous operation... execution time: 00:00:53 and 0.30% complete' ]
[ 'Processing asynchronous operation... execution time: 00:00:57 and 0.32% complete' ]
[ 'Processing asynchronous operation... execution time: 00:01:01 and 0.34% complete' ]
[ 'Asynchronous operation d168bc76-052f-ed11-9db1-0022480b1b2c successfully finished within 00:01:05.6509573' ]

The % Complete should be multiplied by 100 before displaying.

'PowerPlatformExportSolution@2' times out or fails when export async is true

Starting on 10/10/22, my export solution task has been timing out. Before this, my solutions were taking 2-5 mins to export, depending on size. Now they are timing out at 60 mins, but should never take that long to export.
I set the async to false and they export fine.
I'm running PPT v2.0.7.
Thanks!
Bryan

Virtual Machine scale set self hosted agent PackageManagement dependency

Using Virtual Machine scale sets for running our build pipelines in Azure means that the latest version of any powershell packages are also automatically installed.

5 days ago it looks like the PackageManagement package was updated to v1.4.8.1 PackageManagement

This means that all agents spun up on demand will have this new version of the powershell package installed.

This causes a problem with the Power Platform Tool Installer as it seems like it is explicitly expecting v1.4.7 to be installed instead.

As a workaround it's possible to run a separate power shelll script that will install PackageManagement v1.4.7 alongside so that the Tool Installer package can run, but long term this isn't really a proper fix

Power platform solution checker has started failing after upgrading to task version 2

We are using power platform tools extension and tasks with version 0 in azure DevOps
We were getting warning as "This v0 of PP-BT, using a Powershell implementation, has been deprecated!. Please consult https://aka.ms/pp-bt-migrate-to-v2 on how to migrate your pipelines to PP-BT v2."
We upgraded the task version to 2 and our pipeline started failing on task power platform solution checker with an error "Sorry, the app encountered a non-recoverable error and will need to terminate. The exception details have been captured and will be forwarded to the development team, if telemetry has been enabled. Exception Id: efc6a77a-9698-467d-bfff-cc6029954328, Exception Type: System.Net.Http.HttpRequestException"

PP Import Solution V 2.*

I changed the import Version to V2.
Now after some time receive this error:
Around 80 Minutes the import fails, seems it looses the connection while importing?

Processing asynchronous operation... execution time: 01:17:15 and 42.9202249592593% complete
Microsoft PowerPlatform CLI
Version: 1.17.5+gcbb58e8

Error: The HTTP request is unauthorized with client authentication scheme 'Anonymous'. The authentication header received from the server was 'Bearer authorization_uri=https://login.microsoftonline.com/975d243a-4e65-46df-b77f-8f73a893ca23/oauth2/authorize, resource_id=https://perigroup-integration.crm4.dynamics.com/'.
The HTTP request is unauthorized with client authentication scheme 'Anonymous'. The authentication header received from the server was 'Bearer authorization_uri=https://login.microsoftonline.com/975d243a-4e65-46df-b77f-8f73a893ca23/oauth2/authorize, resource_id=https://perigroup-integration.crm4.dynamics.com/'.
The remote server returned an error: (401) Unauthorized.

On prem install fails

On prem install fails with... "Permission section could not be loaded" No other information is provided. I had installed the prior, deprecated version and was starting to use it. I uninstalled the prior version to see if that would help...it did not. Now I cannot continue with my pipeline construction since I have no build tools installed. Please help...troy

Repo enhancement proposal | Suggest using sane labeling

The default GitHub labels are not sufficient when scaling an open-source project, IMO. Dave Lunny posted a great Medium article titled Sane GitHub Labels that provides a good overview for a better labelling system. see: Sane GitHub Labels | medium article

Here are some good examples in JSON format that can be applied using the GitHub API to standardize across projects.

jasonbellamy/git-label-packages

Thoughts? @microsoft/powerapps-isv-tools-contrib and others?

I believe this will help drive clarity on the type of issue/pr/other, status, etc.

On-premise Install Failing

On-premise install is failing. I have checked with our network team to confirm nothing is being blocked. I am looking for the download link for the VSIX to download upload the extension as suggested in Issue #177, but can't find that. Please help.

Add async and async wait time options to Publish Customizations

When running the Publish Customizations task, it fails if publishing takes longer than 4 minutes.
THe CLI has flags to run this async and add an async max wait time, so it'd be great if this could be exposed in the Task as well.

[ 'Calling pac cli inputs: solution publish' ]
[ 'Connected to...Contoso DEV' ]
[ 'Publishing All Customizations...' ]
[ 'Microsoft PowerPlatform CLI' ]
[ 'Version: 1.17.6+g3fe18a3' ]
[ '' ]
[ 'Error: The request channel timed out attempting to send after 00:04:00. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.' ]
[ '    The HTTP request to \'[https://contoso.crm4.dynamics.com/XRMServices/2011/Organization.svc/web?SDKClientVersion=9.2.47.9489\'](https://contoso.crm4.dynamics.com/XRMServices/2011/Organization.svc/web?SDKClientVersion=9.2.47.9489\%27) has exceeded the allotted timeout of 00:04:00. The time allotted to this operation may have been a portion of a longer timeout.' ]
[ '' ]
[ '' ]
[ 'Usage: pac solution publish [--async] [--max-async-wait-time]' ]
[ '' ]
[ '  --async                     Imports solution asynchronously (alias: -a)' ]
[ '  --max-async-wait-time       Max asynchronous wait time in minutes. Default value is 60 minutes (alias: -wt)' ]
[ '' ]
##[error]error: 1

ExcludeFiles option in PowerPlatformChecker does not exclude the file from being checked

ExcludeFiles option, does not exclude the file from the scanner:

Gives:

All in that one .msapp file.

Add Import/export data task

import/export data through power platform cli is possible but not through power platform build tools.
Would have build it myself but cannot contribute as i don't have access to the wrapper project

Include solution action in PowerPlatformDeployPackage task log

When using the Package Deployer task in the Azure DevOps Power Platform Build Tools the full package deployer logs are only output at the end of a run as a pipeline artifact and a less verbose log is written to the devops logs whilst the task is running.

It would be great if the package deployer decision on whether to install, skip, update or upgrade a solution was shown in the devops logs.

e.g. in the anonymised log snippet below we can only infer via the timings that something happened for ''ACME Solution Sol A' (but was it an upgrade or install?).

2022-09-28T01:02:43.1480136Z ##[section]Starting: PowerPlatformDeployPackage
2022-09-28T01:02:43.1598070Z ==============================================================================
2022-09-28T01:02:43.1598389Z Task         : Power Platform Deploy Package
2022-09-28T01:02:43.1598687Z Description  : Power Platform Deploy Package. Requires Windows build agent
2022-09-28T01:02:43.1598922Z Version      : 2.0.7
2022-09-28T01:02:43.1599083Z Author       : Microsoft
2022-09-28T01:02:43.1599324Z Help         : [More Info](https://aka.ms/buildtoolsdoc)
2022-09-28T01:02:43.1599614Z ==============================================================================
2022-09-28T01:02:43.4084115Z Discovered environment url from explicit input parameter 'Environment': $(BuildTools.EnvironmentUrl)
2022-09-28T01:02:43.4090169Z Discovered Azure DevOps variable expression that needs resolving: $(BuildTools.EnvironmentUrl) -> BuildTools.EnvironmentUrl
[ ... snip ... ]
2022-09-28T01:02:58.1122909Z [ '36. Dependency Found : Dependency on solution msdynce_CustomerServiceHubPatch found on target environment' ]
2022-09-28T01:02:58.1123520Z [ '37. Dependency Found : Dependency on solution BaseCustomControlsCore found on target environment' ]
2022-09-28T01:02:58.1124095Z [ '38. Dependency Found : Dependency on solution CustomControlsCore found on target environment' ]
2022-09-28T01:02:58.1124702Z [ '39. Dependency Found : Dependency on solution msdynce_ProductManagementPatch found on target environment' ]
2022-09-28T01:02:58.1272335Z [ 'Reading the solutions. Please wait.' ]
2022-09-28T01:02:58.1273473Z [ '1. Dependency Found : Dependency on solution msdynce_LeadManagement found on target environment' ]
2022-09-28T01:02:58.1274108Z [ '2. Dependency Found : Dependency on solution FieldService found on target environment' ]
2022-09-28T01:02:58.1274573Z [ 'Found 14 solutions.' ]
2022-09-28T01:02:58.1278156Z [ 'Found the detailed data to import.' ]
2022-09-28T01:02:58.1278733Z [ 'Checking configuration for Finance and Operations application' ]
2022-09-28T01:02:58.1324942Z [ 'Checking configuration for Finance and Operations application' ]
2022-09-28T01:02:58.1343869Z [ '' ]
2022-09-28T01:02:58.3226770Z [ 'Importing solutions' ]
2022-09-28T01:02:58.5405255Z [ 'Beginning load of solution ACME Solution Controls, version: 1.0.0.4.' ]
2022-09-28T01:02:58.8450329Z [ 'Beginning load of solution ACME Solution Controls OSS, version: 1.0.0.2.' ]
2022-09-28T01:02:59.1263568Z [ 'Beginning load of solution ACME Solution Legacy Controls, version: 1.0.0.1.' ]
2022-09-28T01:02:59.4232629Z [ 'Beginning load of solution ACME Solution Images, version: 1.0.0.4.' ]
2022-09-28T01:02:59.7201881Z [ 'Beginning load of solution ACME Solution Core, version: 1.0.0.45.' ]
2022-09-28T01:03:00.0169852Z [ 'Beginning load of solution ACME Solution Readings, version: 1.0.0.3.' ]
2022-09-28T01:03:00.2983185Z [ 'Beginning load of solution ACME Solution Sol A, version: 1.0.0.49.' ]
2022-09-28T03:01:10.4570930Z [ 'Beginning load of solution ACME Solution Sol B, version: 1.0.0.8.' ]
2022-09-28T03:01:10.7536829Z [ 'Beginning load of solution ACME Solution Sol C, version: 1.0.0.15.' ]
2022-09-28T03:01:11.0414198Z [ 'Beginning load of solution ACME Solution Sol D, version: 1.0.0.4.' ]
2022-09-28T03:01:11.3409011Z [ 'Beginning load of solution ACME Solution Sol E, version: 1.0.0.12.' ]
2022-09-28T03:01:11.6343037Z [ 'Beginning load of solution ACME Solution Sol F, version: 1.0.1.18.' ]
2022-09-28T03:01:11.9270838Z [ 'Beginning load of solution ACME Solution Sol E, version: 1.0.0.23.' ]
2022-09-28T03:01:12.2240285Z [ 'Beginning load of solution ACME Solution Sol F, version: 1.0.0.15.' ]
2022-09-28T03:01:12.5214303Z [ 'All solutions import complete.' ]
2022-09-28T03:01:12.5223218Z [ 'Installing Finance and Operations application' ]
2022-09-28T03:01:12.7330090Z [ 'Installation completed for Finance and Operations application' ]
2022-09-28T03:01:12.7336960Z [ 'Installing Finance and Operations application' ]
[ ... snip ... ]

i.e. It would be good if the snipped from the PD logs, e.g.

2022-09-28T03:01:10.7536829Z [ 'Beginning load of solution ACME Solution Sol C, version: 1.0.0.15.' ]  existing version [1.0.0.15]. Solution skipped.

2022-09-28T03:01:10.7536829Z [ 'Beginning load of solution ACME Solution Sol D, version: 1.0.0.15.' ]  existing version [1.0.0.14]. Upgrading solution.

2022-09-28T03:01:10.7536829Z [ 'Beginning load of solution ACME Solution Sol E, version: 1.0.0.15.' ]  existing version [1.0.0.14]. Upgrading solution.

2022-09-28T03:01:10.7536829Z [ 'Beginning load of solution ACME Solution Sol F, version: 1.0.0.15.' ]  solution not installed.  Installing solution.

Build Task "Power Platform Import Solution": New setting "Activate Plugin" suddenly available and unchecked per default

Hi,

the following setting has been added recently. I couldn´t find a proper announcement in the release notes. I´ve only recognized it after the deployment when all the plugin steps were inactive. So the way it is handled at the moment is a bit unfortunate.

Furthermore, the old setting "Activate processes (workflows) after import" seems to be redunant now.

Thanks!

Authentication fails if secret starts with '-'

Hi,

We recently had issues with authenticating in dataverse and found that the issue was the client secret starting with '-'

Example secret : -thisismysecret12353462456

We have resolved this by creating a new secret that does not start with '-'.

Though I would post here in case other happen to have same issue

Power Platform Solution Import Task v0.0.82 failing to import in the final PublishCustomizations part, even if tasks is running async

Hi there,
Eversince the upgrade last week from 0.0.77 to 0.0.82 our solution is not getting imported and consistently failing with this new Asynchronous import model.

We are getting this error
'Error: The request channel timed out while waiting for a reply after 00:04:00. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.' ]

The settings for your import task are
-AsyncOperation: true
-MaxAsyncWaitTime: '240' # 4 hours

Below are the full logs
Starting: Import xxxxxxxxxxx

Task : Power Platform Import Solution
Description : Power Platform Import Solution
Version : 0.0.82
Author : Microsoft
Help : More Info

Discovered environment url from explicit input parameter 'Environment': $(BuildTools.EnvironmentUrl)
Discovered Azure DevOps variable expression that needs resolving: $(BuildTools.EnvironmentUrl) -> BuildTools.EnvironmentUrl
Falling back to url from service connection, using: https://xxxxxxxxxxxxxxx/ /
[ 'Authentication successfully created.' ]
[ 'Validating connection...' ]
[ 'Connected to...xxxxxxxxxxxxxx' ]
[ ' * DATAVERSE https://xxxxxxxxxxxxxxx/ : *** xxxxx' ]
[ '' ]
[ 'The Authentication Result: Authentication successfully created.,Validating connection...,Connected to...xxxxxxx, * DATAVERSE https://xxxxxxxxxxxxxxxxx/ : *** xxx,' ]
[ 'Calling pac cli inputs: solution import --path D:\a\1\Self\Solutions\Unmanaged\Zip\xxxx.zip --async true --import-as-holding False --force-overwrite True --publish-changes true --skip-dependency-check True --convert-to-managed false --max-async-wait-time 240 --activate-plugins false' ]
[ 'Connected to...xxxxxxxxxxxxxx' ]
[ 'Solution Importing...' ]
[ 'Waiting for asynchronous operation 29ff8a16-22f9-ec11-82e7-00224815993b to complete with timeout of 04:00:00' ]
[ 'Processing asynchronous operation... execution time: 00:00:00 and 1% complete' ]
[ 'Processing asynchronous operation... execution time: 00:00:04 and 2% complete' ]
Processing asynchronous operation... execution time: 00:44:41 and 100% complete
Processing asynchronous operation... execution time: 00:44:45 and 100% complete
Processing asynchronous operation... execution time: 00:44:50 and 100% complete
Processing asynchronous operation... execution time: 00:44:54 and 100% complete
Processing asynchronous operation... execution time: 00:44:58 and 100% complete
Asynchronous operation 29ff8a16-22f9-ec11-82e7-00224815993b successfully finished within 00:45:02.3630415
Publishing All Customizations...
Microsoft PowerPlatform CLI
Version: 1.15.9+gf60807f

Error: The request channel timed out while waiting for a reply after 00:04:00. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.
The HTTP request to 'https://xxxxxxxxxxxxx/XRMServices/2011/Organization.svc/web?SDKClientVersion=9.2.47.7698' has exceeded the allotted timeout of 00:04:00. The time allotted to this operation may have been a portion of a longer timeout.
The operation has timed out

Usage: pac solution import [--path] [--activate-plugins] [--force-overwrite] [--skip-dependency-check] [--import-as-holding] [--publish-changes] [--convert-to-managed] [--async] [--max-async-wait-time] [--settings-file]

--path Path to solution zip file. If not specified, assumes the current folder is a cdsproj project. (alias: -p)
--activate-plugins Activate plug-ins and workflows on the solution (alias: -ap)
--force-overwrite Force an overwrite of unmanaged customizations (alias: -f)
--skip-dependency-check Skip dependency check against dependencies flagged as product update (alias: -s)
--import-as-holding Import the solution as a holding solution (alias: -h)
--publish-changes Publish your changes upon a successful import (alias: -pc)
--convert-to-managed Convert as Managed Solution (alias: -cm)
--async Imports solution asynchronously (alias: -a)
--max-async-wait-time Max asynchronous wait time in minutes. Default value is 60 minutes (alias: -wt)
--settings-file The .json file with the deployment settings for connection references and environment variables.

The same code ran like breeze on the previous version last week.

Importing a solution fails if the version number is the same

As the title - attempting to import a managed solution when the version is already installed causes the task to fail with an error. We need an "Skip if the same version" option on the import solution task.

Publish Customizations and Export Solution fails with 1.0.82

Hi,

We are having issues with publish customizations and export solution of the Power Platform Build Tools v1.0.82

Both tasks was working as expected with previous version. Nothing changed on our side. Only change is the PPBT version.

Output of Publish customizations task:
`
2022-07-01T10:56:40.7352156Z ##[section]Starting: Publish Customizations
2022-07-01T10:56:40.7460853Z ==============================================================================
2022-07-01T10:56:40.7461212Z Task : Power Platform Publish Customizations
2022-07-01T10:56:40.7461474Z Description : Power Platform Publish Customizations
2022-07-01T10:56:40.7461708Z Version : 0.0.82
2022-07-01T10:56:40.7461873Z Author : Microsoft
2022-07-01T10:56:40.7462114Z Help : More Info
2022-07-01T10:56:40.7462400Z ==============================================================================
2022-07-01T10:56:41.0028611Z Discovered environment url from explicit input parameter 'Environment': $(BuildTools.EnvironmentUrl)
2022-07-01T10:56:41.0030894Z Discovered Azure DevOps variable expression that needs resolving: $(BuildTools.EnvironmentUrl) -> BuildTools.EnvironmentUrl
2022-07-01T10:56:41.0037606Z Falling back to url from service connection, using: https://xxxxxxx.crm4.dynamics.com/
2022-07-01T10:56:44.1938044Z [ 'Microsoft PowerPlatform CLI' ]
2022-07-01T10:56:44.1939010Z [ 'Version: 1.15.9+gf60807f' ]
2022-07-01T10:56:44.1939392Z [ '' ]
2022-07-01T10:56:44.1940835Z [ 'Error: An unknown argument *** was passed.' ]
2022-07-01T10:56:44.1958073Z [ '' ]
2022-07-01T10:56:44.1958713Z [ 'Usage: pac auth create [--name] [--kind] [--url] [--username] [--password] [--applicationId] [--clientSecret] [--tenant] [--cloud] [--deviceCode]' ]
2022-07-01T10:56:44.1959273Z [ '' ]
2022-07-01T10:56:44.1959858Z [ ' --name The name you want to give to this authentication profile (maximum 12 characters) (alias: -n)' ]
2022-07-01T10:56:44.1960507Z [ ' --kind The kind of authentication profile you are creating, defaults to Dataverse (alias: -k)' ]
2022-07-01T10:56:44.1961083Z [ ' --url The resource URL to connect to (alias: -u)' ]
2022-07-01T10:56:44.1961677Z [ ' --username Optional: The username to authenticate with; shows AAD dialog if not specified (alias: -un)' ]
2022-07-01T10:56:44.1962326Z [ ' --password Optional: The password to authenticate with (alias: -p)' ]
2022-07-01T10:56:44.1963140Z [ ' --applicationId Optional: The application id to authenticate with (alias: -id)' ]
2022-07-01T10:56:44.1963743Z [ ' --clientSecret Optional: The client secret to authenticate with (alias: -cs)' ]
2022-07-01T10:56:44.1964310Z [ ' --tenant Tenant id if using application id & secret. (alias: -t)' ]
2022-07-01T10:56:44.1964852Z [ ' --cloud Optional: The cloud instance to authenticate with (alias: -ci)' ]
2022-07-01T10:56:44.1965402Z [ ' Values: Public, UsGov, UsGovHigh, UsGovDod, Mooncake' ]
2022-07-01T10:56:44.1965956Z [ ' --deviceCode Use the AAD DeviceCode flow for interactive login. (alias: -dc)' ]
2022-07-01T10:56:44.1966405Z [ '' ]
2022-07-01T10:56:44.3966682Z ##[error]error: 1
2022-07-01T10:56:44.3981336Z ##[error]failed: Microsoft PowerPlatform CLI
Version: 1.15.9+gf60807f

Error: An unknown argument *** was passed.

Usage: pac auth create [--name] [--kind] [--url] [--username] [--password] [--applicationId] [--clientSecret] [--tenant] [--cloud] [--deviceCode]

--name The name you want to give to this authentication profile (maximum 12 characters) (alias: -n)
--kind The kind of authentication profile you are creating, defaults to Dataverse (alias: -k)
--url The resource URL to connect to (alias: -u)
--username Optional: The username to authenticate with; shows AAD dialog if not specified (alias: -un)
--password Optional: The password to authenticate with (alias: -p)
--applicationId Optional: The application id to authenticate with (alias: -id)
--clientSecret Optional: The client secret to authenticate with (alias: -cs)
--tenant Tenant id if using application id & secret. (alias: -t)
--cloud Optional: The cloud instance to authenticate with (alias: -ci)
Values: Public, UsGov, UsGovHigh, UsGovDod, Mooncake
--deviceCode Use the AAD DeviceCode flow for interactive login. (alias: -dc)

2022-07-01T10:56:45.3012499Z [ 'Authentication profiles and token cache removed' ]
2022-07-01T10:56:45.4486973Z [ 'The Clear Authentication Result: Authentication profiles and token cache removed' ]
2022-07-01T10:56:45.4509722Z ##[error]Error: Microsoft PowerPlatform CLI
Version: 1.15.9+gf60807f

Error: An unknown argument *** was passed.

Usage: pac auth create [--name] [--kind] [--url] [--username] [--password] [--applicationId] [--clientSecret] [--tenant] [--cloud] [--deviceCode]

2022-07-01T10:56:45.4560151Z ##[section]Finishing: Publish Customizations
`

Output of export solution task:
`
2022-07-01T12:46:14.0270383Z ##[section]Starting: Export Unmanaged Solution
2022-07-01T12:46:14.0395171Z ==============================================================================
2022-07-01T12:46:14.0395572Z Task : Power Platform Export Solution
2022-07-01T12:46:14.0395823Z Description : Power Platform Export Solution
2022-07-01T12:46:14.0396026Z Version : 0.0.82
2022-07-01T12:46:14.0396257Z Author : Microsoft
2022-07-01T12:46:14.0396521Z Help : More Info
2022-07-01T12:46:14.0396889Z ==============================================================================
2022-07-01T12:46:14.3107405Z Discovered environment url from explicit input parameter 'Environment': $(BuildTools.EnvironmentUrl)
2022-07-01T12:46:14.3114526Z Discovered Azure DevOps variable expression that needs resolving: $(BuildTools.EnvironmentUrl) -> BuildTools.EnvironmentUrl
2022-07-01T12:46:14.3124634Z Falling back to url from service connection, using: https://xxxxxxx.crm4.dynamics.com/
2022-07-01T12:46:17.2887543Z [ 'Microsoft PowerPlatform CLI' ]
2022-07-01T12:46:17.2887946Z [ 'Version: 1.15.9+gf60807f' ]
2022-07-01T12:46:17.2888220Z [ '' ]
2022-07-01T12:46:17.2888933Z [ 'Error: An unknown argument *** was passed.' ]
2022-07-01T12:46:17.2889213Z [ '' ]
2022-07-01T12:46:17.2889659Z [ 'Usage: pac auth create [--name] [--kind] [--url] [--username] [--password] [--applicationId] [--clientSecret] [--tenant] [--cloud] [--deviceCode]' ]
2022-07-01T12:46:17.2890126Z [ '' ]
2022-07-01T12:46:17.2890504Z [ ' --name The name you want to give to this authentication profile (maximum 12 characters) (alias: -n)' ]
2022-07-01T12:46:17.2891056Z [ ' --kind The kind of authentication profile you are creating, defaults to Dataverse (alias: -k)' ]
2022-07-01T12:46:17.2891526Z [ ' --url The resource URL to connect to (alias: -u)' ]
2022-07-01T12:46:17.2891998Z [ ' --username Optional: The username to authenticate with; shows AAD dialog if not specified (alias: -un)' ]
2022-07-01T12:46:17.2892513Z [ ' --password Optional: The password to authenticate with (alias: -p)' ]
2022-07-01T12:46:17.2892989Z [ ' --applicationId Optional: The application id to authenticate with (alias: -id)' ]
2022-07-01T12:46:17.2893463Z [ ' --clientSecret Optional: The client secret to authenticate with (alias: -cs)' ]
2022-07-01T12:46:17.2894022Z [ ' --tenant Tenant id if using application id & secret. (alias: -t)' ]
2022-07-01T12:46:17.2894478Z [ ' --cloud Optional: The cloud instance to authenticate with (alias: -ci)' ]
2022-07-01T12:46:17.2894911Z [ ' Values: Public, UsGov, UsGovHigh, UsGovDod, Mooncake' ]
2022-07-01T12:46:17.2895367Z [ ' --deviceCode Use the AAD DeviceCode flow for interactive login. (alias: -dc)' ]
2022-07-01T12:46:17.2895710Z [ '' ]
2022-07-01T12:46:17.2926528Z ##[error]error: 1
2022-07-01T12:46:17.2940731Z ##[error]failed: Microsoft PowerPlatform CLI
Version: 1.15.9+gf60807f

Error: An unknown argument *** was passed.

Usage: pac auth create [--name] [--kind] [--url] [--username] [--password] [--applicationId] [--clientSecret] [--tenant] [--cloud] [--deviceCode]

2022-07-01T12:46:18.1567980Z [ 'Authentication profiles and token cache removed' ]
2022-07-01T12:46:18.3078511Z [ 'The Clear Authentication Result: Authentication profiles and token cache removed' ]
2022-07-01T12:46:18.3160446Z ##[error]Error: Microsoft PowerPlatform CLI
Version: 1.15.9+gf60807f

Error: An unknown argument *** was passed.

Usage: pac auth create [--name] [--kind] [--url] [--username] [--password] [--applicationId] [--clientSecret] [--tenant] [--cloud] [--deviceCode]

2022-07-01T12:46:18.3207175Z ##[section]Finishing: Export Unmanaged Solution
`

export and import portal configuration task not available in Azure devops

We need Export and import portal configuration task are required in azure devops pipeline. we already installed power platform build tools but no use, unable to find the export and import configuration tasks

Power portal extension in dev ops fails on Power Portal Download task

Hi. I have been struggling with this for couple of hours now. When I execute dev ops pipeline it fails on the task of downloading portal.

Extension is being installed successfully, connection is verified with "who am I".

The details of the errors on the task:

The portion that was cut on the screenshot:

"Sorry, the app encountered a non recoverable error and will need to terminate. The exception details have been captured and will be forwarded to the development team, if telemetry has been enabled. Exception Id: 2c3cfa5d-7676-493d-810d-529054d8a0ac, Exception Type: System.ArgumentNullException"

When command is tested in VS Code it works fine. The portal id is correct.

I found similar problem here:
https://powerusers.microsoft.com/t5/Power-Apps-Pro-Dev-ISV/Error-when-using-Microsoft-Power-Platform...
I have tried the last suggestion and it is still not executing properly.

I hope someone is able to assist me.

Kind Regards
Piotr

PS: I can share full logs for failed pipeline with the person who will be taking look into the issue. Please message me.

Power Platform checker fails with new Build Task update

Hello,

since the update for the BuildTasks we are facing an issue with Power Platform Checker.
It suddenly stopped working:

The task configuration wasn't changed and does not use custom endpoint although the error message states so.

Unpacking solution fails with NullRefException when unpacking a .msapp

Greetings.

After working for a couple of weeks now with the folks over on the coe-starter-kit side of the fence, I am reaching out in hopes that someone can assist me in troubleshooting issues with unpacking/packing solutions containing Canvas Apps in my Power Platform ALM pipelines.

We were hopeful that the September release of the ALM accelerator would fix issues related to packing and unpacking apps as the newest release transitioned from using the PP language tooling to the Power Platform Built Tools tasks, but my failures are persisting. What I'm trying to determine now is if this is an issue with my solution packages (this fails on all solutions in the environment in which I am attempting to commit from), or if this is an issue with the build tasks.

In all scenarios, I receive the error shown in the screenshot below. In the ALM accelerator August hotfix release, committing to source control for these solutions worked, but packing the apps to deploy downstream would result in this failure. In the September release, I am seeing it when unpacking the solutions to my repo during commit.

Please let me know what other information I can provide in order to resolve this. Thanks.

Portal Download fails because file exist. No overwrite option available

Missing overwrite option on portal download

[ 'Microsoft PowerPlatform CLI' ]
[ 'Version: 1.17.5+gcbb58e8' ]
[ '' ]
[ 'Error: File \\?\D:\a\1\s\portalSrc\*******\website.yml already exist. provide -o true argument to overwrite the content' ]
[ '' ]

--overwrite Portal website content to overwrite (alias: -o)

ACTION REQUIRED: Microsoft needs this private repository to complete compliance info

There are open compliance tasks that need to be reviewed for your powerplatform-build-tools repo.

Action required: 1 compliance task

To bring this repository to the standard required for 2021, we require administrators of this and all Microsoft GitHub repositories to complete a small set of tasks within the next 60 days. This is critical work to ensure the compliance and security of your microsoft GitHub organization.

Please take a few minutes to complete the task at: https://repos.opensource.microsoft.com/orgs/microsoft/repos/powerplatform-build-tools/compliance

No repository maintainers are set. The Open Source Maintainers are the decision-makers and actionable owners of the repository, irrespective of administrator permission grants on GitHub.

You can close this work item once you have completed the compliance tasks, or it will automatically close within a day of taking action.

If you no longer need this repository, it might be quickest to delete the repo, too.

GitHub inside Microsoft program information

More information about GitHub inside Microsoft and the new GitHub AE product can be found at https://aka.ms/gim or by contacting [email protected]

FYI: current admins at Microsoft include @JimDaly, @lajusp, @MikeStall, @MattB-msft, @davidjenni

Power Platform Export Solution command does not provide a parameter that allows for overwriting the solution file.

WE had created a pipeline that users the PowerPlatform "Export" task to export a specific solution and store it in source control. Since the update to the @2 version, our pipeline "broke" when attempting to export the solution because it cannot overwrite the local solution file on the file system (cloned on the Build Agent from source control earlier in the pipeline).

There does not appear to be a parameter in the pipeline task that corresponds with the -overwrite flag in the underlying CLI command.

I was forced to rollback to the @0 version of the Power Platform Tools due to this issue.

Starting: PowerPlatformExportSolution

Task : Power Platform Export Solution
Description : Power Platform Export Solution
Version : 2.0.5
Author : Microsoft
Help : More Info

##[debug]authenticationType=PowerPlatformEnvironment
##[debug]PowerPlatformEnvironment=f7ba5070-20b5-47df-a1ad-cb61bcbb43a7
##[debug]f7ba5070-20b5-47df-a1ad-cb61bcbb43a7=https://mpegla-test.crm.dynamics.com/
Falling back to url from service connection, using: https://mpegla-test.crm.dynamics.com/
##[debug]Falling back to url from service connection, using: https://mpegla-test.crm.dynamics.com/
##[debug]POWERPLATFORMTOOLS_PACCLIPATH=D:\a_tasks\PowerPlatformToolInstaller_8015465b-f367-4ec4-8215-8edf682574d3\2.0.5\bin
[ 'authN to env: authType=UserPass; cloudInstance: Public; envUrl: https://mpegla-test.crm.dynamics.com/' ]
##[debug]command: D:\a_tasks\PowerPlatformToolInstaller_8015465b-f367-4ec4-8215-8edf682574d3\2.0.5\bin\pac\tools\pac.exe, first arg of 10: auth
[ ''' authenticated successfully.' ]
[ 'Validating connection...' ]
[ 'Connected to...MPEGLA-TEST' ]
[ 'Authentication profile created' ]
[ ' * DATAVERSE https://mpegla-test.crm.dynamics.com/ : *** Public' ]
[ '' ]
[ 'The Authentication Result: '' authenticated successfully.,Validating connection...,Connected to...MPEGLA-TEST,Authentication profile created, * DATAVERSE https://mpegla-test.crm.dynamics.com/ : *** Public,' ]

[ 'Calling pac cli inputs: solution export --name MPEGLAEnvironmentVariables --path D:\a\1\s\Solutions\MPEGLAEnvironmentVariables_unmanaged.zip --managed false --async true --max-async-wait-time 180' ]
##[debug]command: D:\a_tasks\PowerPlatformToolInstaller_8015465b-f367-4ec4-8215-8edf682574d3\2.0.5\bin\pac\tools\pac.exe, first arg of 12: solution
[ 'Microsoft PowerPlatform CLI' ]
[ 'Version: 1.17.6+g3fe18a3' ]
[ '' ]
[ 'Error: Solution output file D:\a\1\s\Solutions\MPEGLAEnvironmentVariables_unmanaged.zip already exists.' ]
[ '' ]
[ 'Usage: pac solution export --path --name [--managed] [--include] [--async] [--max-async-wait-time] [--overwrite] [--targetversion]' ]
[ '' ]
[ ' --path Path where the exported solution zip file will be written (alias: -p)' ]
[ ' --name The name of the solution to be exported (alias: -n)' ]
[ ' --managed Whether the solution should be exported as a managed solution (alias: -m)' ]
[ ' --include Which settings should be included in the solution being exported (alias: -i)' ]
[ ' Values: autonumbering, calendar, customization, emailtracking, externalapplications, general, isvconfig, marketing, outlooksynchronization, relationshiproles, sales' ]
[ ' --async Exports solution asynchronously (alias: -a)' ]
[ ' --max-async-wait-time Max asynchronous wait time in minutes. Default value is 60 minutes (alias: -wt)' ]
[ ' --overwrite The exported solution file can overwrite the solution zip file on the local file system. (alias: -ow)' ]
[ ' --targetversion (deprecated) The version that the exported solution will support (alias: -v)' ]
[ '' ]
##[error]error: 1
##[debug]Processed: ##vso[task.issue type=error;]error: 1
##[error]failed: Microsoft PowerPlatform CLI

Update set-connection-variables task to have outputVariables in task.json

Empty Environment Variable Secret Values in Deployment Settings

Hey all,
Wondering if this is a bug or expected behavior.

What we've noticed is when we generate the deployment settings for the import build task if we leave the value for a secret environment variable blank it throws an exception importing the solution.

The workaround is to remove the node for the secret EV completely from the deployment settings, but this isn't consistent with other environment variables which you can simply provide a blank value and they will be ignored (i.e. won't throw an error but won't set any value on import).

We've added some logic to explicitly remove these secret EVs with empty values in our pipelines before import, but can't see any reason not to treat a blank / empty value the same way as if the environment variable isn't included at all in the deployment settings json.

e.g.

I have a solution that only contains a single EV of type secret and this deployment settings json works

{
    "EnvironmentVariables":  [
                             ],
    "ConnectionReferences":  [

                             ]
}

But the following throws the exception below

{
    "EnvironmentVariables":  [
                                 {
                                     "SchemaName":  "mf_SecretVariable",
                                     "Value":  ""
                                 }
                             ],
    "ConnectionReferences":  [

                             ]
}

<OrganizationServiceFault xmlns:i="[http://www.w3.org/2001/XMLSchema-instance"](http://www.w3.org/2001/XMLSchema-instance%22) xmlns="[http://schemas.microsoft.com/xrm/2011/Contracts">](http://schemas.microsoft.com/xrm/2011/Contracts%22%3E)
  <ActivityId>a07918d9-a0f2-4ed2-a26e-645d47f5bd19</ActivityId>
  <ErrorCode>-2147220970</ErrorCode>
  <ErrorDetails xmlns:d2p1="[http://schemas.datacontract.org/2004/07/System.Collections.Generic">](http://schemas.datacontract.org/2004/07/System.Collections.Generic%22%3E)
    <KeyValuePairOfstringanyType>
      <d2p1:key>ApiExceptionSourceKey</d2p1:key>
      <d2p1:value xmlns:d4p1="[http://www.w3.org/2001/XMLSchema"](http://www.w3.org/2001/XMLSchema%22) i:type="d4p1:string">Plugin/Microsoft.Dynamics.EnvironmentVariables.Plugins.CreateVariableValue</d2p1:value>
    </KeyValuePairOfstringanyType>
    <KeyValuePairOfstringanyType>
      <d2p1:key>ApiOriginalExceptionKey</d2p1:key>
      <d2p1:value xmlns:d4p1="[http://www.w3.org/2001/XMLSchema"](http://www.w3.org/2001/XMLSchema%22) i:type="d4p1:string">Microsoft.Xrm.Sdk.InvalidPluginExecutionException: Null or empty secret reference value found. ---&gt; Microsoft.Xrm.Sdk.InvalidPluginExecutionException: Null or empty secret reference value found.
   at Microsoft.Dynamics.EnvironmentVariables.Plugins.EnvironmentVariableUtil.ValidateSecretVariableValue(Entity definition, Entity variableValue, IPluginExecutionContext context, IServiceProvider serviceProvider)
   at Microsoft.Dynamics.EnvironmentVariables.Plugins.CreateVariableValue.Execute(IServiceProvider serviceProvider)
   at Microsoft.Crm.Extensibility.V5PluginProxyStep.ExecuteInternal(PipelineExecutionContext context)
   at Microsoft.Crm.Extensibility.VersionedPluginProxyStepBase.Execute(PipelineExecutionContext context)
   --- End of inner exception stack trace ---
   at Microsoft.Crm.Extensibility.VersionedPluginProxyStepBase.Execute(PipelineExecutionContext context)
   at Microsoft.Crm.Extensibility.PipelineInstrumentationHelper.Execute(Boolean instrumentationEnabled, String stopwatchName, ExecuteWithInstrumentation action, PipelineExecutionContext context)
   at Microsoft.Crm.Extensibility.Pipeline.&lt;&gt;c__DisplayClass3_0.&lt;RunStep&gt;b__0()</d2p1:value>
    </KeyValuePairOfstringanyType>...

Publish-pipeline-artifact fails with CLI for managed solution but still okay with Powershell

Pipeline worked for 9 months then upgraded from Power shell to CLI.
Now publish only works for Unmanaged but fails for managed I raised a full ticket here
https://developercommunity.visualstudio.com/t/Publish-Pipeline-Artifact-Power-Platfor/10170869
If I untick the 'managed' box it worked, how weird is that?
Now reverted back to Powershell and all okay but I have no hair left.
Cheers, Richard

Summary-Unmanaged-okay-managed-fails.txt

Configurable polling interval for asynchronous operation status while overwriting old status line

The spam of operation status log entries is really annoying. We are having customers were solution import and upgrade are taking several hours. A four second polling interval for the status update is not necessary.

Therefore I would really appreciate either of both of two solutions:

Overwrite the last status line entry with the new one. The values changing in the same line would still indicate its alive.
A configurable setting for the interval to poll for the current status. If it takes like 3 hours to import and upgrade a big solution I really would like to not poll for it every 4 seconds. This adds up to 900 lines of status log lines for just one hour.

DeployPackage fails to load package dll - "Could not load assembly CrmPackageExtentionBase"

The changes are not backward compatible. Our pipelines started failing as soon as you are making chnages. It failed on June 14 as well. that worked after the changes were reverted. It will be good, if you allow the clients to control the version so that they can work out by keeping old version while you guys try to test out the new changes. As of now, it breaks our PROD systems.

error: 1
failed: Reading the import configuration. Please wait.
Failed to Load the Import Configuration : Config File Missing
Failed to Load the Import Configuration : Config File Missing
Microsoft PowerPlatform CLI
Version: 1.15.9+gf60807f
Error: Failed to Load the Import Configuration : Config File Missing
Usage: pac package deploy [--logFile] [--logConsole] --package
--logFile Log file path (alias: -lf)
--logConsole Output log to console (alias: -c)
--package path to a package dll or zip file with a package (alias: -p)
1 more errors. Click on expand view in the context menu to view complete logs.

The Power Platform Build Tools are not backwards compatible

It seems impossible to point to an older version of the Power Platform Build Tools or I am missing something!

The latest version (1.0.82) has broken our pipelines, and we have an end of financial year release that is failing. We simply want to use the previous stable version of the task (1.0.77) that was successfully tested everything against, but how is this done - is it even possible?

I read the following in regards to versioning in another issue which has been raised recently, but it doesn't seem to be true or not documented properly:

RE: versioning: It was a conscious choice by the team, as it has the least amount of pain on existing customers. Since both the old PS based and the pac CLI based versions do depend on having an initial ToolInstaller, there is no mix and match between e.g. @0 ToolInstaller and a @1 DeployPackage task.

We had similar issues with this task for the 1.0.76 release which was fixed by 1.0.77 on the same day but still caused issues for us.

Async Import Times out and Sync gives error: There is no active transaction

Hi,

As of 17th October, we are having problems with the Import of our solutions.
We had it successfully running as a Async Import for a while now.

I tried changing it to a sync import but then we get the following error message: There is no active transaction. After exactly 3 minutes.

Details:

Using the latest version of PPT 2.0.7.
Wave 2 update was pushed around that date by MS (Could be coincidence)
Our main solution is massive and takes around 1.5 hours to import, now it times out after 6 hours and 15 minutes (i've set the maximum wait time very high).
We have 2 smaller solutions that takes around 2 minutes these work fine
It's an import without Publish, we publish in the following step.

Thanks in advance!

tasklog_8 (2).log

Power Platform Deploy Package tool - Failing since 0.0.82

Failing to use the Power Platform Deploy Package tool which used to work in previous 0.0.41 release and the package successfully deploys using the package deployer tool manually.

Error is: Failed to Load the Import Configuration : Config File Missing

2022-07-01T16:32:57.5087581Z ==============================================================================
2022-07-01T16:32:57.5088023Z Task : Power Platform Deploy Package
2022-07-01T16:32:57.5088320Z Description : Power Platform Deploy Package
2022-07-01T16:32:57.5088574Z Version : 0.0.82
2022-07-01T16:32:57.5088782Z Author : Microsoft
2022-07-01T16:32:57.5089066Z Help : More Info
2022-07-01T16:32:57.5089442Z ==============================================================================
2022-07-01T16:32:57.7749980Z Discovered environment url from explicit input parameter 'Environment': $(BuildTools.EnvironmentUrl)
2022-07-01T16:32:57.7760957Z Discovered Azure DevOps variable expression that needs resolving: $(BuildTools.EnvironmentUrl) -> BuildTools.EnvironmentUrl
2022-07-01T16:32:57.7772941Z Falling back to url from service connection, using: **********************************
2022-07-01T16:32:59.7911277Z [ 'Authentication successfully created.' ]
2022-07-01T16:32:59.7912649Z [ 'Validating connection...' ]
2022-07-01T16:33:00.4516079Z [ 'Connected to...a365-rel-fieldservice' ]
2022-07-01T16:33:00.5661548Z [ ' * DATAVERSE ********************************** : *** Public' ]
2022-07-01T16:33:00.5662187Z [ '' ]
2022-07-01T16:33:00.7467811Z [ 'The Authentication Result: Authentication successfully created.,Validating connection...,Connected to..**********************************, * DATAVERSE ********************************** : *** Public,' ]
2022-07-01T16:33:00.7496909Z [ 'Deploying package: C:\agent\_work\r20\a\extracted\A365forDeviceServicePackage.dll' ]
2022-07-01T16:33:00.7514144Z [ 'Calling pac cli inputs: package deploy --package C:\agent\_work\r20\a\extracted\A365forDeviceServicePackage.dll --logFile C:\agent\_work\r20\a\out\DeployPackage\deploy-package\A365forDeviceServicePackage-2022-07-01T16-33-00.735Z.log' ]
2022-07-01T16:33:02.8053484Z [ 'Reading the import configuration. Please wait.' ]
2022-07-01T16:33:02.8054911Z [ 'Failed to Load the Import Configuration : Config File Missing' ]
2022-07-01T16:33:02.8082593Z [ 'Failed to Load the Import Configuration : Config File Missing' ]
2022-07-01T16:33:02.8497684Z [ 'Microsoft PowerPlatform CLI' ]
2022-07-01T16:33:02.8499104Z [ 'Version: 1.15.9+gf60807f' ]
2022-07-01T16:33:02.8500183Z [ '' ]
2022-07-01T16:33:02.8512553Z [ 'Error: Failed to Load the Import Configuration : Config File Missing' ]
2022-07-01T16:33:02.8512956Z [ '' ]
2022-07-01T16:33:02.8517181Z [ 'Usage: pac package deploy [--logFile] [--logConsole] --package' ]
2022-07-01T16:33:02.8517930Z [ '' ]
2022-07-01T16:33:02.8518534Z [ ' --logFile Log file path (alias: -lf)' ]
2022-07-01T16:33:02.8519265Z [ ' --logConsole Output log to console (alias: -c)' ]
2022-07-01T16:33:02.8520305Z [ ' --package path to a package dll or zip file with a package (alias: -p)' ]
2022-07-01T16:33:02.8521136Z [ '' ]
2022-07-01T16:33:03.0408626Z ##[error]error: 1
2022-07-01T16:33:03.0423353Z ##[error]failed: Reading the import configuration. Please wait.
Failed to Load the Import Configuration : Config File Missing
Failed to Load the Import Configuration : Config File Missing
Microsoft PowerPlatform CLI
Version: 1.15.9+gf60807f

Error: Failed to Load the Import Configuration : Config File Missing

Usage: pac package deploy [--logFile] [--logConsole] --package

--logFile Log file path (alias: -lf)
--logConsole Output log to console (alias: -c)
--package path to a package dll or zip file with a package (alias: -p)

2022-07-01T16:33:04.0077024Z [ 'Authentication profiles and token cache removed' ]
2022-07-01T16:33:04.1815274Z [ 'The Clear Authentication Result: Authentication profiles and token cache removed' ]
2022-07-01T16:33:04.1823701Z ##[error]Error: Reading the import configuration. Please wait.
Failed to Load the Import Configuration : Config File Missing
Failed to Load the Import Configuration : Config File Missing
Microsoft PowerPlatform CLI
Version: 1.15.9+gf60807f

Error: Failed to Load the Import Configuration : Config File Missing

Usage: pac package deploy [--logFile] [--logConsole] --package

--logFile Log file path (alias: -lf)
--logConsole Output log to console (alias: -c)
--package path to a package dll or zip file with a package (alias: -p)

Issue with Process CanvasApps in Power Platform Unpack Solution

Hey All,
I've run across an interesting issue with the Process CanvasApps flag in the new Unpack Solution command. What I've noticed, and been able to reproduce in a generic pipeline, is that while the first time you unpack a solution the source files are created and can be committed to source control, the second time the unpack runs and commits the unpacked canvas app is deleted. The following YAML is what I'm using to test. The result is you can see the unpacked Canvas App in the Initial Commit and that it's deleted in the Second Commit. Let me know if I can provide additional information.

pool:
  name: Azure Pipelines
steps:
- powershell: |
   git config user.email "user.onmicrosoft.com"
   git config user.name "User Name"
   git checkout origin/main --track
   git checkout -b 'test' 'refs/heads/main'
   
  displayName: 'PowerShell Script'

- task: microsoft-IsvExpTools.PowerPlatform-BuildTools.tool-installer.PowerPlatformToolInstaller@0
  displayName: 'Power Platform Tool Installer '

- task: microsoft-IsvExpTools.PowerPlatform-BuildTools.export-solution.PowerPlatformExportSolution@0
  displayName: 'Power Platform Export Solution Unmanaged'
  inputs:
    authenticationType: PowerPlatformSPN
    PowerPlatformSPN: 'https://***.crm.dynamics.com/'
    SolutionName: ALMAcceleratorSampleSolution
    SolutionOutputFile: 'ALMAcceleratorSampleSolution_unmanaged.zip'

- task: microsoft-IsvExpTools.PowerPlatform-BuildTools.export-solution.PowerPlatformExportSolution@0
  displayName: 'Power Platform Export Solution Managed'
  inputs:
    authenticationType: PowerPlatformSPN
    PowerPlatformSPN: 'https://***.crm.dynamics.com/'
    SolutionName: ALMAcceleratorSampleSolution
    SolutionOutputFile: 'ALMAcceleratorSampleSolution_managed.zip'

- task: microsoft-IsvExpTools.PowerPlatform-BuildTools.unpack-solution.PowerPlatformUnpackSolution@0
  displayName: 'Power Platform Unpack Solution '
  inputs:
    SolutionInputFile: 'ALMAcceleratorSampleSolution_unmanaged.zip'
    SolutionTargetFolder: 'ALMAcceleratorSampleSolution_unpacked'
    ProcessCanvasApps: true

- powershell: |
   Write-Host "This is a script that could use $env:SYSTEM_ACCESSTOKEN"
   git add --all
   git commit -m "Initial Commit"
   git -c http.extraheader="AUTHORIZATION: bearer $env:SYSTEM_ACCESSTOKEN" push origin 'test'
  displayName: 'PowerShell Script'
  env:
    SYSTEM_ACCESSTOKEN: $(System.AccessToken)

- task: microsoft-IsvExpTools.PowerPlatform-BuildTools.unpack-solution.PowerPlatformUnpackSolution@0
  displayName: 'Power Platform Unpack Solution 2'
  inputs:
    SolutionInputFile: 'ALMAcceleratorSampleSolution_unmanaged.zip'
    SolutionTargetFolder: 'ALMAcceleratorSampleSolution_unpacked'
    ProcessCanvasApps: true

- powershell: |
   git add --all
   git commit -m "Second Commit"
   git -c http.extraheader="AUTHORIZATION: bearer $env:SYSTEM_ACCESSTOKEN" push origin 'test'
  displayName: 'PowerShell Script 2'
  env:
    SYSTEM_ACCESSTOKEN: $(System.AccessToken)

Power platform solution checker fails with "Exceeded the max wait"

Since v0.0.77 (and still in 0.0.85) we often (not always) are getting the following error in the output logs

##[error]Exceeded the max wait. Try running again with an increased SecondsBetweenChecks and MaxStatusChecks.

There is no option for the task to extend the wait time, except the default timeout built into any devops task (which has no affect). The timeout seems to be locked at 5min, which is probably fine since when the check works on the same solution it takes about 30seconds. The logs saved in the output folder do not indicate any other error.

I've attached the an image showing output of unsuccessful check and successful next to each other. Both checking the same solution

Portal Upload fails due to pre-update plug-in

Recently, when uploading a portal to an environment with a community portal installed, the upload failed due to a pre-update plugin. This cause the site setting to NOT be associated with the website.

The plugin is:
Microsoft.Dynamics.Community.Plugins.SiteSetting_PreUpdate: Update of adx_sitesetting

With the error:

Exception Message: Object reference not set to an instance of an object.

ErrorCode: -2147220891
HexErrorCode: 0x80040265

ErrorDetails:
ApiExceptionSourceKey: Plugin/Microsoft.Crm.ObjectModel.CustomBusinessEntityService
ApiStepKey: 41952d10-4e53-ea11-a814-000d3a3b1e97
ApiDepthKey: 1
ApiActivityIdKey: 2147f1bc-dc07-48b4-86bf-279b2e74e528
ApiPluginSolutionNameKey: System
ApiStepSolutionNameKey: System
ApiExceptionCategory: ClientError
ApiExceptionMessageName: IsvAborted
ApiExceptionHttpStatusCode: 400
OperationStatus: 0
SubErrorCode: -2146233088
Plugin:
PluginTrace: [Microsoft.Dynamics.Community.Plugins: Microsoft.Dynamics.Community.Plugins.SiteSetting_PreUpdate]
[68a2d42a-8bf1-eb11-bad6-000d3af6d0a1: Microsoft.Dynamics.Community.Plugins.SiteSetting_PreUpdate: Update of adx_sitesetting]
CorrelationId:78e3514a-7ede-4327-bcff-376667b2b006 Entered Microsoft.Dynamics.Community.Plugins.SiteSetting_PreUpdate.Execute()
CorrelationId:78e3514a-7ede-4327-bcff-376667b2b006 Exception: System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.Dynamics.Community.Plugins.SiteSetting_PreUpdate.ExecuteCrmPlugin(LocalPluginContext context)
at Microsoft.Dynamics.Community.Plugins.PluginBase.Execute(IServiceProvider serviceProvider)
CorrelationId:78e3514a-7ede-4327-bcff-376667b2b006 Exiting Microsoft.Dynamics.Community.Plugins.SiteSetting_PreUpdate.Execute()

TraceText:
[Microsoft.Dynamics.Community.Plugins: Microsoft.Dynamics.Community.Plugins.SiteSetting_PreUpdate]
[68a2d42a-8bf1-eb11-bad6-000d3af6d0a1: Microsoft.Dynamics.Community.Plugins.SiteSetting_PreUpdate: Update of adx_sitesetting]
CorrelationId:78e3514a-7ede-4327-bcff-376667b2b006 Entered Microsoft.Dynamics.Community.Plugins.SiteSetting_PreUpdate.Execute()
CorrelationId:78e3514a-7ede-4327-bcff-376667b2b006 Exception: System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.Dynamics.Community.Plugins.SiteSetting_PreUpdate.ExecuteCrmPlugin(LocalPluginContext context)
at Microsoft.Dynamics.Community.Plugins.PluginBase.Execute(IServiceProvider serviceProvider)
CorrelationId:78e3514a-7ede-4327-bcff-376667b2b006 Exiting Microsoft.Dynamics.Community.Plugins.SiteSetting_PreUpdate.Execute()

Turned off the plugin and the upload worked great.

Would be great to know if turning off plugins is available now or will be in the future.

Large Package "timing out" and falls into an infinite loop of Beginning queueing up UpdateRibbonClientMetadata job"

First noticed when the Azure DevOps tasks moved from PowerShell to using PAC to do the installs, but I've recreated the issue in the base PAC.

We have a package with some very large solutions, which takes about 90 minutes to completely install. Due to sizing issues, we are already using requiredimportmode="async" to prevent the install from failing due to stale progress (the percent complete holds for a LONG time); but the latest version seems to time out almost exactly after an hour and moves into a loop of Beginning queuing up UpdateRibbonClientMetadata job before ending with a StackOverflowException

Log from the DevOps pipeline below:

2022-07-05T08:07:33.2162340Z ##[section]Starting: Installing ***
2022-07-05T08:07:33.2409278Z ==============================================================================
2022-07-05T08:07:33.2409664Z Task         : Power Platform Deploy Package
2022-07-05T08:07:33.2409904Z Description  : Power Platform Deploy Package
2022-07-05T08:07:33.2410125Z Version      : 0.0.84
2022-07-05T08:07:33.2410293Z Author       : Microsoft
2022-07-05T08:07:33.2410977Z Help         : [More Info](https://aka.ms/buildtoolsdoc)
2022-07-05T08:07:33.2411386Z ==============================================================================
#CUT
2022-07-05T08:07:38.3282201Z [ 'Deploying package: D:\\a\\1\\a\\***.dll' ]
2022-07-05T08:07:38.3392094Z [ 'Calling pac cli inputs: package deploy --package D:\\a\\1\\a\\***.dll --logFile D:\\a\\1\\a\\DeployPackage\\deploy-package\\***-2022-07-05T08-07-38.330Z.log' ]
2022-07-05T08:07:41.1460134Z [ 'Reading the import configuration. Please wait.' ]
2022-07-05T08:07:41.2295468Z [ 'Import configuration loaded.' ]
2022-07-05T08:07:41.2296163Z [ 'Reading the solutions. Please wait.' ]
#CUT
2022-07-05T08:07:41.6730191Z [ 'Reading the solutions. Please wait.' ]
2022-07-05T08:07:41.6730483Z [ 'Found 7 solutions.' ]
2022-07-05T08:07:41.6730792Z [ 'Found the detailed data to import.' ]
2022-07-05T08:07:41.6731162Z [ 'Checking configuration for Finance and Operations application' ]
2022-07-05T08:07:41.6811559Z [ 'Checking configuration for Finance and Operations application' ]
2022-07-05T08:07:41.6832490Z [ '' ]
2022-07-05T08:07:41.8734848Z [ 'Importing solutions' ]
2022-07-05T08:07:42.0824843Z [ 'Beginning load of solution ***' ]
2022-07-05T08:17:22.5134221Z [ 'Beginning load of solution ***' ]
2022-07-05T08:18:00.4151782Z [ 'Beginning load of solution ***' ]
2022-07-05T08:19:38.5547027Z [ 'Beginning load of solution ***' ]
2022-07-05T08:19:55.3425045Z [ 'Beginning load of solution ***' ]
2022-07-05T08:22:18.8486932Z [ 'Beginning load of solution ***' ]
2022-07-05T09:03:28.0193787Z [ 'Beginning queueing up UpdateRibbonClientMetadata job.' ]
2022-07-05T09:03:28.1047675Z [ 'Beginning queueing up UpdateRibbonClientMetadata job.' ]
2022-07-05T09:03:28.2914157Z [ 'Beginning queueing up UpdateRibbonClientMetadata job.' ]
2022-07-05T09:03:28.4418794Z [ 'Beginning queueing up UpdateRibbonClientMetadata job.' ]
#CUT
2022-07-05T09:07:38.2655308Z [ 'Beginning queueing up UpdateRibbonClientMetadata job.' ]
2022-07-05T09:07:38.2668777Z [ 'Beginning queueing up UpdateRibbonClientMetadata job.' ]
2022-07-05T09:07:38.2680065Z [ 'Beginning queueing up UpdateRibbonClientMetadata job.' ]
2022-07-05T09:07:38.2692287Z [ 'Beginning queueing up UpdateRibbonClientMetadata job.' ]
2022-07-05T09:07:38.2784298Z ##[error]Process is terminated due to StackOverflowException.

This did used to work with the Powershell wrapper (as part of the old tasks) and also in the previous versions of PackageDeployer.exe (I will retest this to confirm).

Unable to download Power Platform Build Tools from Marketplace

I can't download Power Platform Build Tools from Marketplace. From "Get it free", I have a 500 error.

Enhancement: Sorting in unpacked solutions

When solutions are unpacked, it would be helpful if certain XML fragments were sorted as dynamics returns them in random orders each export. Examples are:-

MissingDependency in the solution.xml
AppModuleComponents for AppModules

This would help minimise changes when unpacked solutions are tracked in git.

Tasks fail to authenticate with exceptionId when targeting crm19/NOR DV environments

We had a working pipline until updating to 1.0.82.

Now some or our pipelines are failing on the step using "Power Platform Publish Customiztions".

Some of the error output:

##[debug]authenticationType=PowerPlatformSPN
##[debug]PowerPlatformSPN=84948b0a-4261-47db-bf30-2fd5e8a1e0af
##[debug]84948b0a-4261-47db-bf30-2fd5e8a1e0af exists true
##[debug]84948b0a-4261-47db-bf30-2fd5e8a1e0af=https:///
##[debug]Environment=$(BuildTools.EnvironmentUrl)
Discovered environment url from explicit input parameter 'Environment': $(BuildTools.EnvironmentUrl)
##[debug]Discovered environment url from explicit input parameter 'Environment': $(BuildTools.EnvironmentUrl)
##[debug]IsolateVarRef: $(BuildTools.EnvironmentUrl) -> BuildTools.EnvironmentUrl (isRefExpression=true)
Discovered Azure DevOps variable expression that needs resolving: $(BuildTools.EnvironmentUrl) -> BuildTools.EnvironmentUrl
##[debug]Discovered Azure DevOps variable expression that needs resolving: $(BuildTools.EnvironmentUrl) -> BuildTools.EnvironmentUrl
##[debug]BuildTools.EnvironmentUrl=undefined
##[debug]PowerPlatformCreateEnvironment_BuildTools_EnvironmentUrl=undefined
##[debug]PowerPlatformCopyEnvironment_BuildTools_EnvironmentUrl=undefined
##[debug]PowerPlatformResetEnvironment_BuildTools_EnvironmentUrl=undefined
##[debug]PowerPlatformRestoreEnvironment_BuildTools_EnvironmentUrl=undefined
##[debug]authenticationType=PowerPlatformSPN
##[debug]PowerPlatformSPN=84948b0a-4261-47db-bf30-2fd5e8a1e0af
##[debug]84948b0a-4261-47db-bf30-2fd5e8a1e0af=https:///
Falling back to url from service connection, using: https:///
##[debug]Falling back to url from service connection, using: https:///
##[debug]POWERPLATFORMTOOLS_PACCLIPATH=D:\a_tasks\PowerPlatformToolInstaller_8015465b-f367-4ec4-8215-8edf682574d3\0.0.82\bin
##[debug]command: D:\a_tasks\PowerPlatformToolInstaller_8015465b-f367-4ec4-8215-8edf682574d3\0.0.82\bin\pac\tools\pac.exe, first arg of 12: auth
[ 'Sorry, the app encountered a non recoverable error and will need to terminate. The exception details have been captured and will be forwarded to the development team, if telemetry has been enabled. Exception Id: 63f8ebd7-4fcb-4d16-993f-d5113c1499d0, Exception Type: System.NotImplementedException' ]
[ 'The diagnostic logs can be found at: D:\a\_tasks\PowerPlatformToolInstaller_8015465b-f367-4ec4-8215-8edf682574d3\0.0.82\bin\pac\tools\logs\pac-log.txt' ]
##[error]error: 1
##[debug]Processed: ##vso[task.issue type=error;]error: 1
##[error]failed: Sorry, the app encountered a non recoverable error and will need to terminate. The exception details have been captured and will be forwarded to the development team, if telemetry has been enabled. Exception Id: 63f8ebd7-4fcb-4d16-993f-d5113c1499d0, Exception Type: System.NotImplementedException

Import-Solution errors out with expired access token after 60 min

Hello. I have a big solution that needs to be installed on the environment. An error occurred while importing the solution, the logs are below.

More precisely, the problem is related to asynchronous requests. An hour later, I received the error ### "The HTTP request is unauthorized with client authentication scheme 'Anonymous'", according to error, I can assume that the problem is in the token update. I would like to note that there was no such error when using the *.0 version

Download Portal fails on adx_blog table

Downloading: Site Setting [adx_sitesetting]...
Downloaded: Bot Consumer [adx_botconsumer]
Downloading: URL History [adx_urlhistory]...
Downloaded: Site Setting [adx_sitesetting]
Downloading: Web Template [adx_webtemplate]...
Downloading: Web File [adx_webfile]...
Downloaded: URL History [adx_urlhistory]
Downloaded: Table Permission [adx_entitypermission]
Downloading: Web Page Access Control Rule [adx_webpageaccesscontrolrule]...
Downloaded: Website Language [adx_websitelanguage]
Downloaded: Web Template [adx_webtemplate]
Downloaded: Web File [adx_webfile]
Downloading: Ad [adx_ad]...
Downloading: Poll [adx_poll]...
Downloading: Website Access [adx_websiteaccess]...
Downloading: Website Binding [adx_websitebinding]...
Downloading: Page Template [adx_pagetemplate]...
Downloaded: Ad [adx_ad]
Downloaded: Poll [adx_poll]
Downloaded: Website Binding [adx_websitebinding]
Downloaded: Page Template [adx_pagetemplate]
Downloading: Ad Placement [adx_adplacement]...
Downloading: Poll Placement [adx_pollplacement]...
Downloaded: Web Page Access Control Rule [adx_webpageaccesscontrolrule]
Downloading: Shortcut [adx_shortcut]...
Downloading: Redirect [adx_redirect]...
Downloading: Web Role [adx_webrole]...
Downloaded: Redirect [adx_redirect]
Downloaded: Shortcut [adx_shortcut]
Downloaded: Ad Placement [adx_adplacement]
Downloaded: Website Access [adx_websiteaccess]
Downloaded: Web Role [adx_webrole]
Downloaded: Poll Placement [adx_pollplacement]
Microsoft PowerPlatform CLI
Version: 1.17.4+g2bdb4f2

Error: ************ Exception getting metadata info from Dataverse : Failed to resolve entity metadata for adx_blog.

Portal upload not uploading annotations attached to web files.

After downloading portal to a source branch from a dev environment, when uploading to a test environment only 1 of 18 annotations are uploaded.

This is the second pass update

Results after

Deploy Package Task fail

Power PLatform Build Tool Extension Version : 2.0.4
DevOps Pipeline Task : Power Platform Deploy Package

Behavior: In Azure DevOps pipeline, i define Power Platform Deploy Package task with the following properties:

Authentication type: Username/password (no MFA support)
Environment Url: refering my target environment
Package File: referencing the DLL to my deployment package.

In my deployment package, i import various power platform solutions, among those solutions there is one solution that contains solution-aware dataflows

I get the following error in the output of the solution history.

I noticed that only Power Platform solutions that contains Dataflows are failing, as soon as i exclude the datafalows from my solutions it works.

Also there is no helpful information in the pipeline logs.

I also notice that i am only capable of running the deployment with the Authentication type: Username/password and i cannot run it with Service Principal/client secret , otherwise i cannot see the dataflow appearing in the dataflow list.

The deployment has to be done using an office 365 and not using app registration (application user), otherwise the dataflows are not display in the UI in https://make.powerapps.com.

Add overwrite parameter to the Export Solution action

Hi.

I changed to version 2 and it is now causing the error to download the solution. Is it possible to enable the overwrite parameter?

Error: Solution output file D:\a\1\s\PowerPlatform.Solutions\mysolution.zip already exists.

##[debug]Processed: ##vso[task.issue type=error;]
failed: Microsoft PowerPlatform CLI
Version: 1.17.4+g2bdb4f2

Error: Solution output file D:\a\1\s\PowerPlatform.Solutions\mysolution.zip already exists.

Usage: pac solution export --path --name [--managed] [--include] [--async] [--max-async-wait-time] [--overwrite] [--targetversion]
  --path                      Path where the exported solution zip file will be written (alias: -p)
  --name                      The name of the solution to be exported (alias: -n)  --managed                   Whether the solution should be exported as a managed solution (alias: -m)
  --include                   Which settings should be included in the solution being exported (alias: -i)
                              Values: autonumbering, calendar, customization, emailtracking, externalapplications, general, isvconfig, marketing, outlooksynchronization, relationshiproles, sales
  --async                     Exports solution asynchronously (alias: -a)
  --max-async-wait-time       Max asynchronous wait time in minutes. Default value is 60 minutes (alias: -wt)
  **--overwrite                 The exported solution file can overwrite the solution zip file on the local file system. (alias: -ow)**
  --targetversion             (deprecated) The version that the exported solution will support (alias: -v)

##[debug]command: D:\a\_tasks\PowerPlatformToolInstaller_8015465b-f367-4ec4-8215-8edf682574d3\2.0.3\bin\pac\tools\pac.exe, first arg of 2: auth

powerplatform-build-tools/src/tasks/export-solution/export-solution-v2/index.ts

Line 28 in ec14d99

await exportSolution({

##[error]No agent found in pool {poolname} which satisfies the specified demands: PowerPlatformTool, Agent.Version -gtVersion 2.163.1

Hi,

I'm getting this error in the job after updated to the version 2. This is the failing task.

#Power Platform Import Solution - task: microsoft-IsvExpTools.PowerPlatform-BuildTools.import-solution.PowerPlatformImportSolution@2 displayName: 'Power Platform Import Solution ' inputs: authenticationType: PowerPlatformSPN PowerPlatformSPN: PowerPlaatform-Dev SolutionInputFile: solution.zip UseDeploymentSettingsFile: true AsyncOperation: true MaxAsyncWaitTime: 60 PublishWorkflows: true
The new version of the CLI is installed on the pipeline agent.

Please help!

microsoft / powerplatform-build-tools Goto Github PK

powerplatform-build-tools's Introduction

Power Platform Build Tools

High level architecture

Feedback & Questions

Community Office Hours

Contributing

Code of Conduct

Security issues

Trademarks

powerplatform-build-tools's People

Contributors

Stargazers

Watchers

Forkers

powerplatform-build-tools's Issues

Below are the full logs Starting: Import xxxxxxxxxxx

Task : Power Platform Import Solution Description : Power Platform Import Solution Version : 0.0.82 Author : Microsoft Help : More Info

Action required: 1 compliance task

GitHub inside Microsoft program information

Starting: PowerPlatformExportSolution

Task : Power Platform Export Solution Description : Power Platform Export Solution Version : 2.0.5 Author : Microsoft Help : More Info

Recommend Projects

Recommend Topics

Recommend Org

Jobs

Below are the full logs
Starting: Import xxxxxxxxxxx

Task : Power Platform Import Solution
Description : Power Platform Import Solution
Version : 0.0.82
Author : Microsoft
Help : More Info

Task : Power Platform Export Solution
Description : Power Platform Export Solution
Version : 2.0.5
Author : Microsoft
Help : More Info