I have an append-only comments column on a form. A workflow kicks in when anything is modified on the form. This workflow appends the latest comment again to the chain of comments.
This is what the comments section looks like.
Has anyone had to deal with this before?
Solved! Go to Solution.
I apologize for my confusion, but it sounds like the workflow is doing what is expected by appending again what the form will already do on its own.
What is the intention of the workflow other than updating comments? If you remove the part in the workflow that updates the comments the form should automatically do the append.
The workflow is does not have the part that updates the comments but still the comments are getting appended when the workflow runs.
Anyway, I have a work around now. Instead of append column I added a regular column and created a workflow that updates the comments.
Hi all. Not sure if this is still an issue with recent versions of Nintex forms (we haven't upgraded for a while), but I solved this by making sure whenever my workflow updates an item, I also get it to update the appending comments field with blank data. Somehow it doesn't actually update the comments at all no matter how many times the other fields are updated.
So after many item updates, my comments still look like they should.
Hope this helps.
The cause of this is the type of multi-line of text field you are using. When using rich or enhanced text, this issue will occur. I believe it has something to do with an empty html element being created for the empty field, making it ready for you to insert text (so in fact it really is not empty), and Nintex then believes an update has occurred. If you change the field to plaintext then the issue will go away.
A quick warning though, changing field type like this will result in all previous data being lost, so this will not work if you are looking to keep the existing content stored in these fields as rich / enhanced text.