Document and warn of "inability to edit in multiple tabs at once"

[joegl]

Due to [CRM-12989] and other issues, there is still an issue with data integrity and editing records in multiple tabs at the same time. Saving one record might pull data from another open tab instead, overwriting what should be there.

I believe we should warn users of this behavior as it has caused endless headaches for a client of ours, but I do not have a good proposition as to where to add it. Suggestions appreciated.

JIRA: https://issues.civicrm.org/jira/browse/CRM-12989?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel&focusedCommentId=118300#comment-118300

[joannechester]

I am not sure how wide spread this issue is, but I think the warning should be inserted wherever reference is made to editing records.

One place would be https://docs.civicrm.org/user/en/latest/membership/finding-and-viewing-memberships/.

If records can be corrupted if you have two records open for when making additional payments for events then the warning should also go on https://docs.civicrm.org/user/en/latest/events/manual-event-registration/ perhaps just above "To make an additional payment on this registration:"

It also maybe appropriate to add the warning somewhere on https://docs.civicrm.org/user/en/latest/organising-your-data/contacts/ and there could be other places also.

However, no matter how many places you put the warning in the documentation, there will be people who edit records without reading the documentation.

[michaelmcandrew]

excuse the repition from https://issues.civicrm.org/jira/browse/CRM-12989 but wanted to add it here for convenience...

As a general rule it is much better to fix bugs in the system rather than document them.

I totally understand the motivation for documenting it since it has been in the system for a while but if at all possible it would be better to try and fix this bug than document it.

I can't imagine it is impossible to fix - just a part of the system that has been neglected.

It would be sad if by virtue of getting documented, people accepted the behaviour and stopped thinking about fixing it / that it was possible to fix.

If you do end up documenting it, would be good to keep the above in mind when doing so.

[joannechester]

Agree wholeheartedly with Michael that it is better to fix the problem rather than document it. I just wasn't prepared to say so as I can't fix it or pay for someone else to fix it.

[joegl]

I also completely agree.

However, this issue has existed for 6+ years in various forms. I personally have had clients lose valuable data unknowingly, costing them money. As a system keeping track of financial data for thousands of contacts, contributions, events, etc., not having this documented will cost people money. It did for us.

[michaelmcandrew]

ok - I'm not suggesting that you don't document it - just that you keep the above in mind if you do.

[github-actions]

This issue has had no activity in 60 days and has been marked as stale, it will be closed in 10 days.