Unanswered

Archiving of rows to optimize performance in app

(0) Share

Report

Posted on by Gyllentid

894

I have an onboarding app that I am looking to optimize. One thing I would like to do is limit the amount of rows that the app needs to handle. The app uses multiple tables in Dataverse. An idea I had is to delete rows in each table to keep them current and higher performance as there are quite som delegable tables/filters. In some circumstances I won't be able to use collections, but I have done this where possible.

Have any of you figured out some way to archive rows, maybe in other tables or in excel or similar?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (0)

ChrisPiasecki 6,422 Most Valuable Professional on at

Like (0)

Report

Hi @shavora,

Have you looked at the new Long Term Data Retention feature for Dataverse? It will allow you to set data retention policies and move read-only / infrequently accessed data to archive storage.

Otherwise, using views or filter is the best way to limit rows returned in a particular query.

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

Was this reply helpful? Yes No
Gyllentid 894 on at

Like (0)

Report

Hello ChrisPiasecki,

I always filter. The selection of items that is showcased in a gallery is often less 10 due to the filter. But within the gallery there are delegeable lookups to related tables and I worry that they will slow down the app. So would you say that the filtering in and off itself is enough to keep the issue of performance at bay? The lookups that is referencing the lookup or filtered table has a thousand rows.

I will look into the Long term Data retention, thank you 🙂

Was this reply helpful? Yes No
ChrisPiasecki 6,422 Most Valuable Professional on at

Like (0)

Report

Hi @shavora,

It all really depends on the query and how complicated it is. Adding lots of columns and lookups to the query and filtering on many lookups will certainly introduce a performance hit but how much or how noticeable is difficult to determine ahead of time.

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

Was this reply helpful? Yes No