Open a detail record on new tab in community site doesn't work

Kevin

We're using Spark (12.2.14) and we have a page with tables, these have records with fields that contain references to SF objects, these display as links. If I click on the links, the correct SF object opens in the same tab. If, however, I chose to open the link in new tab from right click menu, all I get is the page with the tables again not the SF object. 

This means I can't keep a skuid page open with all the filters etc applied and at the same time look at objects referenced in the tables. 

Anna Wiersema

Hi Kevin, thanks for bringing this issue to our attention and including your Skuid version. Could you provide the following information to help us better understand the scenario?:

1. To confirm, this issue where the links aren't working as expected is just occurring in the community site? Is it also happening when you preview the Skuid page in your internal Salesforce environment?
2. Are you using Visualforce or Lightning Communities?  Record links are handled differently between Visualforce Communities, Lightning Communities, and internally in Salesforce.
3. Which browser and operating system are you using?
4. Are you using Skuid API v1 or v2?

Kevin

Hi Anna,

Thank for your support.

1. The issue only occurs in the community site. 
2. Lightning Communities
   
3. Chrome and Windows 10
4. Skuid API v1
   

The current page URL: https://xxx.force.com/xxx/s/po/a0M1000000zdTYVEA2/extra-items
After click from right-click menu: https://xxx.force.com/xxx/s/po/a0M1000000zdTYVEA2/extra-items#/sObject/a0E1000001bFxsiEAC/view

Anna Wiersema

Thanks for those details Kevin.  

To clarify, you want community users to be able to use the links in a list to navigate to the record detail page?  It seems like the URLs that direct users to detail pages are handled differently in communities than internally within Salesforce. Skuid is directing community users to the internal URL for detail pages, but here's how you can update your page to direct them to the community detail page URL.

1. First of all make sure that your community users have view access for all records and related records on the detail page.
   
2. Make sure that you've set up the record detail page in the community (https://help.salesforce.com/articleView?id=community_designer_create_record_detail_page.htm&type=5)
   
3. Once your record detail page is setup, you can view its URL in the Experience Builder. In this case it looks like the URL for a case would be /case/{{Id}}/{{Name}}
   
4. Update your list page to reference this URL wherever you want users to access it, here are some suggestions:
   

• You can also use template fields to take users to a custom URL, make sure "allow HTML" is checked and then do something like <a href="/cases/{{Id}}/{{Name}}">{{Name}}</a>
  
• You can have buttons/actions direct users to this URL.
• You can also use template fields to show Id and Name fields WITHOUT THE LINKS by using triple brackets: {{{Name}}}
  

Does that make sense? Let me know if this helps and if you have any questions.

Anna Wiersema

I'm sorry Kevin, I just realized you were referring to right click + opening a new tab, which is the behavior which is not working. To clarify

• Clicking on the links works fine
• Right clicking on the links to open in a new tab isn't working.

This seems to be related to a known Skuid issue where in Windows browsers : control + click on nav item doesn't open new browser tab. This issue was addressed as of 12.2.17.  I would recommend you upgrade Skuid in a sandbox and see if this fixes the issue. See the end of this post for upgrading best practices.

Additionally, I just saw your similar post: https://community.skuid.com/skuid/topics/can-not-navigate-to-detail-record-in-community-site-in-api-v2-spark-12-0-6.  Is this the same issue or something different? 


Best practices for upgrading can be found in Upgrading Skuid on Salesforce.  As a reminder, Salesforce does NOT allow reverting back to prior versions of managed packages. Skuid always recommends installing new versions in a non-business critical sandbox environment to test all mission critical functionality before installing into a production environment. We also recommend that you update out of date Themes and Design Systems after you upgrade. Please let us know if you continue to encounter any problems with this issue after upgrading. 

Kevin

Thank for your support,

I've upgraded to Spark (12.2.18) but the issue is still occurring.


----------------------------------------------------------

Update your list page to reference this URL wherever you want users to access it, here are some suggestions:

• You can also use template fields to take users to a custom URL, make sure "allow HTML" is checked and then do something like <a href="/cases/{{Id}}/{{Name}}">{{Name}}</a>

• You can have buttons/actions direct users to this URL.

• You can also use template fields to show Id and Name fields WITHOUT THE LINKS by using triple brackets: {{{Name}}}

Because we have many Skuid pages, we cannot apply the above for each page.

Anna Wiersema

Hi Kevin, thanks for your reply.  Here's my current understanding of the situation, please answer the following questions and correct and clarify as necessary:

1. You upgraded Skuid, but right clicking on links to open in a new tab still isn't working for v1 pages in a community site while using Chrome on Windows 10. Is that correct?
   
2. What version of Chrome are you using?
3. Sounds like manually changing the links isn't a practical solution because it would entail a lot of work across multiple pages and be difficult to maintain.

Kevin

Hi Anna,

1. Yes.
2. Google Chrome 80.0.3987.149 (Official Build) (64-bit)
   
3. Yes.

I think you can reproduce this issue easily.

Anna Wiersema

Hi Kevin, I tried to reproduce this issue in 12.2.18 a community site while using Chrome 80 on Windows 10 but was unable, the detail links opened successfully in a new tab.

Could you grant Skuid Support login access so we can take a look?

Kevin

Hi Anna,

Please note that the issue only occurs in the Lightning community site. I still enable to reproduce this issue in 12.2.18 (V1).

If I choose to open the link in a new tab from the right-click menu, the "#/sObject/{{Id}}/view" value will be appended to the original URL. The URL in a new tab is different from internal SF.

Anna Wiersema

Hi Kevin, sorry for not specifying, I was using the skuid:page component in a Lightning community site.  It seems like to be able to further investigate the issue, it would be helpful to see what you're seeing and exactly how you've configured your community, so it would be helpful if you could grant Skuid Support login access. You should have received an email from the team earlier today explaining how this works.

Kevin

Hi Anna,

I granted the login access to my Sandbox. Please check detail in my email.

This seems to be related to a known Skuid issue where in Windows browsers : control + click on nav item doesn't open new browser tab. This issue was addressed as of 12.2.17.  I would recommend you upgrade Skuid in a sandbox and see if this fixes the issue. See the end of this post for upgrading best practices.

The above issue was resolved before but now it's occurring again in 12.2.18. Please also help to check that.

Anna Wiersema

Hi Kevin, thanks for granting login access. The team will investigate and send you any followup questions via email.  Once we've finished the investigation, we'll post a summary here to update any other users following this issue.

Anna Wiersema

Update: Skuid Support has confirmed this is a product defect affecting v1 pages in certain Lightning community templates (e.g. Partner Central).

Description:  In certain Lightning community templates, right clicking on a record name or Id in a v1 table does not open the detail page in a new tab, it duplicates the tab the user is already on. A normal click on the link will open the detail page as expected (in the same tab).

Kevin

@Anna Wiersema Any update on it.

Anna Wiersema

No update @Kevin. Right now we have this issue's level of client impact marked as Level 4 - Medium. Does this sound correct or should it be escalated to Level 3 - High?

Kevin

@Anna Wiersema Please escalate to Level 3 - High. I think it isn't difficult to be resolved.