Monitor shows that all items are loaded on startup

(1) Share

Report

Posted on by EdViegas

436

Hi,

I've noticed that after the Power Apps version update, some apps are loading — or rather, retrieving — data from the datasource at startup. After running some tests, I found that the issue occurs when these apps use a main menu component with a collection as an input parameter, where the screen control is passed as a value. I mean, the typical setup:

GlobalMenuItems = Table(
    {
        Id: 2,
        MenuLabel: "Customer",
        Screen: Screen2
    },{
        Id: 1,
        MenuLabel: "Product",
        Screen: Screen3
    },
    
    {
        Id: 3,
        MenuLabel: "Projects",
        Screen: Screen1
    }
);

This collection is an input parameter for the main menu.

If I select version 3.24101.10 (from Settings - Support), everything works great, and I see in the Monitor that only the controls on the current page are loaded. With other versions, like 3.24111.7, 3.24104.14 (flagged as recommended), 3.24103.17, and 3.24102.17, the Monitor shows that all controls from every screen are retrieving data from external sources on start.

Has anyone else noticed this?

Categories:

Building Power Apps

I have the same question (0)

All responses (5)

Answers (1)

blanghorst 206 on at

Like (0)

Report

Did you ever find an answer for this issue? We saw something interesting today - we have an app that has been working correctly forever but since 3.24104.14 was released, it won't work. We will sometimes see the "app has stopped working" error when trying to launch the app whereas other time, the app loads but some of the workflows and data loads just stop. We switched back to 3.24102.17 (which was the last working version) and it now works fine. The monitor logs have been pretty useless in trying to determine the issue.

Was this reply helpful? Yes No
EdViegas 436 on at

Like (1)

Report
I've reproduced the error again. I’ve created a super simple app with three screens: A, B, and C. I’ve added three tables from Azure SQL Server: Customers, Products, and Projects.
Screen B has a gallery with the Projects table as its items.

In App.Formulas i've added:

GlobalMenuItems = Table( { name: "a", screen: Screen1 }, { name: "b", screen: Screen2 }, { name: "c", screen: Screen3 } );

Then, I’ve added a gallery to each screen with GlobalMenuItems in the "Items" property.

- Gallery1: Control: Gallery Variant: galleryVertical Properties: Items: =GlobalMenuItems DelayItemLoading: =true Height: =350 Layout: =Layout.Vertical LoadingSpinner: =LoadingSpinner.Data TemplateSize: =104 Width: =440 X: =835 Y: =418 Children: - Label1: Control: Label Properties: OnSelect: =Select(Parent) Text: =ThisItem.name X: =40 Y: =40

The monitor always shows: LoadDependentScreens (Screen1 -> Screen2, Screen3).

And it always displays "Requested 100 rows. Received 100 rows" from Screen2 (but I've visited only Screen1).

The problem occurs when I add the Screen control as the value of a property in GlobalMenuItems.

I am sure that Power Apps did not behave this way in previous versions.

I also do not understand how it is possible to create a navigation menu in Power Apps without including a reference to the Screen control inside a variable.

Was this reply helpful? Yes No
Verified answer

EdViegas 436 on at

Like (2)

Report

After numerous test I found that enabling the "New analysis engine" option alters this behavior in Power Apps worsening significantly the performance of the published application. The authoring version tested is: 3.24111.11

Options enabled on last test are:

New:
Modem controls and themes
Expanded media support for SaveData on Power Apps mobile apps
Enable delegation for Updatelf and Removelf

Preview:
Enable Ideas panel
Copilot component
Copilot answer component
Edit in Copilot Studio
App Copilot
Copilot for formulas
Enhanced component properties

Experimental:
None

Retired:
Export and import components

Was this reply helpful? Yes No
Suggested answer

SaiRT14 1,990 Super User 2025 Season 2 on at

Like (1)

Report
Newer versions may preload data for screens referenced in collections, treating them as dependencies

try the following:

Use screen names instead of direct screen references.

Optimize your menu component to avoid unnecessary screen dependencies.

Enable lazy loading or improved data source behavior in app settings.

Roll back to the stable version and report the issue to Microsoft.

Was this reply helpful? Yes No
IAmIntractable 280 on at

Like (1)

Report

Many in my orbit have reported issues with the new Analysis Engine. Avoid it if you don't want to be a beta tester. Sadly, I am never going to know for sure it ready for prime time.

Was this reply helpful? Yes No