Issue: Receiving the subject error against the "Update Multiple Items" action in a simple workflow, but no evident way to determine specific issue with the action.
Context: List A in Site A is initiated by a Boolean field change in state, and when initiated the workflow's "Update Multiple Items" action is set to filter Site B's List B with the item title ("Accomplishment") field which is the same in both lists, and then to update the List B item's "Description" field with List A item's "Description" value. I've also tried changing from a Value assignment to a List Lookup on current item, but the same subject error is produced.
The Nintex Workflow version is 18.104.22.168.
If anyone has ideas about what might be causing the issue, and/or how to capture more granular details about the error, I'd appreciate it!
do you have sufficient permissions on target list and items to be updated?
don't you have any validations on list or list field that may reject the update?
aren't there mandatory fields on items to be updated without a value yet (eg. Title)?
Ok, so here's the answers after double checking. None of these immediately appear to be the cause, but still considering the mandatory field relationships.
Thanks again everyone,
P.S. if noteworthy, the workflow is actually the same thing that creates the item on the target list w/o error (so, I'm doubly sure list & item permissions, validation & mandatory fields aren't an issue). The flow is initiated by a boolean field on the form, and then it's a simple decision point in the flow to determine if it's been previously created or not. If new, it creates it in the target, & if it exists in the target already, it runs the "Multi Item Update" action on the existing item (and fails). That's the end of the workflow though.
can you write value of 'Accomplishment' to history log and check it really contains expected value?
make sure there are not leading or trailing spaces in the value.
how do you check whether workflow runs for new or existing item?
can not it happen workflow goes down the update branch when the item do not exist yet?
can you post configuration of 'Description' field?