Here's another vote. This has been top complaint about WA in general. Yes, it is important to to be able to determine who deleted a contact or registration, but on a more abstract level, each and every change (insert, update, delete) that leads to the "current" set of information should be available to allow a complete transactional history of contacts, members, event sign ups, payments, ...
Here is an example of what I should be able to extract from the database:
List in chronological order all transactions for member x to include date their membership record was created, changes to membership status, membership invoices created, membership payment entered, .....
I've been involved with the development of online database systems for many years. All systems that I am familiar with fall into one of three categories:
1. System builds a transaction from user input and then applies it to the "current" records and keeps the transactions around as a complete history of how the "current" record got to its current state.
2. System uses user input to update the "current" record without first building transactions. The only history are any fields that on the "current" records such as "member record creation date". This is typically done by people who have no database experience and do things buy a copy of Microsoft Access and create a Members table to track their members.
3. System uses user input to update the "current" record as in number 2 above and also writes some basic information to a log file which is better that number 2 but not a robust as number 1.
So, I would like to know which of these WA is doing and hopefully if it's number one or number 3 I'd like an explanation why you won't make it available. Do you not have the transactional data to share, do you think your customers are not smart enough to use the data, are you afraid you competitors will somehow use this to your disadvantage, do you not have enough staff to implement?
Based on the thread, it appears that people have been asking for some time for this ability. Have you taken any action to "test the waters" or are you just relying on the number of people that post here?
MikeW
Here's another vote. This has been top complaint about WA in general. Yes, it is important to to be able to determine who deleted a contact or registration, but on a more abstract level, each and every change (insert, update, delete) that leads to the "current" set of information should be available to allow a complete transactional history of contacts, members, event sign ups, payments, ...
Here is an example of what I should be able to extract from the database:
List in chronological order all transactions for member x to include date their membership record was created, changes to membership status, membership invoices created, membership payment entered, .....
I've been involved with the development of online database systems for many years. All systems that I am familiar with fall into one of three categories:
1. System builds a transaction from user input and then applies it to the "current" records and keeps the transactions around as a complete history of how the "current" record got to its current state.
2. System uses user input to update the "current" record without first building transactions. The only history are any fields that on the "current" records such as "member record creation date". This is typically done by people who have no database experience and do things buy a copy of Microsoft Access and create a Members table to track their members.
3. System uses user input to update the "current" record as in number 2 above and also writes some basic information to a log file which is better that number 2 but not a robust as number 1.
So, I would like to know which of these WA is doing and hopefully if it's number one or number 3 I'd like an explanation why you won't make it available. Do you not have the transactional data to share, do you think your customers are not smart enough to use the data, are you afraid you competitors will somehow use this to your disadvantage, do you not have enough staff to implement?
Based on the thread, it appears that people have been asking for some time for this ability. Have you taken any action to "test the waters" or are you just relying on the number of people that post here?