Unanswered

Collections On Start

(0) Share

Report

Posted on by jed76

Anyone have any idea why it appears that my collections are not 'collectin' OnStart (which is enabled)?

I hae receiving an error with a filtered gallery the first time it is shown on a screen. The items are from a collection. As soon as the gallery is shown the first time, all is well, but it seems that the collection is not being created when the app first starts, only when I refresh the gallery?

Categories:

Building Power Apps

All responses (4)

Answers (0)

Sort by

AmeerJab 370 on at

Like
a
(0)

Report
Copy link

Link copied!

Hello,

so on the Onstart you define a collection, and when you use the collection in a gallery it gives you errors?, can you please provide more details
PowerNuggets 360 on at

Like
a
(0)

Report
Copy link

Link copied!

hi @jed76

You can change the properties of your first Screen. The Screen has an OnVisible property which performs actions when you navigate to the screen. This applies to the very first screen of the app too.

So you can set the OnVisible property of Screen1 to:
Collect(collectionName, SharepointListSource)

_____________________________________________________________________________________
Like my answer? - Hit that Thumbs Up. Resolved the Issue? - Hit Accept as Solution.

KR,
timl 37,287 Super User 2026 Season 2 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @jed76

This is most likely a timing issue. Power Apps isn't finishing the collection of data when it shows the gallery for the first time.

You can experiment with turning off the 'use non blocking OnStart rule'. That might help to resolve the problem.
jed76 on at

Like
a
(0)

Report
Copy link

Link copied!

I think I've fixed it!

I was using some logic to display a label informing the user of a duplicate item. However, instead of referencing the collection within the label I was referencing directly to the data source. So the gallery was using the collection and the visible property of a label within the gallery was referencing the data source directly. I have now changed the query to the collection and it seems to have done the trick!