Overview
Plug-in Notes:
Key Features & Functionality
The Appian Log Reader Plug-in contains functionality to:
I'm trying to read the contents of "design_errors.csv" (which appears to be a normally-formatted CSV file). I've tried readCSVLog(), readCSVLogPaging(), and readCSVLogPagingWithHeaders(); all of them fail to pull back any contents. They do receive the header column names from the CSV file, but return no rows of data. Any suggestions?
Ok great! I'll look for the update from the community
Mark Talbot - that sounds like a good feature. I won't be able to test it in our case because I had appian support archive the older design_errors.csv file in all our environments, which proved out my theory that it was breaking because the number of columns changed over time. But that means I no longer have a version to test this against. However anyone who has an instance that's been around since the '19 versions or so, should be able to reproduce the issue and test if the new functionality works.
I've added a function that reads the CSV in reverse. Please see if this works for your use case. Note that reading a CSV in reverse is less efficient if you are going to read the whole file than it would be if you read it normally. However, reading the CSV in reverse is more efficient for large files if you are only reading a few lines at a time.
That is my end goal, yes.
Sam Zacks - do you mean a fix to the plug-in? That seems like it would be useful, since otherwise any future alterations to the columns of a log file will seemingly have the same "breaking" effect.
You're correct about this - I understand the issue is when there are inconsistent column sets. I'm continuing to investigate changes and trying to reproduce so that I can prove out a fix.
phorning - I had Appian Support deprecate the existing design_errors.csv files across all my environments, such that a new file has been created as of a few days ago, so that there is now a consistent number of columns across all rows. Per my expectation, the log reader query now works fine.
Sam Zacks - for further clarification: I've had Appian Support deprecate the existing design_errors.csv in all my environments so that they can start over with consistent columns in all rows, and the log reader query now works fine, as I'd expected.
Sam Zacks - also, I wasn't notified of your reply until just now when someone clicked "like" on my top comment. I suggest when replying to these you directly tag people and/or click "like" on the comment you're replying to. It seems to me that Community settings should be refined such that people are notified of replies here.
Sam Zacks - your design_errors.csv file would (i presume) need to have some rows in it with the older version of the column set. What do you see when you look?