You’re offline. This is a read only version of the page.
Announcements
139
Hello Community,
I’m facing an issue with the navigation component after enabling the new analysis engine in Power Apps.
Earlier, we used to pass a collection from the app scope to the navigation component. This allowed us to seamlessly manage screen names and other properties. However, with the new analysis engine, the setting of passing a collection to a component must be disabled. This requires us to initialize the collection at the component level instead of passing it from the app scope.
The main issue arises when trying to pass the screen name to the navigation component. Since the screen name is not available at the component level, I’m struggling to make the navigation component work dynamically based on user clicks.
I attempted to use input-output properties in the component, but passing the screen name this way has proven to be very challenging. Without the screen name, my navigation logic isn’t functioning as intended.
If anyone else has encountered and resolved a similar issue, I’d greatly appreciate your guidance. Your insights could be very helpful to me and others facing the same problem.
For reference, here is a link/resources where we used to pass the screen name from the app scope to the component:
Thanks in advance for your help!
Share
Report
All responses (
Answers (
