New condition error - no issues for months

(0) Share

Report

Posted on by wiredupjax

195

Dear community,

I have been running this flow flawlessly for 7 months. About 2 weeks ago, the flow is now failing with the following error: (I'm wondering if this is w/ the new condition)

InvalidTemplate. Unable to process template language expressions in action 'Willow_Lawn-Send_Internal_Email_Notification' inputs at line '1' and column '2486': 'The template language expression 'body('Set_Insurance_to_60d-Window')['first_x0020_name']' cannot be evaluated because property 'first_x0020_name' cannot be selected. Please see https://aka.ms/logicexpressions for usage details.'.

Any ideas why?

Categories:

General topics

I have the same question (0)

All responses (2)

Answers (1)

v-bacao-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @wiredupjax ,

Could you share the full screenshots of Flow configuration?

It seems that the problem is not related to the configuration of Condition. The error displayed by the error message is related to the configuration in "Willow_Lawn-Send_Internal_Email_Notification" action.

Please check if the first name property has been changed. If there is any update, the content configured in the action also needs to be updated.

I recommend that you reconfigure an identical Flow to configure actions based on the properties of the current version of the relevant data source.

Please take a try and see if issue still exists.

Best Regards,

Was this reply helpful? Yes No
Verified answer

wiredupjax 195 on at

Like (0)

Report
Copy link

Link copied!

ISSUE RESOLVED but not necessarily how you would have expected.

A secondary DECISION TREE was failing based on a previous SHAREPOINT UPDATE record. The DECISION TREE was failing because it could not access a field from the RECORD associated with the SHAREPOINT UPDATE item. While this worked before, it was now failing for an unknown reason.

SOLUTION:
I removed all of the ITEM FIELDS associated with the SHAREPOINT UPDATE item throughout the flow. I had some help identifying the dependencies through the PEAK CODE option finding the reference to the title of the workflow item.

Once they were all set to the SHAREPOINT START item that kicked off the process, FLOW began to function correctly.

Was this reply helpful? Yes No