Loading Dataverse data into collection does not load all data

[jrossstocholm]

I have a Canvas app that feeds off Dataverse data. I am experimenting with loading data into a collection at app startup instead of directly from Dataverse.

However - the behaviour puzzles me.

I instantiate the collection in the App's OnStart event like this

The view "Current and future topics - setting" holds three items. They have all been created by me.

When I fire off the "Run OnStart" on the app, I would expect the rows from that field to be loaded into the collection. In the screenshot just below, the three items are shown in the purple row - so my app can clearly see the items.

But not all rows are loaded into the collection. Only two rows are loaded.

When I go to the "Variables" section I see this

Only two rows are loaded - and there are no values available in them.

I feel that I am missing something here ... can anyone help me figure out what?

Thanks 😊

/Jesper

[ivan_apps]

Just to confirm - your app is working as expected but you seeing 2 rows listed in the collection but when your gallery shows the collection it is 3 rows? It could simply be a display issue if 3 rows are successfully shown in your app that references the collection.

[jrossstocholm]

Hi @ivan_apps 

If I set one of my galleries' "Items" property to my collection, it shows two items and not three

Also - I have a label control within my gallery items and I have set the "Text" property to "ThisItem.Name. But no value is shown ... which might be caused by no values being shown in the "data collection view" I showed above (the last picture in the original post)

[ivan_apps · Accepted solution]

Weird, can you try to change your clear collect to use a filter() on your table instead of using a view? You should be able to recreate the view criteria with Filter() at least so we know if the view is the issue or not.

[Yaffle]

I notice an asterisk next to the view name in the screenshot of the view - doesn't that mean you have outstanding modifications to save?

[jrossstocholm · Accepted solution]

I have done just that, and it works. I have rewritten the code to load all items into a collection and then create additional "sub collections" that are filtering the initially loaded collection. It is not super pretty, but it works 😊.

[AldenKnibbs]

I ran into this issue when completing the following labs: Create a machine ordering app with Power Apps - Online Workshop - Training | Microsoft Learn

Issue Summary

Collection data not loading on the compare screen in PowerApps while following a specific learning path.

Detailed Issue Description

The issue arose in the Power Apps Online Workshop, specifically affecting the compare screen's functionality, which is designed to allow users to select items for comparison. Despite following the outlined steps within the learning materials, collection data expected to populate did not load, hindering the ability to proceed with the exercises as designed. The core challenge was ensuring that the necessary data from the collection was accessible and appropriately utilized on the compare screen, without displaying unnecessary data.

Resolution Steps

The issue was resolved through a strategic approach to data management within the app, focusing on the preparation and utilization of collection data before it was needed on the compare screen:

1. Data Preparation in Gallery: In the gallery component where items are chosen for comparison, text labels were created for all necessary data from the collection that needed to be compared.
2. Setting Visibility: The visible property of the text labels for data not required to be displayed on the compare screen was set to false. This method ensured that the data was pre-loaded and readily available for use when needed, without visually cluttering the interface.
3. Utilizing Prepared Data: By preparing the data in advance and managing its visibility, the compare screen successfully loaded the data when items were selected for comparison, effectively resolving the issue.

[jrossstocholm]

Hi @AldenKnibbs 

Thank you for pitching in. As mentioned above I have a working solution now. I have not done anything specific to fix this than what I have written about earlier. I am now loading directly from the View in Dataverse (the thing that did not work previously) and it somehow works now.