Which is coercion failed in this workflow?

Which is coercion failed in this workflow?

Coercion Failed: Unable to transform the input lookup data into the requested type. The Workflow has one people picker column, one lookup column and 4 text columns. We work in our WF with the “collect data from user” and add this information to a field in our list.

What is the failure of coercion in SharePoint?

Coercion Failed: Unable to transform the input lookup data into the requested type. Workflow Scenario Consider a SharePoint list called “Employee” with following schema. We create a SharePoint Designer workflow to send a simple email with Employee Name and Country when an item is created.

What is the problem with SharePoint Designer workflow?

I have a huge problem. We created a Sharepoint Designer Workflow. It works fine for more than one month. Yesterday we got an error message: Coercion Failed: Unable to transform the input lookup data into the requested type. The Workflow has one people picker column, one lookup column and 4 text columns.

How is the coercion problem similar to the post?

This problem is similar to this post: Coercion Failed: Unable to transform the input lookup data into the requested type.

What does a data type error in workflow mean?

There is a data type error wherein the workflow is trying to set a value in a field in the list item using the wrong data type. You should confirm that the Return Field As operation in their lookup is of the correct data type. This indicates there is an error in the workflow logic.

Why does my workflow fail the first time?

I have a workflow that is assigning a task based on a lookup value. This workflow runs successfully the first time then fails on subsequent attempts. Here’s how the data looks: Why would it work once and then fail? I have isolated this as the issue because if I hard code a Plant Title it works every time.

Is there a problem with the SharePoint Designer list workflow?

SharePoint Designer Workflow problem with Lookup column There is a particular scenario in which you might receive the below error if using SharePoint Designer List Workflow. Coercion Failed: Unable to transform the input lookup data into the requested type.

How to deal with coercion in SharePoint workflow?

The solution to this is converting the Lookup value to a string and then using it in workflow stages. Create a Workflow Local Variable named “country” of type “string”. Modify the workflow by adding an if condition to check if the Lookup value is not-empty (is not empty). Add further stages after the if condition. Add an else condition if required.

What happens when a workflow is canceled in SharePoint?

Though the workflow is pretty simple. We note that it worked fine where lookup values are the United Kingdom, United States, Spain, Australia, but fails when the lookup value is blank. It gets ‘Canceled’ in this case. If we look closely at the workflow history, it shows these details –