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
{{ message }}
This repository has been archived by the owner on Nov 25, 2022. It is now read-only.
To isolate this behaviour (in case users want to keep the existing behavior), a checkbox "Allow Update and Delete" is added to the upload screen.
If the checkbox is selected then:
For each record, a check is made whether it exists (based on id) and if so it is updated rather than created
If the record has an attribute operation_delete then the record is delete (based on id). Records with this attribute still need to be valid records, because they are validated as part of the field mapping (I use this for bulk deleting, although the way it is done is not ideal).
Some of this design could possibly be improved, but am keen to get feedback on it and to get your thoughts on whether you see benefit in merging this into your repo?
The text was updated successfully, but these errors were encountered:
I have created a fork with the ability to update and delete records.
https://github.com/ztech-company/strapi-plugin-import-export-content/tree/update-delete
To isolate this behaviour (in case users want to keep the existing behavior), a checkbox "Allow Update and Delete" is added to the upload screen.
If the checkbox is selected then:
operation_delete
then the record is delete (based on id). Records with this attribute still need to be valid records, because they are validated as part of the field mapping (I use this for bulk deleting, although the way it is done is not ideal).Some of this design could possibly be improved, but am keen to get feedback on it and to get your thoughts on whether you see benefit in merging this into your repo?
The text was updated successfully, but these errors were encountered: