0

I have a SPD 2010 work flow, that is triggered when a user uploads a document to a library.

The workflow itself is pretty simple.

It updates a field in another list by doing look up on a field in the document being uploaded, and finding a matching record to be updated in the target list.

Its one action long, and should not be problematic.

And I have gone to great lengths to ensure that its not some kind of coercion error brought on by the look up.

Moreover I believe I can logically eliminate the workflow structure and logic itself as the source of the problem, since the workflow has and will run successfully.

The problem is that, although it has run successfully, it only does so rarely.

Most of the time I trigger the workflow, it cancels immediately. Logging only the following error.

Coercion Failed: Unable to transform the input lookup data into the requested type.

and not any of the history logging errors I have placed before and after the action in an attempt to troubleshoot. Which suggests to me that the problem does not lie within the workflow, rather the workflow itself is just failing to run at all.

Any thoughts ideas or even just keywords to google would be a huge help.

Thanks in advance.

Here's the work flow:

Step 1

 Update item in Document Library A

Here's how the look up is configured.

 In  Document Library A

 Where Doc ID Value == Current Item Attached To (Which is a Field which contains Doc ID as a Look Up Value(Text) )
  • If you run the workflow on the same document multiple times, does it sometimes succeed and sometimes fail? Or does it fail on some documents but not others? – Erin L Jun 10 '16 at 15:56
  • The documents don't seem to be a factor since, I can re-upload the same document from my desktop multiple times, and the Files are all essentially the same as well since they are just dummy documents with different names , but the same fields and content. – Timothy Ward Jun 10 '16 at 16:49
  • Can you put up a screen shot of the workflow? – Josiah Jun 10 '16 at 18:01
  • yeah sure thing – Timothy Ward Jun 10 '16 at 18:48
  • actually I can't. So I'll write it out here. – Timothy Ward Jun 10 '16 at 19:28
2

When performing a lookup on a metadata field associated with document, I always added a "Pause for Duration" action of 5 minutes at the start of the workflow. Reason being, uploading a document with metadata is a 2 step process. First, the document is uploaded. Second, the metadata is submitted after the document is uploaded. The problem is that the workflow will trigger once the document is uploaded, and the metadata typically isn't available. By adding the Pause for Duration at the start of the workflow, your action to match the lookup values should start functioning consistently.

  • Thank you so much, this makes so much sense. Huge help, have an awesome week. – Timothy Ward Jun 13 '16 at 14:38

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.