Bug - CSD task - saving prompt to affect CO record

[AntWeb-org]

Steps to reproduce the bug

1.In the CSD task
2.Made update/added data to Attributes/Custom Attributes field and pressed Save
3.Prompt suggesting that the collecting event was modified and will affect all CO records associated with that CE.
4.Went to Edit collecting event for good measure and did not make any changes
5.Pressed Save although no updates/changes were made
6.Another prompt suggesting changes to CE will affect associated COs.
...

Screenshot

Prompt in CSD record/no updates made to CE record:

Prompt in CE records/no updates made to CE record:

Expected behavior

It seems that there is an issue with one specific (as far as I know) CO and associated CE (CASENT0042899/BLF09800). I tested and saved other records and did not experience that issues.

I did not make any updates to that CE record and cancelled the updates to the CO record. I am wary of that prompt and do not know if anything will affect the CO records for that CE.

Additional Screenshots

No response

Environment

Production

Sandbox Used

No response

Version

v0.37.1

Browser Used

Chrome Version 120.0.6099.131

[AntWeb-org]

Update: happening in other CO records in the CSD when I attempt to add data into a Custom Attribute field.

[tmcelrath]

This is also happening when you try to create a brand new collecting event from comprehensive. Instead of creating a new one it is editing the old one. NEEDS A HOT FIX ASAP.

[tmcelrath]

Weirdly - even though you are prompted that it will "edit >100 records" it does not actually do so.

[tmcelrath]

Upon refresh, the CE is created as normal, even though client-side, pre-refresh, it looks like it you are editing a CE with >100 records.

[AntWeb-org]

So can I click Edit and hope for the best or should I hold off until the issue is fully resolved? I'm still a little hesitant.

[tmcelrath]

At least from my end everything has all been client-side visual and is not actually making changes to the CE with >100 records unless you are actually doing so. It's very confusing and @jlpereira has said he will try to fix it today.

[AntWeb-org]

That's great! Thank you!

[jlpereira]

@AntWeb-org where do you add the custom attributes? To the collection object or to the collecting event?

[AntWeb-org]

I was adding to the CO in the CSD, specifically for CASENT0042899 under Attributes.
Thanks!

[jlpereira]

Were you editing other collection objects without leaving the interface? Does this happen if it is the first collection object you load when you open the interface?

[AntWeb-org]

Someone else was making an update to that specific specimen initially. I checked to see if it was done. When I realized it was not done I made the update and then received the Edit message. I was not happening previously for other COs I updated and I do not think I was updating in separate tabs. It was not happening on the first CO.

[tmcelrath]

For me - it gives me the warning if I go to any CO that has a CE with >100 records. If I edit anything on the record (even if not in CE), then I get warning.

[tmcelrath]

Secondarily - if I remove the CE with >100 objects, and create a new one - it tells me that I am editing the CE with >100 COs. If I save, it even looks like the CE has been edited. If I refresh the page however, that disappears.

[AntWeb-org]

I guess I was editing COs with CEs that have fewer than 100 COs associated. Weird.

[jlpereira]

I think I found the problem and already solved it, in a moment I will be pushing it.

[AntWeb-org]

Thank you!

[mjy]

Can someone confirm if this is visual, of if it could really affect the data because of editing a record you didn't think you should be editing?

[tmcelrath]

Visual.

[tmcelrath]

Extremely confusing, but visual.

[mjy]

Heard. I panicked big time on somethign like this the other day too...

[AntWeb-org]

Unfortunately, the problem has returned even before I add any collecting event to a new CSD that I am entering. Notice the Attributes as still locked. It began happening steadily at this point on my fifth or sixth entry.

[jlpereira]

@AntWeb-org this fix is not yet in production

[AntWeb-org]

Got it, thanks