Hi Mihaela,
Thank you again for your reply!
1. Sorry for the confusion. The "Frontend edit via Breezing Form", actually means a menu item of the CB "List View" type, which selected the view I created for editing (which was already working in the backend):
mrkr.io/s/5c4f67cbef645932207deb27/0
The view was set to "checked" for the "edit by type", and that view was for Breezing form, so if a login user clicked this menu item link, he/she will first see a list of all the records he/she created (which is great! we need this!), then he/she can click one of these record to start editing.
If a super user login at the backend, then the record can be edited (including the separate data table's values);
If the author of that record login at the frontend (i.e. you can find frontend login information at the end of this post), only values stored in Breezing form records was edited, and we will see a 404 page after the form was submitted. You can tried it with this link after you login:
This message contains confidential information
Because each user might have multiple records, "Submission editable by user checked" probably won't work as it can let the user to edit his/her very last record only.
2. Understood! We will figure out a way to remove the record then. Unless there is a "delete" rule for integrator... or breezing form.
The reason why the record was still displayed at the frontend, is because that our frontend listing page:
This message contains confidential information
was a customized page that will draw records from the separate data table. Therefore it will keep displaying the record removed from CB view, but remained in the separate data table.
If you need to test #1 above, you can try with the listing page too (so that you can "see" what value was saved to the separate data table);
Thank you very much! Login information pasted below:
This message contains confidential information