How do i Create a Copy of Current Record after Editing to another Table (children records)
I mean a change log record everytime editting.
I create 2 tables.
*Table A:
- Property Address
- Width
- Floor
..
*Table B (same as Table A, but lookup and child record):
- Property Address (lookup to Table A - Property Address)
- Width
- Floor
..
What i want is: everytime i edit a record of Table A, it will automatically copy the current record to Table B (as a change log) - child record. So that i can see all edit history of a record from Table A.
I know i can start with : function bds_after_update
but i still have no idea. Please help.
thanks
Create a Copy of Current Record after Editing to another Table (children records) (change log)
Re: Create a Copy of Current Record after Editing to another Table (children records) (change log)
Hi,
just a quick answer.
I did something similar using the Audit Log (see my footer).
The audit log keeps track of all changes in table A - done.
If you want to see that history, I suggest:
1. create a view in your database which reads the audit log for table a (you can skip this, if you only use audit log for table a)
2. create a "fake" table in AG which has the fields (from the view/audit log) that you want to show to the user. Then show data from the audit log which matches the primary key of your item in table a.
.... well not sure, I described this correct - was a long day. Essentially: Look at the audit log
For me it looks like this:
Olaf
just a quick answer.
I did something similar using the Audit Log (see my footer).
The audit log keeps track of all changes in table A - done.
If you want to see that history, I suggest:
1. create a view in your database which reads the audit log for table a (you can skip this, if you only use audit log for table a)
2. create a "fake" table in AG which has the fields (from the view/audit log) that you want to show to the user. Then show data from the audit log which matches the primary key of your item in table a.
.... well not sure, I described this correct - was a long day. Essentially: Look at the audit log
For me it looks like this:
Olaf
Some postings I was involved, you might find useful:
SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button; Place a search on details view
SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button; Place a search on details view