Andy in the Cloud

From BBC Basic to and beyond…

13 thoughts on “Introducing the Dynamic Flow Component

  1. Pingback: Introducing the Dynamic Flow Component — Andy in the Cloud – SutoCom Solutions

  2. Thank you for sharing great article related to dynamic flow. i want to contribute article related to salesforce.

  3. Your video tells us how to create a childrecord via the Utility bar. We want to make a button (on account for example) that calls the flow that creates a child record (opp) and opens that record. Can you tell us how to do that

    • Sure just drag the Component on the record page and it will Work just the same. If you want an actual button displayed along with the others, that’s something on my backlog

  4. @Wilfred Lammers

    As of Spring 18 can create a button to launch your flow via Quick Actions

  5. This is really great idea. One thing I can’t seem to get passed is its use in custom objects that end in Customobjectname__c. How does one add it as a custom metadata type under Setup?

    • Have you tried putting Customobjectname__c into the Dynamic Flow Component Name field?

      • I hit the same issue–
        When you add a custom object name, like Invoices__c, to the Dynamic Flow Component Name field (as directed in the utility bar message) the error returned is:
        “Custom Metadata Record Name: The Dynamic Flow Component API Name can only contain underscores and alphanumeric characters. It must be unique, begin with a letter, not include spaces, not end with an underscore, and not contain two consecutive underscores.”

        Second note: instructions say that you have to tell the component that your flow is an autolaunched flow, by marking the custom metadata record somehow, but there’s no field in the metadata record that seems to be for that purpose.

        Thanks! Once I solve this, I’ll write up a blog to use this tool to redirect to the child record from the standard New record UI. I hope! 🙂

      • Ok let me take a look at this, will get back to you soon.

      • This has been fixed in v2.5. Also in this release, you do not need any special consideration for auto-launched flows, so do not worry about what the instructions say in respect to this. I will update the instructions to remove this reference.

  6. Pingback: Dynamic Flow component – Deepthi Thati

  7. Pingback: Tools | Andy in the Cloud – Kay Scott's Blog

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s