Skip to main content

Notifications

Power Apps - Building Power Apps
Answered

Gallery showing data no longer available to users

(0) ShareShare
ReportReport
Posted on by

I am currently building a PowerApp which consists of 2 screens: an overview screen with a gallery and a detail screen where users can preform actions on the record.
The data is coming from a Dataverse table which holds requests from clients, filled through Azure Portal. In the details the users have 3 actions they can take, they can approve a request with a start and end date of the approval, they can decline a request and they can re-assign the request to a different team / business unit. These actions all work and do as advertised, the re-assignment is done through calling a PowerAutomate flow and waiting for its response before navigating back to the overview page.
Here we are currently running into the issue that despite the users being able to re-assign the Owner column and having proper security roles set on the AD Group reflecting this, when they re-assign a record the item still stays visible in the Gallery on the overview page. Even though there is a "Refresh(DV_Requests)" set in the OnVisible of the overview page, this still remains the case.

Is there some way this could be avoided without adding too much delay on the PowerAutomate flow or adding many components to the Detail screen?

Categories:
  • Verified answer
    Re: Gallery showing data no longer available to users

    The issue lies in that there is no awaiting the Patch resolution if you do it directly in PowerApps.
    Then you get the error message as following:

    SteveSchurmans_0-1651070677795.png


    The issue has been resolved by just calling a PowerAutomate flow and forcing PowerApps to wait for the response of Automate before Navigating back to the Overview. Do be aware that with Patch in Power you can just assign the Owner column to an entire Team, where in Automate you need to first fetch the OData ID from the table (it will not accept the Teams GUID as a string to update, it needs to come from a 'Get Row by ID'-action and the OData ID parameter from that action).

     

  • Re: Gallery showing data no longer available to users

    If you are only using the PA flow for updating the record, I suggest changing it to a patch function. That way you can directly update the record and don’t have to wait for a flow and not the full dataset has to be refreshed, but just the record.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Microsoft Kickstarter Events…

Register for Microsoft Kickstarter Events…

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Announcing Forum Attachment Improvements!

We're excited to announce that attachments for replies in forums and improved…

Leaderboard

#1
WarrenBelz Profile Picture

WarrenBelz 145,580

#2
RandyHayes Profile Picture

RandyHayes 76,287

#3
Pstork1 Profile Picture

Pstork1 64,909

Leaderboard