We are using the Portals support for Power Platform CLI - Power Apps | Microsoft Docs in an Azure DevOps Pipeline and after a few successful runs uploading the portal to a TEST Environment from our Git Repo (exported from a DEV environment) with a command like:
pac paportal upload --path $(System.DefaultWorkingDirectory)\ExportedPortal\custom-portal --deploymentProfile ${{ parameters.environment }}
at the end of the upload to TEST it gives this notification:
Updating table with record id:00000000-0000-0000-0000-000000000000 FAILED due to adx_entitylist With Id = c86f059d-4f36-ec11-8c64-000d3a2fd376 Does Not Exist
Started uploading website data
Loading Portal Manifest...
Manifest loaded successfully.
Connected to...Kiwa Dynamics 365 Inspection Portal TST01
Upload completed for table: adx_entityformmetadata
Upload completed for table: adx_website
...etc...
Upload completed for table: adx_publishingstate
Upload completed for table: adx_contentsnippet
Updating table with record id:00000000-0000-0000-0000-000000000000 FAILED due to adx_entitylist With Id = c86f059d-4f36-ec11-8c64-000d3a2fd376 Does Not Exist
Updating table with record id:00000000-0000-0000-0000-000000000000 FAILED due to Adx_webpageaccesscontrolrule With Id = c77a069a-bc3b-ec11-b6e5-000d3aab4dc4 Does Not Exist
Updating table with record id:00000000-0000-0000-0000-000000000000 FAILED due to Adx_webpageaccesscontrolrule With Id = be45cb46-be3b-ec11-b6e5-000d3aab4dc4 Does Not Exist
Updating table with record id:00000000-0000-0000-0000-000000000000 FAILED due to adx_entitylist With Id = c86f059d-4f36-ec11-8c64-000d3a2fd376 Does Not Exist
Updating table with record id:00000000-0000-0000-0000-000000000000 FAILED due to Adx_webpageaccesscontrolrule With Id = c77a069a-bc3b-ec11-b6e5-000d3aab4dc4 Does Not Exist
Updating table with record id:00000000-0000-0000-0000-000000000000 FAILED due to Adx_webpageaccesscontrolrule With Id = be45cb46-be3b-ec11-b6e5-000d3aab4dc4 Does Not Exist
Updating table with record id:00000000-0000-0000-0000-000000000000 FAILED due to adx_entitylist With Id = c86f059d-4f36-ec11-8c64-000d3a2fd376 Does Not Exist
Updating table with record id:00000000-0000-0000-0000-000000000000 FAILED due to Adx_webpageaccesscontrolrule With Id = c77a069a-bc3b-ec11-b6e5-000d3aab4dc4 Does Not Exist
Updating table with record id:00000000-0000-0000-0000-000000000000 FAILED due to Adx_webpageaccesscontrolrule With Id = be45cb46-be3b-ec11-b6e5-000d3aab4dc4 Does Not Exist
Updating table with record id:00000000-0000-0000-0000-000000000000 FAILED due to adx_entitylist With Id = c86f059d-4f36-ec11-8c64-000d3a2fd376 Does Not Exist
Updating table with record id:00000000-0000-0000-0000-000000000000 FAILED due to Adx_webpageaccesscontrolrule With Id = c77a069a-bc3b-ec11-b6e5-000d3aab4dc4 Does Not Exist
Updating table with record id:00000000-0000-0000-0000-000000000000 FAILED due to Adx_webpageaccesscontrolrule With Id = be45cb46-be3b-ec11-b6e5-000d3aab4dc4 Does Not Exist
Upload completed for table: annotation
Finishing: Import portal config
This is totally understandable, because these specific records were deleted from DEV environment so they are not needed in TEST. The manifest.yml file of the exported portal configuration files from DEV even know this:
- RecordId: c86f059d-4f36-ec11-8c64-000d3a2fd376
DisplayName: Assets
CheckSum: 5fe5fd7ea32d16be060ee2289163c1adace50e7b814217434a779a9a72d98f93
IsDeleted: true
...but if the manifest from DEV already states that the record has the property of IsDeleted: true --> why does the pac paportal upload command for TEST try to upload that record?
Should the tooling not be smart enough to skip this and prevent the (multiple) failed-notifications?
Just wondering if there is something I am missing here 😊
