cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Django
Impactful Individual
Impactful Individual

Power Apps Portals CLI upload record failed does not exist

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 😊

1 ACCEPTED SOLUTION

Accepted Solutions
Django
Impactful Individual
Impactful Individual

So here is what I think I found:

  1. DevOps seems to download the Git repo locally to the VM that runs the pipeline.
    In my case this means that the manifest of a previous export is available for the Pipeline.
  2. The Power Platform Build Tool seems to compare the old manifest of previous exports to the current Portal tables.
    Then it records changes (like deleted records) to the new manifest of the new export.
  3. Then a new import will give these failed notifications

Again: no harm seems te be done except for these useless Failed notifications that cannot even be considered as traditional errors (where something actually went wrong).

 

My workaround 

  1. Clean up the "old" manifest of the GIT manually for every GUID in the failed notification run
    (verify that the rest of Portal Config files do not reference these GUIDs)
  2. Run a new Export --> I saw that the Pipeline now did not update the manifest because there was nothing (no deleted records in old manifest) to compare it to
  3. Run a new Import --> no Failed lines notifications

View solution in original post

4 REPLIES 4
chleverenz
Power Participant
Power Participant

@Django ,

just to make sure: does this also happen, when do it manually from a clientmaschine?

 

In our company we also think, that some things are missing in that tool. For example the deletion of all files when using  "-o true" on download is not that helpful when using git...

We are currently working on a devops integration for that and try to download the code from the targetsystem before uploading the new version (yes, call me paranoid). In that scenario you face problems in the devops (which is currently related to my limited experience in devops...) because you might overwrite your local new code with the one from the target. So we should create a branch before downloading or just upload to a completely diffrent repository for backup purposes. Just writing about it seems to me as there is not a clear way how to do it rightly 🙂

 

Have fun and thanks for publishing, that obviously also other people struggle with parts of the portals devops integration 🙂

Christian

 

Have fun,
Christian
----------------------
Please do not forget to leave feedback if this post helped you. Already giving kudos is a great way of feedback when the post was helpful.
Comments on how the answer could be improved are welcome, too.
Django
Impactful Individual
Impactful Individual

@chleverenz --> not checked if also on Client from Visual Studio occurs. 

In our case the Pipeline is a given fact so it needs to be fixed there.
I am also curious though so will update when I have tested this 😁

chleverenz
Power Participant
Power Participant

Hi @Django ,

does not help, but my commandline just told me:

chleverenz_0-1637599670984.png

so, seems to be a tool problem and not a problem ob devops...

Kind regards, Christian

Have fun,
Christian
----------------------
Please do not forget to leave feedback if this post helped you. Already giving kudos is a great way of feedback when the post was helpful.
Comments on how the answer could be improved are welcome, too.
Django
Impactful Individual
Impactful Individual

So here is what I think I found:

  1. DevOps seems to download the Git repo locally to the VM that runs the pipeline.
    In my case this means that the manifest of a previous export is available for the Pipeline.
  2. The Power Platform Build Tool seems to compare the old manifest of previous exports to the current Portal tables.
    Then it records changes (like deleted records) to the new manifest of the new export.
  3. Then a new import will give these failed notifications

Again: no harm seems te be done except for these useless Failed notifications that cannot even be considered as traditional errors (where something actually went wrong).

 

My workaround 

  1. Clean up the "old" manifest of the GIT manually for every GUID in the failed notification run
    (verify that the rest of Portal Config files do not reference these GUIDs)
  2. Run a new Export --> I saw that the Pipeline now did not update the manifest because there was nothing (no deleted records in old manifest) to compare it to
  3. Run a new Import --> no Failed lines notifications

Helpful resources

Announcements

Summer of Solutions | Week 3 Results | Win free tickets to the Power Platform Conference

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 1: Community MembersSolutionsSuper UsersSolutionsPower Pages @Inogic  1   @ragavanrajan  2 @aofosu  1 @Jcook  1Open  @OliverRodrigues  1Open  @Lucas001  1Open Open    Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 2: Community MembersSolutionsSuper UsersSolutionsPower Pages @taraubianca25  2 @EmadBeshai  2 @ALP2  2@Fubar 2 @ekluth1  2@ragavanrajan 1 @mandela  1@OliverRodrigues 1 @Ajlan  1Open   @elishafxx  1    @TA_Jeremy  1    @helio1981  1       Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower PagesInogic2@EmadBeshai 6Ajlan1@ragavanrajan 4CraigWarnholtz1@Fubar 4  @Jcook 3  @OliverRodrigues2  

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

  On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Top Kudoed Authors
Users online (4,906)