Can Lightning:navigation Be Used In Communities


Answer :

lightning:navigation is not supported in communities .Take a look at Summer18 release notes here that clearly mentions below

These resources aren’t supported in other containers, such as Lightning Components for Visualforce, Lightning Out, or Communities. This is true even if you access these containers inside Lightning Experience or the Salesforce mobile app.

Update:

With Recent releases it is now supported in lightning communities as well .


There's been an update for this since the best answer was posted and it's now possible to navigate around at your heart's content.

Here's how:

On the component:

<!-- exampleComponent.cmp --> <aura:component implements="forceCommunity:availableForAllPageTypes" access="global" >     <lightning:navigation aura:id="navService"/>     <!-- Your content here -->     <lightning:button label="Navigate To Page" variant="Neutral" onclick="{!c.completeOrder}" /> </aura:component>

In the controller:

({     navToPage : function (component, event, helper) {         // gets the <lightning:navigation> tag on the component         let navService = component.find("navService");          // Sets the route to [Org url]/[Community uri]/[pageName]         let pageReference = {             type: "comm__namedPage", // community page. See https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/components_navigation_page_definitions.htm             attributes: {                 pageName: 'home' // pageName must be lower case             }         }          navService.navigate(pageReference);     } })

And that's it!

If you'd prefer, there are more options including generating the url on init and saving it in an attribute to use later, or writing the controller code in the helper file instead of directly in the controller, which allows you to more cleanly input a pageName without a giant chunk of code - especially if you want to reuse it.

For more info, see the below links:

lightning:navigation tag:
https://developer.salesforce.com/docs/component-library/bundle/lightning:navigation/documentation

Page Reference Types:
https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/components_navigation_page_definitions.htm

Cheers Guys! Happy coding!

Dunks


Comments

Post a Comment

Popular posts from this blog

Are Regular VACUUM ANALYZE Still Recommended Under 9.1?

Answer : VACUUM is only needed on updated or deleted rows in non-temporary tables. Obviously you're doing lots of INSERTs but it's not obvious from the description that you're also doing lots of UPDATEs or DELETEs. These operations can be tracked with the pg_stat_all_tables view, specifically the n_tup_upd and n_tup_del columns. Also, even more to the point, there is a n_dead_tup column that tells, per table, how much rows need to be vacuumed. (see Monitoring statistics in the doc for functions and views related to statistics gathering). A possible strategy in your case would be to suppress the scheduled VACUUM, keeping an eye on this view and checking on which tables the n_dead_tup is going up significantly. Then apply the aggressive VACUUM to these tables only. This will be a win if there are large tables whose rows never get deleted nor updated and the aggressive VACUUM is really necessary only on smaller tables. But keep running the ANALYZE for the optimiz
Read more

Can Feynman Diagrams Be Used To Represent Any Perturbation Theory?

Answer : Diagram machinery works also for perturbation theory in classical statistical mechanics and classical field theories. Generally, various kinds of diagrams constitute a pictorial way of talking about tensor products and their contractions while hiding the multi-linear algebra from the layman. In the simplest case, vertices (or blobs) represent vectors, matrices, tensors; vertices have ingoing and/or outgoing ports; ingoing ports denote (contravariant) ro indices; outgoing ports denote (covariant) co indices; directed arcs between blobs give a pair of equal indices summed over; different base spaces ⇔ \Leftrightarrow ⇔ different arc types; symmetric tensors ⇔ \Leftrightarrow ⇔ undirected diagrams; no labels are needed for internal lines. In many cases, the directed arcs are decorated (as thin, thick, broken,wavy, curly lines), each decoration indicating the presence of a so-called propagator, a function of its label to use as a weight in the sum, which may beco
Read more