cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Philip_Worrell
Advocate II
Advocate II

Compose steps output getting corrupted

Today I had an issue I have not seen before. 

 

A cloud Flow that generates email using a couple of compose steps from data in a SharePoint list to create the TO: and CC: lines. 

The compose steps had been through a number of tests. I had not used them live int he flow until this morning when I set the final email recipients to the To and CC compose steps. 

 

The flow uses a lot of these and I had verified the concatenate expressions making sure everything was a string and separated by a semi colon. I did this on 3 individual steps this morning. 2 out of three have no issues. 

 

The error I got back was 

 

Unable to process template language expressions in action 'Send_an_email_from_a_shared_mailbox_(V2)_22' inputs at line '1' and column '98775': 'The template language expression 'outputs('Compose_-_To_3a.1')?['$']' cannot be evaluated because property '$' cannot be selected. Property selection is not supported on values of type 'String'. Please see https://aka.ms/logicexpressions for usage details.'.

 

When I looked at the flow the outputs of the compose items had all changed to $. 

 

Philip_Worrell_0-1633959994049.png

Removing and readding didn't work. Tried several times. Tried adding a new send email action. That didn't work

I had to create new compose steps before it would work again. 

 

The Output kept being replaced with $. 

That $ was equal to

@{outputs('Compose_-_CC_3a.1')?['$']}

 

when it should have been 

@{outputs('Compose_-_To_3a.1')}

 

I am wondering it my Compose name had anything to do with it as it contain a .1 in the name. 

 

Anyone seen this before? 

3 REPLIES 3
ekarim2020
Super User
Super User

Can you show a screenshot of the expressions used in the Compose_-_CC_3a.1 along with some sample data the reproduces the problem?

 

Ellis

A bit difficult to do that without exposing email addresses. 

It is a concat statement with a bunch of compose, variable and hardcoded email addresses in it. I have been using it a lot without issue. 

DanBlack
Regular Visitor

I have had this issue for a while now. This output should be:

  • outputs('ACTION_DESCRIPTION_4.0')

But it keeps changing to this:

  • outputs('ACTION_DESCRIPTION_4.0')?['$']

The workaround up until now has been:

  1. Delete the reference to the Compose (Outputs) field in each of the Send an email actions
  2. Delete the Compose action - usually doesn't let me delete it unless I save the Flow, close and re-open
  3. Recreate the Compose action
  4. Renter the Compose (Outputs) field into each of the Send an email actions

BUT this particular one is giving me grief. I have tried five times now with the same result. If I leave this as it is the email will fail to send in any of the CATCH scenarios.

DanBlack_0-1638342624028.png

 

Helpful resources

Announcements
MPA Virtual Workshop Carousel 768x460.png

Register for a Free Workshop

Learn to digitize and optimize business processes and connect all your applications to share data in real time.

New Process Advisor Capabilities carousel.png

Read the blog for the latest news

Read the latest about new experiences and capabilities in the Power Automate product blog.

May UG Leader Call Carousel 768x460.png

What difference can a User Group make for you?

At the monthly call, connect with other leaders and find out how community makes your experience even better.

PA Survey Carousel Image.png

We want to hear from you!

If you are a small business ISV/Reseller, share your thoughts with our research team.

Users online (1,717)