Validation Error Message Pops Up

[miplatt]

Now whenever we edit details of an existing "entity" (table of companies, orgs, etc.) or "contact (table of individuals) and click on the disk/save icon, a validation error message pops up reporting conflicts with newer changes by system.

This is not supposed to happen. All we want to do is edit the data and save--there are no conflicts in these cases.

Suggestions for how to alleviate this?

[ZevToledano]

The only time this should appear is when a user and an automation rule both changed the same field(s). For example, the user saves the record, an automation kicks in to change field 'A' while the user is also changing it right after he saved.

If this is the case (or something similar) then the conflict window will popup every time by design.

Another common example is if a user keeps the record open and edited for a long time while other users and automations are changing it as well.

The conflict management window should show you exactly where the conflict is to help you figure out what is happening.

[miplatt]

I think I understand but have not located anything that appears to be causing this.

1) I have gone through all of the automations and do not see any that could kick in in these circumstances.

2) These records are not being kept open while other users and automations are changing it.

This only started happening after January 4 when we upgraded to Clay version 9.0.0a83.

Any other ideas? What else can I look for?

[ZevToledano]

Well, like I said, the conflict window should tell you which fields are in conflict. Then you can search for automations that change this field using filters in the Automation window.

If it is listing an unexpected field, let me know.

[miplatt]

The conflict resolution window lists the right field(s). The window pops us when I change any of the fields.

I searched for automations using the filters in the Automation window and still have not found any automations that impact all of these fields and can explain this behavior.

Perhaps I am missing something. Any other avenues to explore?

[ZevToledano]

I just remembered that you use HTML tabs, but this still didn't help me reproduce the problem.

I need a detailed step by step description on how to reproduce the problem starting from when you open the form, everything you click on, until the validation error.

Also please include which exact fields are being changed and which fields are being reported as conflicting, and what type of fields they are (text/numeric/date/etc).

[miplatt]

Here is a start and I will think about what I can add to the explanation.

This problem is not limited to the HTML tabs. It also occurs when we edit details in regular clay tabs.

This problem also seems to be inconsistent: it usually happens when editing an existing entity or contact but has also happened when editing a new entity or contact just inputted.

It is not limited to a type of field. As far as I can tell, it happens in text, numeric, date, notes, checkbox and email fields.

Here are some step-by-step examples of how we experience the problem:

Open entity’s record.
Click into the telephone (or any other) field and alter/enter the number.
Click on the save/disk icon OR on OK.
The conflict validation window pops up indicating that the telephone (or whatever other) field has been changed. Under new is what we changed, under existing is how the information was prior to the change.


Open contact’s record.
Click into the VOIP (or any other) field and alter/enter the information.
Click on the save/disk icon OR on OK.
The conflict validation window pops up.
The conflict validation window pops up indicating that the VOIP (or whatever other) field has been changed. Under new is what we changed, under existing is how the information was prior to the change.

[ZevToledano]

Thanks for the details. I managed to track it down to a combination of factors involving user-generated automation events. There will be a fixed release tonight.

[miplatt]

Great, thank you very much. We appreciate your efforts.

We will plan to install it this coming week.