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.
MIT License
199
stars
41
forks
source link
Does pac solution import --stage-and-upgrade work on new solution import? #1078
We are running solution deployment in DevOps for Power Platform dev. We found the below code errored out when it is an new import and works if it is an solution upgrade.
pac solution import --path /home/vsts/work/1/FOBDSPNotes-managed/FOBDSPNotes.zip --skip-dependency-check --max-async-wait-time 60 --convert-to-managed false --publish-changes --stage-and-upgrade --async --settings-file /home/vsts/work/1/settings/settings.qa.json
Here is the error we got:
ImportAsHolding failed with exception :Solution manifest import: FAILURE: Cannot create a holding solution for missing base FOBDSPNotes.
--stage-and-upgrade seems to do import and upgrade the solution. If that is not the correct command, what we should use when doing a new import?
We are running solution deployment in DevOps for Power Platform dev. We found the below code errored out when it is an new import and works if it is an solution upgrade. pac solution import --path /home/vsts/work/1/FOBDSPNotes-managed/FOBDSPNotes.zip --skip-dependency-check --max-async-wait-time 60 --convert-to-managed false --publish-changes --stage-and-upgrade --async --settings-file /home/vsts/work/1/settings/settings.qa.json
Here is the error we got: ImportAsHolding failed with exception :Solution manifest import: FAILURE: Cannot create a holding solution for missing base FOBDSPNotes.
--stage-and-upgrade seems to do import and upgrade the solution. If that is not the correct command, what we should use when doing a new import?