Salesforce ETL, querying current value of Salesforce field - DocGen

Hi @VI3DS, 

It looks like we do not have anything documented on our support site. However here is an overview of the step properties: 

Salesforce Object Type (required) = Asking for the API name of the Salesforce object to query.
Salesforce Object Id (required) = Asking for the 18 digit object ID to query. This is likely passed in at the start of the workflow.
Radio Button Options (one option is required) = Choose one of these options to query Salesforce with
Configuration Document = Something like a text file with which you've built the query
Configuration Variable = Variable that contains the query
Configuration Document Generation Form  = *Simplest option in my opinion* Document Generation Form which contains the fields to query from Salesforce. The form and fields are all connected to Salesforce. See screenshot for example. No doc gen configuration is needed - just the form. 

Output (not required but useful) = Set your variable to store the output of the query which will be the requested data from Salesforce 

Sample workflow step properties:

Sample document generation form (for a different object then the above screenshot):

I hope this provides you with some good guidance for moving forward!
Kelly

Hi Everyone!

May I ask if there is a way to use that expression builder if the Configuration Document Generation Form is selected. The reason for this is the form that we will be using is dynamic so I need c# for it. The problem is it does not accept it when I am trying to return the Document Generation Form Name. Can you help me with this? It would really help a lot.

Thank you!

How about 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?