Salesforce ETL step

Based on the error message, it looks like this is looking for the Guid that corresponds to the FORM you have created.  If you click on the Form you want want to use, you can grab the “configUid=...” portion of the URL and use the guid that is available there.  You will need to create a mapping or use logic if you are planning on substituting the guid, and vis-a-vis the form, for different scenarios.

This will require special consideration as part of deployment as the Id’s will likely be different in UAT vs. PRD.

Thank you for your response. The approach you suggested should work, but given that we have over 30 or 40 DocGen forms in use for this process, maintaining them could become quite challenging. Additionally, as you pointed out, the IDs differ between UAT and production environments, which adds another layer of complexity.

How I wish we could simply use the DocGen Configuration name in the expression builder instead of manually extracting the UID from URLs. It’s odd that while the input selection shows the form names, we can’t use them directly in the expression builder.

I appreciate your help and will consider how best to manage these differences. Thank You again, Scott.

Thank you for the suggestion! This is a brilliant idea, and I’ll probably give it a try. It seems like a great way to simplify the configuration and handle the differences between UAT and PRD. I’ll keep you posted on how it goes.

Thanks again for your help!

Is there an example of using the ‘Configuration Variable’ with A SOQL Query in an Update Variable Value Step?

https://support.docusign.com/s/document-item?language=en_US&bundleId=yks1643320936212&topicId=man1576610096178.html&_LANG=enus

Configuration Variable: Specifies an XML variable whose value contains a valid SOQL query describing the data to read from the Salesforce record. The variable’s value must also contain the schema of the output variable that stores the result. A configuration variable works similarly to a configuration document, except the XML variable’s value gets crafted directly in the workflow. In the Update Variable Value workflow step, you use an expression to craft the SOQL query. The step then assigns the query to an XML variable. Use a configuration variable when your query contains dynamic parameters. The parameters can be dynamically inserted into the SOQL query when using the expression. An example is a query with a WHERE clause that uses a data point whose value might change for each workflow.

The ETL step keeps failing; what would the Update Variable Value step look like?