Skip to main content
小组

UnofficialSF Discussion

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

Hi all, 

 

I recently encountered a weird quirk with the "convert records to CSV" capability in the UnofficialSF base pack. 

 

This eventually led to a known issue, created recently:

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

 

 

The short version is that if you are getting really fancy and using a Screen Action to pass back a record collection that you want to convert to CSV, you'll need to re-query that collection in the "top" level Flow until they fix this KI. 

 

Hope this helps in case anyone does a search or runs into this behavior.

1 条评论
  1. Eric Smith (Retired) Forum Ambassador
    8月31日 21:04

    Thanks for the details.

0/9000

I am using the Quick Choice component from the Flow Base Pack (the app exchange version) The data source is Picklist Field, I have it set to required and in the Value field, I have Default, as I have a default value set on the record type and picklist field. The default value is "Employer", however, when running the flow the default value is not showing up and even though it's marked as "required" it's still progressing in the flow and then erroring out as "Default" is not an acceptable value. It just started happening to my knowledge, so any ideas on what could be causing the issue? 

 

Here is a screen shot of the settings, notice that it's set to required as well  

 

Quickchoice not displaying

 

Here is what it looks like in the screen flow, notice there is no value in the quickchoice field, it should be set as Employer. 

Quick Choice Default 2.png

 

In debugging I did not put in any value for the field, and it advances, even though there is no value. and then errors out as "Default" is not a valid option. 

 

Any thoughts/suggestions are welcome 

#Quick Choice Set Component #Unofficial SF #Salesforce Admin #Flow

1 个回答
  1. Steven Trumble (Strum Consulting) Forum Ambassador
    8月7日 00:27

    When you type "Default" you are passing the literal string of "Default" to the quickchoice.  

    There is no label associated with "Default" which is why it appears blank in the UI,but then tries to save as "Default". 

     

    Check out the documentation on unofficialsf. Notice how they are passing in variables from the flow 

     

     

    When you type

     

     

0/9000

Hello from down-under. 

 

I am a long-standing user & fan of the flow Datatable component. 

 

I recently built new flow which incorporates a need for the user to select a different picklist value for an account field update. The trouble is that with the record displayed at the bottom of the table, the picklist values are obscured and it's a super-fiddly process to try see & then and scroll through the values and attempt to make a selection. I've struggled to think of any method around this and I'm wondering if some design change that I'm not aware of could help. If possible, just adding more space between the bottom-most record and the table boundary would be a simple solution. 

 

Keen for input to asisst. 

 

Thanks in advance, 

Steve 

Hello from down-under. I am a long-standing user & fan of the flow Datatable component.

2 条评论
0/9000

I'm trying to edit a percentage field in a datatable component with two decimal places, for example (8.55% = 0.0855), but I get the error " Your entry isn't a valid increment." for any number that I put to the decimal point that is different from zero. Can anyone help or has been through this?

@Eric Smith

DATATABLE - Edit percent fields with 2 decimal places

4 个回答
  1. Eric Smith (Retired) Forum Ambassador
    7月7日 16:32

    Thanks for the step by step instructions @Gabor Nemeth.  I'll put this in the official documentation.

0/9000

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 个回答
  1. 5月28日 21:58

    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 个回答
  1. 5月28日 23:01

    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 个回答
  1. 4月22日 07:51

    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 个回答
  1. 4月17日 18:28

    @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 个回答
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 个回答
  1. 4月10日 18:44

    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