Skip to main content
Group

UnofficialSF Discussion

Unofficialsf.com is a community website that provides useful information about Flow, Next Best Action, Lightning Pages, and more.

In the Datatable component has begun to show related field IDs instead of the name and URL, even when specified, for related object fields. Has anyone see this or found a workaround to this? 

 

This bug started to show up in both Preview and non Preview sandboxes (haven't deployed this to production yet) for us a few weeks ago. 

 

I updated to 4.3.7 today and it is still present. What is

really

odd is two things: 

1. Administrator users do not experience this bug. 

2. When using Debug in Flow and running as another user, it renders properly. 

 

The screenshot below shows the datatable component and the out of the box Datatable component that is due out in Summer '26, where it renders properly. 

 

I have an open ticket with Salesforce support, but they have been "researching" for a few days now and it would be helpful to know if this is something bigger than our implementation or if there is a workaround. 

 

 

Thanks!  

 

 

Bug in Datatable (even in 4.3.7) URLs for related fields

 

 

3 answers
  1. May 28, 9:58 PM

    Hey All, 

     

    I heard back from Salesforce. The issue here is as follows (per Salesforce support):

    The ers_Datatable Lightning component renders lookup fields as clickable links by enriching the row data through its Apex controller (ers_DatatableController.getReturnResults). Inside getColumnData, lookup fields are only added to the lookupFields collection when the running user has Edit (Updateable) access to the field:

    when 'REFERENCE' {

    if (dfr.isUpdateable()) {

    lookupFields.add(fieldName);

    }

    }

     

    In other words, the documentation on the UnofficialSF website is might need some slight wording adjustment. That is, the user in question needs EDIT permissions on the field itself, not the just the object that the datatable is listing records for. 

     

    In case it helps anyone, I compared to the standard/out of the box datatable links to related records feature due in the next update and the "Edit" permission is not required. I do think the standard datatable component is still lacking a large number of features, though.

0/9000

In my research, I came across this UnofficialSF component: 

https://unofficialsf.com/save-and-update-custom-metadata-records-using-flow/

 

There is a link to this YouTube video that is using older Flow pages, so it isn't totally clear what's going on. 

https://www.youtube.com/watch?v=VdmSd4qemhs

 

I also found this:  

https://help.salesforce.com/s/issue?id=a028c00000smLF8AAM

  which contains a code snippet that I managed to get to work.  

 

Is anyone using this Flow Action who can lend a helping hand? 

 

Thanks, 

Pierre 

 

@Salesforce Flow Automation

1 answer
  1. May 28, 11:01 PM

    After a few hours of trial & error, I got this to work. YAY!!! 

    Since this flow action actually creates a deployment, checking in Deployment Status helps figure out what's wrong. 

    Since I only have one single record in my custom metadata type, I need to update the AccountID field with the record ID of the account the user is viewing. 

    Attaching screenshots of what I ended up doing in Flow.  

    After a few hours of trial & error, I got this to work. YAY!!! Since this flow action actually creates a deployment, checking in Deployment Status helps figure out what's wrong.

     

     

    CMDT_Flow2.png

     

     

    CMDT_Flow3.png

     

     

    CMDT_Flow4.png

     

     

     

     

0/9000

Hi, 

 

I’m unable to get the email template working. I tested using both the email template ID and the template name (once at a time ) however, the HTML body is not being rendered in the outgoing email. Can someone advise if there is something I am missing ? 

 

 

email template  not working with send better email action

 

 

image.png

 

 

1 answer
  1. Apr 22, 7:51 AM

    Hello @Deepika Gali

     

    If you are using an email template, do NOT put any value in the Subject field. Doing so causes the email template to basically be blanked out. Please check !!  

     

0/9000

I have the most recent version of the Flow Base Packs and the Datatable.  All experience cloud users are assigned a permission set group and the perm sets that are installed with these packages are included in that PSG.  Attached are some debug logs I ran on a user reporting the issue.  As well as some Chrome developer tool results.  I have no idea how to fix this.  The datable is not a fancy setup in the screen flow.  It just displays a list of contacts.  Prior to the screen I have the contacts sorted by 3 fields that are check box fields.  Any help would be appreciated. #Unofficial SF #Datatable #Flow #Automation @Eric Smith

Upgraded Datatable Throwing Error for Some (NOT ALL) Experience Cloud Users

 

Screenshot 2023-09-21 at 8.19.28 PM.png

 

Screenshot 2023-09-21 at 8.21.55 PM.png

 

Screenshot 2023-09-21 at 8.22.04 PM.png

 

Screenshot 2023-09-21 at 8.22.10 PM.png

 

Screenshot 2023-09-21 at 8.47.08 PM.png

 

Screenshot 2023-09-21 at 8.48.27 PM.png

 

Screenshot 2023-09-21 at 8.48.58 PM.png

 

Screenshot 2023-09-21 at 8.49.13 PM.png

 

Screenshot 2023-09-21 at 8.49.44 PM.png

10 answers
  1. Apr 17, 6:28 PM

    @Justin White I'm checking the option called  Open links in the same Tab

    to open in same tab for my Console app, stil it is opening in New Tab. Did you came across this issue by any chance. 

    Appreciate your answer.

0/9000

Hi the problem I am running into, i have a screen flow where community users upload files, but from mobile devices the files are not being uploaded, from any other pc it works fine, except for mobiles. 

 

The file uploading screen does not appear even when the files have already been uploaded. It seems that those two components are not triggered. I have not yet found out what is going on, I hope you can help me with this problem. 

4 answers
0/9000

I think I know the answer to this, but wanted to validate.  The Quick Choice component that is now in the Flow Base Pack is different than the "old" Quickchoice FSC component.  Is that correct?  The primary reason for the ask is that I am trying to do some org clean up on Apex Classes, etc and some classes attached to the Quickchoice FSC component is causing some deployment issues. 

 

I should be able to remove that old Quickchoice component without any issues, correct? 

 

#Nonprofit #Flow #Salesforce Admin #Unofficial Salesforce

1 answer
  1. Apr 10, 6:44 PM

    Hi @Heath Parks

     

    Yes - they are different components. The old FSC Quickchoice is legacy and separate from the Flow Base Pack version.

    You can remove the old one if nothing in your org is referencing its Apex classes/flows. Just verify dependencies first in a sandbox. 

     

    If you find this helpful feel free to mark it as Best Answer !!!! 😊 

    Thanks and Regards.

0/9000

We use the Salesforce Mobile app for several processes like guest check-in. Recently (in the past month or so) we've seen intermittent slowness when users navigate between flow screens (20-30 seconds where it used to be 1 second or less). 

 

Here's what we've noticed/tried so far:

  • Happens most often when the device is idle on a flow screen for more than 3-4 minutes. Exiting the app to the home screen seems to help prevent it.
  • We tried having users refresh the flow before using it; helped at first, but does not seem to work anymore.
  • Deleting the app and reinstalling will help for about 1 day before the issue comes back
  • Flow runs fine on desktop and shows no issues when debugging.
  • Reasonably sure this isn't a connectivity issue, as we've tested on several networks as well as cellular
  • Seems to not be related to a specific device; we've tested on iOS and Android, across several different OS versions
  • We've updated all UnofficialSF base packs, FSCs, and Actions to the most recent available version
  • To this point, Salesforce Premium Support is unable to find any issues in the flow itself and have not been able to recreate the issue.

There's a lot at play here and I'm relatively new at developing flows, so any insight is welcome. I'm not convinced this is an issue with the UnofficialSF packages, but Salesforce support seems to think so. 

 

Has anyone else had similar issues? 

Are flows not intended for this kind of volume (sometimes thousands of scans in a given day) or to be left idle for long periods? 

Any troubleshooting steps you would recommend that I haven't tried yet?

1 answer
  1. Apr 4, 5:05 PM

    Had similar issues with flows on mobile. Few things that helped us. 

     

    Most likely culprit.

    The Salesforce mobile app aggressively caches and the webview session goes stale after a few minutes of idle. That 3-4 minute pattern you're describing is classic. The app suspends the webview, and when it wakes back up it has to re-establish the session. That's your 20-30 seconds right there. 

     

    Things worth trying:

    • Auto-refresh on the flow screen. Add a timed screen component or a subflow that keeps the session alive. Basically a heartbeat so the app doesn't think it's idle.
    • Check for reactive components. If you have reactive variables or dynamic choice sets that re-query on every screen load, those stack up fast on mobile.
    • Pull out UnofficialSF components temporarily. Swap them with standard ones on a single flow and test. Support isn't wrong to point there, custom LWCs in mobile flows have known performance quirks. At minimum it rules it out.

    On the volume question.

    Flows handle the volume fine but the mobile app is the bottleneck, not the flow engine. The app wasn't really built for kiosk-style usage where it sits open on one screen for hours. If this is a dedicated check-in device, try running the flow through mobile browser instead of the app. You lose push notifications but the webview is way more stable. 

     

    Also worth opening a case specifically about mobile webview session timeout behavior. 

      

    That's a known area Salesforce has been working on.

0/9000

I have a flow screen where I want to make a section only visible if the quick choice value does not start with a string.  Other fields react to the values chosen, but not the visibility.

 

editWOfaultCode is the screen quick choice field.

My formula is boolean, BEGINS( {!editWOfaultCode.value}, "Part Needed for"  ).

Then the field's visibility checks that the above formula is false before making it visible.

 

However, the field remains visible no matter what I do.  I can create a checkbox field on the screen, set it to this boolean formula's value, and then set the visibility based on this checkbox field.  However, then I have an extra field on the screen and making it not visible renders it useless. 

 

Any ideas?  I'm trying to avoid navigating to another screen.

  

@Solo Admins@Salesforce Flow Automation@MVP Office Hours (US)

6 answers
  1. Eric Smith (Retired) Forum Ambassador
    Feb 8, 2024, 1:46 PM

    Reactive formulas do not apply to visibility on a Flow screen.  To get around this I've created a reactive screen component whose output can be used for conditional visibility.  Just pass your formula in as input and use the output for the conditional visibility setting for the section.  It is included in the FlowScreenComponentsBasePack.  See this video for a sample use case.

0/9000

I've actually had this problem for years now, but I only periodically try to fix it... I can't upgrade UnofficialSF's Quick Lookup because I get these errors when I try: 

 

Package: quickLookup (04t5G000003zgYw)

Error Number: 1216316176-46277 (-539558448)

Problem:

1. ApexClass Invalid type: schema.Location

QuickLightningLookupController: Invalid type: schema.Location

2. ApexClass Variable does not exist: lstRec

QuickLightningLookupController: Variable does not exist: lstRec

3. ApexClass Invalid type: schema.Location

QuickLightningLookupController: Invalid type: schema.Location

4. ApexClass Invalid type: schema.Location

QuickLightningLookupController: Invalid type: schema.Location

5. ApexClass Incompatible types since an instance of schema.Location is never an instance of SObject

QuickLightningLookupController: Incompatible types since an instance of schema.Location is never an instance of SObject

6. ApexClass Dependent class is invalid and needs recompilation:

 Class QuickLightningLookupController : Invalid type: schema.Location

QuickLightningLookupControllerTest: Dependent class is invalid and needs recompilation:

 Class QuickLightningLookupController : Invalid type: schema.Location

 

 

I'm not sure what to do. After looking for solutions online I tried changing the API verion of QuickLightningLookupController and QuickLightningLookupControllerTest to something higher (62) and that didn't change anything. I also tried recompiling all classes before doing the upgrade. The recompile succeeded but the upgrade still failed. It fails regardless of if I choose "Compile all Apex in the org" or if I choose "Compile only the Apex in the package."  

 

I can't uninstall and reinstall the entire thing because I have so many Flows and Flow versions referencing that component. Does anyone have any suggestions?

2 answers
  1. Mar 19, 4:13 PM

    I don't think I can? If I try to delete the installed package it complains because the component is being used in many flows and many versions of those flows.

0/9000

Hi All - I've been implementing some new Flows utilizing the excellent blog posts that combine usage of the UnofficialSF Datatable and the Salesforce Labs Flow Launcher (here

, if you're interested), and I've come across an interesting issue. I emailed Josh Dayment about the issue but he cannot replicate on his side. 

 

Specifically, when I have a Datatable, the Flow Launcher component either does not see the Datatable component. In other other Flows it will see the component but not allow me to select the Actioned/Selected Row as the Input record. See Screenshots below - the second will show that the datatable component does not appear for selection.  

 

Has anyone else encountered this? My current workaround is to have a Screen Action take in the Actioned/Selected Row and just pass it back as the Flow Launcher plays well with a Screen Action Subflow. 

 

Datatable issue with the Salesforce Flow Launcher?image.png

 

 

 

 

4 answers
  1. Mar 5, 6:27 PM

    Hi Cormac - you'll get a better response if you post up a new question rather than a reply. 

     

    I'm not sure if your setup, but keep in mind that the Action buttons do not navigate and they populate a different variable called "outputActionedRow" rather than "outputSelectedRow". I've had successful usage of the Actioned row in many of my Flows, so just ensure you're updated to the latest versions of the base component packs and the datatable as well.

0/9000