Today, I was trying to update a list item with some data using the Update listitem action in Nintex and I got
Coercion failed: Unable to transform the input lookup into the requested type
The string value that I had was “Other;” and I tried to update a lookup field with this string. Once I removed the semicolon the problem went away
The annoying pain in this case was that the workflow even though it had started there was no ‘In progress’ or ‘Failed’ link to the workflow history.
Also, during my debugging I disabled the update item action, but the disabled action still caused the workflow to fail in the same way.
Discover more from SharePains
Subscribe to get the latest posts sent to your email.
Pieter Veenstra
Is your business still running on paper trails, sprawling Excel files, or ageing Access databases? There's a better way — and I can show you exactly what it looks like. I'm the Technical Director of Vantage 365, a Microsoft solutions consultancy working with clients across the UK, the Netherlands, and worldwide. For over 30 years I've been turning messy, manual business processes into clean, automated systems that save time, reduce errors, and give teams the visibility they need to make better decisions. SharePains is not just any blog run by a Microsoft MVP. Have you ever used Try-Catch in Power Automate? The original post about Try-Catch in Power Automate can still be found on this site, https://sharepains.com/2018/02/07/try-catch-finally-in-power-automate-flow/ Or have you ever used the Pieter’s method to avoid variables and speed up your flows? https://sharepains.com/2020/03/11/pieters-method-for-advanced-in-flows/ You can contact me using contact@sharepains.com
did you ever resolve the issue? if so, what did you do?
I think the problem was related to a ; in the text used to update a field. Can you give me more details on how you are getting this error?