SharePoint calculated column blank in Adobe Sign

[ElvirBotic]

Hello, all, 

I am working on a Power Automate flow to capture responses from a form and when the form is submitted I have a question that retrieves property information from a property list we maintain and I concatenate the street address, city, state, zip to populate an Adobe Sign document and send it for signature to the appropriate approvers for that property. Prior to sending the document for signature I copy all responses to a SharePoint list and then I use the SharePoint fields to populate the Adobe agreement, however when I use the calculated column from SharePoint containing the 'Complete Property Address' it shows as blank in my Adobe Sign. I have tried using the compose function as well, but had no luck. Anyway, to use calculated columns in an Adobe Sign to not be blank?

 

[ScottShearer]

@ElvirBotic 

I can't use the Adobe connector so I can't test but calculated columns are problematic in Power Automate.  I suggest recreating the value that should be in the calculated column in your Flow - use expressions to recreate the calculation.  You can use a Compose action and reference the Compose to populate the Adobe agreement or use the simply use an expression when populating the Adobe agreement.

[ElvirBotic]

@ScottShearer I have attempted a compose action, but I can never see the full list of dynamic content. Do I need to do something to be able to retrieve the steps? I am doing the compose after my "get building details" step which is using the filter query property to find the specific address in our property list. 

Do I need to do something else after I "Get building details"?

[ScottShearer]

@ElvirBotic 

This behavior is Power Automate trying to be helpful 🙂

You need to refer to the column in another way - the syntax can be confusing.  The easy way to do this is to use a Compose action to refer to the column.  Then, click on Peek Code to see how to refer to that column.  Remove the @ before the expression.  Add the code to your expression.

When done, when, remove the unneeded Compose actions.

Alternatively, you could just add Compose actions to refer to each column.  Then refer to the Compose act6ions in your expression.

[ElvirBotic]

@ScottShearer I just tried creating a compose for each part of the address but it puts everything in an apply to each and when I did that and set up an email to see what kind of information it would return. I only had the option to use "current item" which was a bunch of odata information. Although it had the address of the property it carried with it all of the additional columns from our lookup list. I did not think it would be this tricky to be able to concatenate an address together. 

[ScottShearer]

@ElvirBotic 

Please post a screen shot of you Flow.

[ScottShearer]

@ElvirBotic 

Please post a screen shot of you Flow.

[ElvirBotic]

@ScottShearer Here is the entire flow. The only last steps are once the adobe agreement is signed to add the signed document to the SharePoint list item. 

My compose was in between "get building details" and the "empty array for no attachments" 

I was able to concatenate the address, city, state, and zip and save it to SharePoint. I then used the entire address from SharePoint when mapping the columns for the agreement, but it returns null.