# Navigation Issues

[Max Widmaier]

I’ve found an issue with using #’s for navigation with the crm. If you’re not in the linked workspace (Say I want to navigate to the activities tab of a household with oid ‘xyz’), clicking on a link such as <serverRoot>/ui/portal#Contacts/tabHouSummary;EntityId=xyz  does not navigate you to the household but opens the contact workspace.
However, if I am already in the contacts workspace navigating to such a link works just fine.

I am unsure if this is some framework issue or was intended from the start. Thank you for the assistance!

0

[stephane.lachance]

Is there an issue with using the controller’s ‘navigate API? Ie. (navigate controller viewPath context …)?

0

[shahzad.qureshi]

A framework bug has been filed CRM-1129 and targeted to our 23.11 release in November.
However, we recommend you should be using portlet ref here rather than tabs/page.  e.g. mda_EntityBio_hou_portlet

0

[Max Widmaier]

Ya, it produces the same effect however. To respond to Stephane’s question, this is being used to create hyperlinks in text in a react portlet where the normal scheme API is not available. If there’s an alternate way to do this, that would be amazing!

0

[stephane.lachance]

There might be a way to for the React portlet app to fire a UI event to the context bus while intercepting it in the broker portlet, thus making available the typical ‘navigate API. However, this would be a fairly advanced use of our front-end platform’s capabilities and require internal investigation. Is the React portlet app implementation available to anyone internally at NexJ?

 

0

[Max Widmaier]

The actual portlet implementation is in the Nexj Wealth Community repository however the source code for the portlet jsx/rendering code is private. If that code is necessary, I can look into getting it for you. (Or at least the relevant parts)

0

[stephane.lachance]

Does the React component pass any prop containing the id of the household (or entity, for that matter)?

0

[Author]

Posts