Hello,
I have a Cloud customer with a strange issue. It doesn't happen often, but the fields involved get exported to another software system, so when it does occur, it's easily noticed and has to be fixed.
The multi-value field group in question has 3 fields. The first 2 fields are dynamic fields, with the 2nd field being dependent on the 1st field. Sometimes, we end up with a duplicate field group in the last position. I know the user isn't doing this intentionally. Audit Trail says it's the user's account making this change, so it's not something in Workflow doing it. I haven't been able to replicate it myself, nor could Support. It seems to be happening more often than it used to. Is there some keyboard shortcut that could be causing this? I believe the users in question here use the tab button on their keyboards to move between fields - is there some combination of keystrokes that could cause this when moving between fields/field groups? I'm at a loss for how to troubleshoot this at this point. This is in the Windows client.
Alternatively, I could try building something into the workflow that exports the document data to the other software system. My thought was it could get the number of items in the multi-value token, then create a new token that uses the Remove Duplicates function, and then get the number of items in the multi-value token with duplicates removed. If the counts differ, that indicates there was a duplicate, which I can assume is in the last position of the multi-value field. But how I get rid of just the group in the last position is something I haven't figured out yet.
Any help is appreciated. Thanks!
Question
Question
Cloud - Multi-value field group periodically contains duplicate groups
Replies
Well I somehow never thought to apply the Remove Duplicates function to the token that gets put in the Run Script Rule activity, but that solves the issue of duplicate data getting sent to the other software.
Still have the duplicate field group in Laserfiche, but I can use the Count function on the original token, then use the Remove Duplicates function on it, and then count that resulting token, and know that I have a duplicate value if the counts differ. Currently putting a tag on those documents so I can find them later if I come up with a solution eventually.
Thanks for reporting this, we'll look into it. It sounds like you have a pretty standard process, so I take it the user is at least intending to perform the same action on each of these documents. From the audit logs, do the times when the multiple values are saved appear any different from the correct functioning? For instance, does it look like there is a second update?
If you do discover anything that makes it more likely to reproduce the problem, please let us know as that is always very helpful when troubleshooting.
It seems pretty consistent that the user will input data to the majority of template fields, including this field group, and there is no duplicate at this time. Later, they'll go back and update a couple more fields, and this is when the duplicate field group appears.