![]() The resulting flow uses a collection operator. The tooltips in Flow Builder are completely overhauled and have a lot of extremely timely tips they’re not just simple definitions. I needed to restructure my flow and got a key hint from a brand new tooltip: ![]() When flow loops, Salesforce prepares a single transaction so it can commit all of the loops with one database action, in the name of resource conservation. I had forgotten that you can’t use a callout (here, the flow action is “calling out” from Salesforce to the quip api endpoint) in the middle of an open Salesforce transaction. When I ran the flow in the debugger, though, I got this error: In my first attempt at setting up the flow, it looked like this: Side Discussion 2: Mixing Callouts and Transactions If I try to immediately update the Contact as soon as I get the data out of the Quip document like this: You don’t have to actually use these variables, but if you take the time to define them, then any error messages you get will show up in the debugger like this: Here I’ve created variables to map the Error Message and Is Success outputs. This is one of three ways you can specify a specific cell value:ģ) Finally, map the retrieved values from the Quip document to flow storage variables so you can use them later in the flow: Start with a contact name, generate the ConstructedName using that formula, and pass it in to the flow action:Ģ) For each piece of data that we want to extract from the quip doc, we reference it by specifying the label value of the cell to its immediate left. Provide the name of the corresponding Quip doc.To configure the Get Quip Sheet Data flow action, we do the following: (Note that this uses the new Spring ’19 Flow Builder):Ī key element of this is that the name of each quip document is formed using a Flow formula: If each of those employees has a Quip document and a Contact representing them, the documents can be used to display data from Salesforce and collect data from the employees. One scenario where this can be useful is when an enterprise has employees that don’t have Salesforce licenses. ![]() In this example, Quip docs have been created for different Salesforce contacts. Here are some examples: #1: Update Salesforce with Data From Different Quip Docs The new Quip Flow Actions for Salesforce Flow open up new ways to combine the shared, universal accessibility of Quip with the power of Salesforce.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |