Unanswered

undefined facing a challenge with the document upload feature on our Power Apps Portal.

(0) Share

Report

Posted on by Neverz

Hi Everyone,
I hope you're all doing well. Our development team currently facing a challenge with the document upload feature on our Power Apps Portal.
We're using the document upload feature to create multiple line items in Dynamics 365 from an Excel file. Each line item contains about six fields (field type numbers) of information. While the upload process itself seems to work fine, we're experiencing a significant delay in seeing these records reflect both in Dynamics and on the portal.
In fact, it's taking close to 10 minutes for the records to appear, which is causing some frustration among our users. We've looked into possible background processing or synchronization contributing to this delay, but we're still searching for an effective solution.
Has anyone encountered a similar issue before? If so, could you please share your insights, tips, or best practices that might help us address this delay?
Any guidance or suggestions you can provide would be greatly appreciated

Categories:

General topics

All responses (2)

Answers (0)

Sort by

Lucas001 2,595 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @Neverz,

your problem refers to the cache in power pages and dynamics. Unfortunately it takes up to 15 minutes and currently you won't find a "nice" solution for that problem.
But you can have a look here and try to use that or a similar approach to solve your problem.

--------------------------------------------------------------------------------------

Hope that helps.

If the post solves your problem, please mark it as solution. If it helps, consider a thumbs up.
Fubar 17 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Delay on the Dynamics side is most likely your code (assuming you aren't using the extended) the data from the portal to Dataverse is close to realtime.

Delay for records showing on the Portal is the portals cache (the SLA is 15 mins but will usually refresh within a few minutes). The following doesn't work with out of the box views etc but if you are querying via fetchxml or the Web API you can invalidate the Cache by making your query relatively unique by including today's date down to seconds e.g. createdon/modifiedon less than today formatted in reverse date down to seconds (as it can't match the query in its cache - other than down to the current second in - it will pull from Dataverse) - but note, it is not recommended by Microsoft to invalidate the cache
(a bit more info here in the "Retrieving data via FetchXML/Liquid or oData" section https://oliverrodrigues365.com/2020/07/27/power-apps-portals-caching-tips probably not the best example but should have enough info to work it out yourself).

When I have done something similar in the past we just sent them an email letting them know the status and a link when we knew the records would be available - and set their expectation that processing may take a while and we would email them when it was completed.