Relentless error message for URL parameters when referencing Napili Standard Community Page

Question

I've seen versions of this question — but no workable answer. So trying again. Need to know what parameters will work to pull up logged-in user's Account Detail. This should not be complicated!

Using the OOB Navigation Menu

• Edit Navigation Menu to add menu item
• type = Community Page
• Page = Account Detail
• URL defaults to /account/:recordId

the last required item is the URL, and the default is /account/:recordId — but that won't save.

The Salesforce documentation recommends removing the colon — that doesn't work either. I was able to save as /account/detail — but when logged in as the user, I get "Invalid Page".

I'm pulling my hair over this! Can you help?!?

Answer 1

The record detail page aspect of the Napili Community is very confusing. Correct me if I am wrong but it looks like you created a set of record pages for Account. This gave you Account Detail, Account List, and Account Related List. Placing the Account Detail page as a top level link requires you to hardcode it to a direct Account Id by replacing :recordId with an actual live Id such as 001E0000014chufIAA. I am not sure what the actual use case is for this, but this is the functionality Salesforce built. Instead, you could link to the Account List page (where the user should only be able to see their personal account) then have them click on their Account name to navigate to their Account Detail.

A better solution that would require a little bit of coding would be to create an intermediate lightning component that will get the current User's Account Id using an Apex controller, then in the callback redirect the user to the account detail page using their Account Id. You would then place this on a new community page and use that page as the target for your navigation link.

Here's to hoping that Salesforce adds a 'My Contact' and 'My Account' concept as standard pages in Napili!

Edit - Account Page Creation

@Eric mentioned that he did not in fact create the pages as I noted above but they already existed in his org. My guess is that this difference between orgs has to do with my org being created quite a long time ago so I did not have the pages out of the box.

Eric Edit

Here are the steps I took based on this answer:

1. Apex controller to return user's Contact AccountID
2. Lightning Component with an Init event that uses force:navigateToSObject based on the Id from #1. This takes you to the appropriate Account Detail Object Page
3. In Lightning controller Init comment out the event.fire (needed so we can publish the page)
4. Create a "Navigate To Account" page in the community
5. Add the component to the page in the community (ensure you did step #3)
6. Publish the page to the community
7. Uncomment the event.fire from #3
8. Edit the navigation menu, add an item that goes to the community page you created
9. publish and upon clicking the navigation item you will be taken to the user's account

Answer 2

I have a write up and some working code that handles exactly this use case here.. The basic gist of it is, create a component that grab's the logged in user's account id via apex, then in the callback, navigate the user to their account page. Put this action as the init handler of the component, then drop the component on a standard community page (not an object page). The page with that component just serves as a dynamic redirect. Finally, use that page in your navigation menu.

One thing you'll want to update in the component controller:

redirectToAccount: function(component, event, helper) {
    var loggedInUser, navEvt, state;

    var action = component.get("c.getLoggedInUser");
    action.setCallback(this, function(response) {
        state = response.getState();
        if (state === "SUCCESS") {
            loggedInUser = response.getReturnValue();
            // add check for users without contact Id / account Id
            // YOUR CODE HERE

            // otherwise do
            navEvt = $A.get("e.force:navigateToSObject");
            navEvt.setParams({
                "recordId": loggedInUser.Contact.AccountId,
                "slideDevName": "detail"
            });
            navEvt.fire();
        }
    });
    $A.enqueueAction(action);
}

Answer 3

Can I link to an answer I just wrote on the exact same topic?

Napili Navigation Menu

Solution that doesn't require writing a redirect page- but it does still require a reasonable amount of dev/effort.

I think this probably provides the best UX.