The latest update to the Datatable component adds a few new requested features and fixes some minor bugs. One new addition is Custom Labels for some of the interface text to easily allow for translation to other languages. Another new feature is the addition of support for Screen Readers for the visually impaired. More objects […]
The latest release of the Datatable component adds a major new feature. You can now Save and Retrieve settings for your Column Configurations. If you find yourself adding identical or similar Datatables to multiple flows, this will be a tremendous time-saver. Check out the updated documentation for all the details on how to take advantage […]
This new Datatable release includes two new features and a few minor bug fixes. Because the outputEditedRows attribute is not Null even if no rows were edited nor included in the output collection variable, I’ve added a new output attribute numberOfRowsEdited that can be used to check if any rows were edited. I’ve also updated […]
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 […]
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 […]
I have released a maintenance update for the Datatable component. Current Version: 3.2.1 Updates: Picklist values can now be restricted to a single record type per table Bug Fixes: Text formula fields will now wrap correctly (This had regressed in v3.2.0) Output Selected Rows is no longer null if the screen containing the Datatable also has a Section component See the complete list in the Release Notes
A huge thanks to Guillaume Davies and Jerry Poon from Accenture in Sydney Australia for sharing their solution for supporting Picklist Field editing in the Datatable component. Download the latest version (3.2.0) of Datatable to take advantage of this new and often requested feature. Currently, all available picklist values will be made available for selection […]
I have released Version 3.1.1 of the Datatable component. Please note that you will first need to update to the latest versions of the FlowActionsBasePack and the FlowScreenComponentsBasePack. Updates: Moved the “Display ALL Objects for Selection” choice in the CPE from Advanced to Data Source Added an attribute to hide all column header actions such as Sort, Clip/Wrap Text and Filters If Multi-Currency is enabled, convert currency field values to the User’s currency (Thanks to Novarg1) Bug Fixes: Text formula fields will now wrap correctly Display ALL Objects for Selection attribute is now persistent Input data is Apex-Defined attribute is now persistent The number of pre-selected rows will now not exceed the Maximum Number of Records to Display attribute value Don’t require the key field to be explicitly listed in the Column Edits attribute for Apex Defined Objects The Clear Selection button will no longer appear on single row tables when Disallow row selection is checked The Clear Selection button will clear the Output Selected Rows (User Defined) attribute for Apex Defined Objects Fixed the column filtering on Checkbox Fields when the filter value is ‘false’ Fixed the vertical alignment of the table header text
Thanks to vijayignatius, we have a new option for the Lookup component. He has provided a new attribute that lets you pick a field other than the Display field to be used as the the field to search on. Read on for his excellent overview of why and how you can use this new feature. […]
Flow Datetime Methods Created by Carl Vescovi This Post was most recently updated on: 9/1/23Updated package linksCurrent Version: 1.0 At the moment Datetime and Business Hours are not particularly well supported in Salesforce Flows. The intent of this code is to be a gap filler until such time as Salesforce delivers more functionality. The way this code […]