If you create a hyperlink in a generative page to an entity form, the web page level navigation in the entity form does not work, e.g. the "Go back" button is grayed out. Is there a way to fix the navigation between generative and entity forms?
The “Go back” button is disabled because the app’s navigation history doesn’t include the generative page when you open the entity form via a direct link. There’s no built-in toggle to change this behavior in Power Apps at the moment.
In related scenarios (opening forms via code vs link), users have found that navigation context dictates whether the back button works:
If navigation is done via launch/URL, history isn’t tracked properly → back button doesn’t work.
If navigation is done via internal nav APIs (like Navigate() in custom pages or model-driven navigation functions), the app retains navigation history and the back stack works.
So the core issue isn’t specific to generative pages, it’s how model-driven app navigation and browser history interact.
The closest “fix” is to ensure the form is opened using a navigation method that preserves the internal app navigation stack (e.g., navigate functions), or to implement your own back link/button.
Instead of embedding a <a href="..."> link or direct URL, consider using client API navigation functions such as Xrm.Navigation.navigateTo (in a custom page context) or the Power Fx Navigate() if supported.
✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem. 👍 Feel free to Like the post if you found it useful.
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.