Are you looking for a taste of what you can find on here on Unofficialsf.com? How about some ideas on how to put some of the more popular Flow Components found on this site to work for you? Are you looking to improve how your users interact with your Lightning Record Pages?

Find all that and a few other ideas from a presentation I’ve given at Dreamforce and various other Salesforce events around the world. This recording is from the London’s Calling event held earlier this Spring.

I have either created or enhanced most of these components and they are all available, with source code, for free here on unofficialsf.com. They range from simple to complex, but all of them can be used in ways you may not have thought of before to bring out the best in your user experiences. The components are designed to be generic. No coding is required, and all can be customized and configured with built in parameters.

Here’s what Flow Combo Box displayed previously:

As of FlowScreenComponentsBasePack version 2.3.7 and higher, Flow Combobox also makes automatic references available:

The DataMapper package provides two Flow Actions that can be combined in different ways to achieve powerful transformations between Salesforce objects and JSON. We’ll demonstrate this using the JSON created in the example in the Make HTTP Call. In that example, a call is made to a foreign exchange web service and it returns the exchange rates for ALL the traded currencies. But we only need a single exchange rate.

Extract JSON Data

Here’s what the JSON returned by the call looks like in a test callout:

Let’s look at it with a little bit of formatting:

In our example, we want to extract the exchange rate of the US Dollar against the Australian Dollar. We can see that at the moment the above call was made, that rate was 1.2945. Let’s extract that with Extract JSON Data, the first of the two Datamapper actions:

As you can see above, we pass the Body JSON in from the HTTP response and then reference the AUD rate by giving the dot-notation path to it. When you use this action, you provide keys and assign their values to 1 of 20 available outputs. These static outputs are labeled ‘value1’, ‘value2’, etc… and they’re strings. You can use those values downstream in the flow or you can assign them to more memorable variables.

This test output shows the successful extractions:

Map JSON Array: Handling groups of JSON objects

Extract JSON Data is powerful but it has a flaw: you can’t practically use it against arrays. And arrays show up all over the place. Here’s an example from a Slack API that can return 1 or more attachments:

The most practical way to manipulate arrays of JSON data is to map them to a corresponding collection of Salesforce SObjects. That’s the function of the second DataMapper action: Map JSON Array. When you configure this action, you first need to isolate the array JSON that you want to map. Here’s what an isolated array json string looks like:

In our example, we’ll use this json data to create records of type ‘CustomAttachment__c’:

Here’s what the Map JSON Array looks like:

This action will output a collection of the selected Target Object Type, which you can use to create a new set of records or do futher processing:

The keys on the right will be looked for in the individual json array members, and their respective values will be set to the specified output fields.

• Developer Note: The underlying action uses a generic SObject output. The CPE makes sure that a concrete type (in this case, CustomAttachment__c) is provided.
• Developer Note: The variable List Builder mechanism used here has been implemented so that it can be reused easily in unrelated CPE’s.

This action doesn’t currently support the ability to edit/update existing records, but that could be added in the future.

Here’s a view of the resulting Custom Attachment records created using the record collection variable output by the Map JSON Array:

Install

Version 3.0.0.0 Unmanaged 4/21/22 Requires Screen Component Base Pack and Action Base Pack version 3.0 or higher.

View Source

source

Old Versions

rsion 1.1.0.0 Unmanaged 6/19/21 JSON can be mapped to Date fields if it is in the form of a Date.

Version 1.0.0.0 Unmanaged 6/13/21

Today, I’ve released a new version of the Datatable component. I’ve fixed a few minor issues and added a few new enhancements. The key changes are that pre-selected records are showing again, edited date fields should display the correct day (not the prior day) and there is a new Table Behavior option to hide the Clear Selection button on Datatables with radio button selection.

Updates: 3.2.3

• When the running User doesn’t have Read access to the Datatable’s SObject, Record Type Id for Picklist Values is ignored and all picklist values will be available when editing a picklist field
• Fields that are Read Only to the running User can still be edited when the Flow is running in System Mode

Updates: 3.2.2

• Editable picklist fields now show a pencil icon when editable (Same behavior as all other field edits) – Thanks to Jerry Poon
• Icon Pickers in the CPE and Configure Column Wizard have been updated to the latest version
• Added a new attribute to optionaly hide the Clear Selection button that appears on a table with radio button selection

Bug Fixes

• Fixed alignment of picklist fields when selecting Center or Right alignment
• Adjust edited Date fields by the running User’s timezone offset to keep the correct day
• Enforced no edits on fields such as Rollups and Formulas
• Fixed occasional error message about the not_suppressNameFieldLink attribute
• Fixed v3.2.1 bug where pre-selected rows did not display as selected