Sounds right to me. I wonder if they have a concern that the column name used for the BigQuery row key might conflict with names of app columns. They’ll be introducing a new column name, and need to avoid conflicts. I can imagine other edge-case concerns, too.
Hello all,
I just read that they are discussing the details of how to safely incorporate the missing data into the BigQuery schema.
I am assuming they received your suggestion but just in case I will add it to the ticket as well.
@Jose_Arteaga Hope you are keeping well with all the movement on forums.
May I ask why the team has failed to update me on mail or keep me in loop with proceedings, the Export to Big Query was a feature my client needed and therefore opted for Enterprise License. I do beleive they should be fixing this urgently as it is an advertised feature for Enterprise. Please ask them to provide an ETA for fix via email.
Of course! I am contacting the support team asking for an update.
@Jose_Arteaga , what’s word on this?
@Steve Latest update last night.
Hello @Denzil_Snyman, I completely understand your frustration regarding this delay. I have reached out to our engineering team to expedite the analysis process and ensure this is addressed as quickly as possible. I truly appreciate your patience and will be sure to keep you updated as I receive more information.
@Shourya_Tomar, is there any hope this issue might be addressed?
Hello @Steve, I wish I had any updates to share with you. I will follow up with the team and keep you posted!
Any new here, @Shourya_Tomar?
Hello @Steve, I have requested an update from our engineering team regarding this matter. I will provide an update here the moment further information is received.
Anything, @Shourya_Tomar ?
@Jose_Arteaga How do I explain this to my clients whom heavily weighed in the choice of Enterprise for the Big Query Audit Log. So that they could log the Audit Trail in this manner…
Nothing was done since day 1 of reporting it and it is advertised, it did not advertise as Performance Log being streamed to Big Query but a way to long term store the Audit History function that appsheet has, therefore a core unfinished thing that was overlooked, not a longstanding behaviour.
Hello @Denzil_Snyman,
Thanks for bringing this up. I will also investigate and come back to you today.
Thank you. I did reply to them via email however pushing this into the bracket of longstanding behaviour is a cheap way to deprioritize this ticket.
The truth is that it that the feature is supposed to provide the teams Audit History as advertised to be streamed into Big Query for long term storage and it clearly doesn’t include the required details.
In the Audit history on appsheet I can see the Values of each field for an Add row or an Edit row. This is completely missing on the big query stream as well as who the Useremail() is performing an action on the system. It only provides the UserID in the big query stream.
Here below are the values shown in Appsheet Audit History linked to an action. Surely finding a way to group this info into a JSON structure of “Column” : “Value” pairs and then adding it to the existing Detail Column coming into Big Query is possible.
Hello @Denzil_Snyman,
First and foremost, I want to sincerely apologize once again for the ongoing stress and frustration this situation has caused. We truly appreciate your incredible patience and willingness to stick with us while we work through this complex issue.
I insisted that we need to provide a transparent update on where things stand: our team is currently finalizing the necessary structural changes to address this. Our current target is to have the fix ready for deployment as early as next week. While deployment timelines can occasionally shift slightly during final testing, please rest assured that this is a priority for us and we are actively driving it toward the finish line.
Thank you again for holding us to a high standard, and I will monitor this closely to update you the moment it goes live.
Thank you for the positive update, may I ask the difference between your response and the support teams response, in terms of how they are on opposite spectrums. How did the teams response via email end up so opposite to yours..
Support works in templates, recipes, and boilerplates to approximate support. @Jose_Arteaga actually provides support.
Hello @Denzil_Snyman and @Steve, thank you so much for showing so much patience while the team was working on a fix. I want to update that the team has come out with a fix and it will likely go out today so it would be great if you,@Denzil_Snyman can try it out and provide some feedback or let us know if you face any issues with it.
Thanks, I hope it helps!
Thank you for the update, would you be able to ask team to share where exactly and what changes or fixes were implemented.
Do we need to do anything on our end, are we still expecting the same Big Query columns?
With regards to the missing Audit History mentioned, what new data is being streamed and where do we expect to find it, will the new data be shown in the “Details” JSON column and will it be only values or column:value pairs?
Will we be expecting to see any details of User Email making the changes with the UserID in the same column?
Can we identify the Key Value of the row that changes took place on?