Try this answer here.
https://community.quickbase.com/discussions/quickbase-discussions/best-solution-to-create-auditchange-logs/17909
I recently converted my field audit process over to this solution and I like it a lot better. It still gets a little bulky with a lot of fields, I actually had to create a part 2 because I hit the 26 step limit. I don't know if MarkShnier__You reads these replys...any thoughts on how to simplify the pipeline if you want to track all fields, or what about a checkbox for fields that you want included? A way to identify fields and have them added to the pipeline without having to add them all manually a step at a time?? Just an idea but the solution is easy to implement and gives a very readable report within your tables.
Qrew LegendYes, this solution is in the category of stupid simple to implement, but it is tedious if you have a lot of fields to track. If you want to continue to use the solution, then you would have to make another pipeline and continue on with more fields.
HoweverYes, this solution is in the category of stupid simple to implement, but it is tedious if you have a lot of fields to track. If you want to continue to use the solution, then you would have to make another pipeline and continue on with more fields.
However, if you were interested in a Solution which was a little bit more technical than there is another method which I have implemented using web hooks but never implemented myself using a pipeline so I don't have any code to that I already have. But if you're interested in pursuing that and you contact me directly at the email address mark.shnier@gmail.com then I don't mind working together with you to document a solution which can track unlimited number of fields and we will circle back in a week or two and post the solution.
Qrew LegendI was unable to get a Pipeline to do a multi record operation using the API_ImportFromCSV api. I will need to chdck with Support to see of it's supported yet in Pipelines.
I was able to get the Webhook working though.
The endpoint is the url to the Audit trail table.
https://mycompany.quickbase.com/db/xxxxxxxxx
The Header is QUICKBASE-ACTION is the Key and API_ImportFromCSV in the value.
<qdbapi>
<usertoken>xxxxxxxxxxx</usertoken>
<records_csv>
<![CDATA[
%RepeatOn%
"Reviews", "Review Date", "[old.Review Date]", "[Review Date]","[email of last modified by]", "[Record ID#]"
"Reviews", "Reviewed By", "[old.Reviewed by]", "[Reviewed by]","[email of last modified by]", "[Record ID#]"
%RepeatOff%
]]>
</records_csv>
<clist>9.10.11.12.13.14</clist>
</qdbapi>
In the example above, my target Field's IDs are 9, 10, 11, 12, 13 and 14. But they need to be entered in period delimited format as the clist. Those fields respectively are the table name, then the field name, than the old value than the new value, and then the Record ID#] of the changed record. By having that record ID you can make a report link field on the parent record have it filtered only for audit log records of the correct table which would be hard coded by a filter on the report and then the report link field would only include audit records for the parent. By anyone viewing the parent record would immediately have the audit trail. The report would also be filtered to exclude where the old value in the new value were the same and you would have a nightly process to purge are the Trail records where the old value in the new value is the same.
The purge can be done very efficiently using the API_PurgeRecords API call.
