You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the Bug
when attaching multiple new records to an existing BCMI collection, a range of undesired behaviours can occure including (collection not being updated, collection would be completely emptied and all records would be removed, most common: it would remove all existing records and only add the new records)
Expected Behaviour
it should create an update and add the records to the collection alongside the existing records
Actual Behaviour
described above, doesn't delete underlying records but does leave them in a broken state where the records believe they are still apart of a collection, but the collection is empty and the records cannot be added back using the UI, needed Dev to go into DB to fix.
Implications
users give up on updating BCMI Collection, causes user to abandon application, very poor user exp.
** Steps To Reproduce**
Steps to reproduce the behaviour:
Go to NRPTI, All Mines Section,
Click on a mine
go to an existing section under a mine.
click on create or add a new record to an existing collection
add multiple records and click update
See error
Additional Context
Could be programmed in a way where it deletes everything in the collection and then rewrites it every time
there is no UI to inform the user that an error occured
this isn't an uncommon upload path for getting records into NRPTI
this error is only with BCMI
most collections only get created with one record and its not a problem, only when its multiple records does the issue begin happening.
The text was updated successfully, but these errors were encountered:
Describe the Bug
when attaching multiple new records to an existing BCMI collection, a range of undesired behaviours can occure including (collection not being updated, collection would be completely emptied and all records would be removed, most common: it would remove all existing records and only add the new records)
Expected Behaviour
it should create an update and add the records to the collection alongside the existing records
Actual Behaviour
described above, doesn't delete underlying records but does leave them in a broken state where the records believe they are still apart of a collection, but the collection is empty and the records cannot be added back using the UI, needed Dev to go into DB to fix.
Implications
users give up on updating BCMI Collection, causes user to abandon application, very poor user exp.
** Steps To Reproduce**
Steps to reproduce the behaviour:
Additional Context
The text was updated successfully, but these errors were encountered: