function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
Vandana Rattan 4Vandana Rattan 4 

Workaround for force:navigateToComponent

I was using the function force:navigateToComponent to navigate from one component to other. It was working fine till some time ago but now it has stopped working. All the blog posts suggest that it is not supported now. Is there any other option available that I can use? It is pretty urgent as I need to rollout the app in beginning of the next FY.

Thanks,
Vandana
bob_buzzardbob_buzzard
I'm using dynamic component creation to move between components inside my application. Thus I have a top level component that encapsulates the component that I am actually dealing with inside a div with the id of content, then when I click a button that would usually navigate to a different component, I dynamically create the component and replace the content div body with the new component. It works well, although you do have to wire up the attributes and event handlers via JavaScript.
Newbie2SFDCNewbie2SFDC
Hello Bob,

It will be great if you can provide a sample code for the above explained.

Many Thanks!