We have been actively using the Shopify Connector for BC 365 SaaS for about a year now. Originally our Shopify shops were configured in BC for logging all transactions. That was cut back to only logging errors awhile back, but still the log entry table is huge. 2.35MM rows and consuming like 18 GB of storage.
Attempting to delete log entries through the Shopify Log Entries list page, the operation times out and returns failure. I'd assume this is due to the inherent SQL Server 300-second command timeout that's usually baked into things. My next thought was to create a configuration package, with only the Shpfy Log Entry table 30115 listed. I could check the option to delete the table contents before importing. And I'd have an Excel import file with just a single dummy row, incrementing the Entry No. value by one more than the previous highest number.
My question is, does the configuration package line option for deleting all table contents perform a back-end SQL Server procedure call, similar to BC 27's Truncate() AL command? Or is this just another front-end client call, like the delete actions in the Shopify Log Entries list page?
When I was poking around in AL trying to come up with something, I recall seeing a warning about access restrictions to the Shpfy Log Entry table 30115. So not sure if looking to implement the Truncate() method in AL code would be the way to go really...
530
Share
Report
All responses (
Answers (
