Others

Fix Power Apps Left Navigation Blank on First Screen

Jason MillerJason Miller Oct 20, 2026 869 views

Question details

The user needs to resolve an issue in a responsive Power Apps application where the left navigation component does not render options on the initially loaded screen.

Fixing Blank Left Navigation on the First Screen in Power Apps
Product
Microsoft Power Apps
Device & OS
not provided
Scenario
Building or running a responsive application in Power Apps with a shared left navigation component across multiple screens.
Observed behavior
The left navigation component appears completely blank on the first screen that loads, but functions correctly on all subsequent screens.
Before you start

Verify that your app's global variables and data collections used for the navigation menu are fully initialized before the first screen finishes rendering.

Solution 1Recommended

Move Initialization Logic to App.OnStart or Screen.OnVisible

Ensure the data driving the navigation component is loaded exactly when the app launches or when the first screen is displayed.

Often, a component appears blank on the first screen because the collections or context variables it depends on have not yet been populated. Placing the initialization formula in the correct property resolves timing issues.

1
Open App Properties

Open your application in Power Apps Studio and select the 'App' object from the Tree view on the left navigation pane.

2
Check App.OnStart

Examine the 'OnStart' property in the formula bar. Ensure any variables or collections used by your navigation component (e.g., ClearCollect(NavMenu, ...)) are defined here.

3
Use Screen.OnVisible as an Alternative

If you cannot use OnStart, select your first screen from the Tree view. Move your navigation initialization formula to its 'OnVisible' property to force the data to load right when the screen renders.

Move Initialization Logic to App.OnStart or Screen.OnVisible
Non-blocking OnStart Rule: If you recently enabled the 'Use non-blocking OnStart rule' in app settings, ensure your variables completely finish loading before the navigation component attempts to read them.
Free Microsoft Office alternative

Need a Reliable Office Suite? Try WPS Office

While troubleshooting Microsoft Power Apps, you might also be looking for a lightweight, powerful, and cost-effective solution for your daily document, spreadsheet, and presentation tasks. WPS Office provides a complete, seamless experience for all your productivity needs.

  1. 1. Visit the WPS Website: Go to the official WPS Office website on your preferred device.
  2. 2. Download the Installer: Click the 'Free Download' button to obtain the lightweight installation package for your operating system.
  3. 3. Install and Launch: Run the installer, follow the simple prompts, and open WPS Office to start managing your daily workflows.
Fully compatible with Microsoft Word, Excel, and PowerPoint formats, ensuring seamless file sharing.Lightweight application that runs smoothly on Windows, Mac, Linux, iOS, and Android.Familiar, highly intuitive user interface requiring zero learning curve for traditional Office users.Built-in advanced PDF editing, merging, and conversion tools to handle diverse documentation tasks.
microsoft office alternative - wps office

Frequently Asked Questions

Why do Power Apps components work perfectly on other screens but not the first one?

This commonly happens because variables, collections, or data sources required by the component are initialized on a secondary screen or haven't finished processing by the time the first screen renders. Consolidating initialization logic in the App.OnStart property usually resolves this.

How can I force a Power Apps component to refresh on screen load?

You can update or re-collect the variables driving the component within the screen's OnVisible property. Using the Reset() function on the component or updating a context variable used as the component's input can also force a data refresh.

What is the difference between OnStart and OnVisible in Power Apps?

App.OnStart executes exactly once when the application is first launched, making it ideal for defining global variables and color themes. Screen.OnVisible executes every time a user navigates to that specific screen, which is useful for refreshing screen-specific data or resetting local UI states.