Wire services fire initially before any flow data is loaded into an lwc’s public properties. If you’re using flow inputs to drive those wire services, like this: …keep in mind that your function will have to deal with that initial result that comes back, which will often be something like undefined. What you want to […]
Author Credit: Eric Smith assisted in the development of this material Because invocable actions make great building blocks, there’s an increased risk that you’ll have a collision if you’re using unmanaged packages, so managed packages are generally recommended (and unless you have IP you want to keep confidential, we also recommend you simultaneously make the […]
PREVIEW Requires Spring ’20 Org The first upgrade to the Collection Processor package is available. Count Records And Fields takes a collection of records and returns a count. Optionally also takes a field name and a field value, and then also counts the number of records that have that particular value for that particular field. […]
Every Flow is completely represented by a single piece of XML metadata, and you can download a Flow xml file, modify it, and redeploy it. But of course, you don’t. Because it’s dangerous to hand-modify the XML. It’s easy to break things down there in the basement. So we try to provide Flow users with […]
We’ve added a new wiki page covering Flow Stages. As is the case with most buildouts of the wiki, this isn’t about a bunch of new content but more of an aggregation of all of the known existing good content on a single focused topic page. As such, everyone should feel encouraged to add good […]
Narender builds on his “world’s first” blog post on invocable actions that use the new Spring ’20 generic SObject support with a new post that shows, for the first time, an action that carries out SOQL and can be used declaratively in any object scenario. The heart of his action is this line: string query […]
Tigerface has posted a free version on AppExchange of their upcoming Datatable solution. The thing that really jumps out at me is that they’ve addressed the core limitation of the existing unpackaged datatable flow screen components: its inability to support more than a modest set of standard object types. Tigerface appears to be solving this […]
This action provides a range of navigation choices available in a single, straightforward navigation action for Flow. It provides support for navigation from a flow to: a record page (in edit or view mode) a new record form for an object (Note that you can use flow to pass initial values to the form) a […]
With the publication of the RecordDetail flow screen component, it became easy to get flow to show any list of field names you choose to give it. In many use cases, you might want to leverage your existing Layouts, particularly in situations where you’ve customized layouts on a per-record-type basis. Other recent tools make it […]
Layouts often differ substantially from recordType to recordType and from profile to profile. This action takes a recordTypeId and a profileId and returns that combination’s current LayoutId. One use of this is dynamically generating flow screen layouts with the RecordDetail flow screen component. To do this, after using this action to retrieve a LayoutId, use […]