Hi,
This is mainly for the Appian team.
I just noticed there is a bug in this plug-in. The moment it comes across a blank row, it treats it as the end of file.
For eg, if rows 1-100 have data in any of the columns and row 101 is completely blank and 102-1000 rows have data in any column again, it only processes data from 1-100 and ignores the data in 102-1000.
This seems to be a bug because previous versions would read from rows 1 to 1000.
What can be done to resolve this?
Discussion posts and replies are publicly visible
PEBKAC (Problem Exists Between Keyboard And Chair) ;-)
it returned totalCount as 65 even though the file has 10001 rows (66th row blank) even after giving stopReadingAtFirstBlankRow as 0 (it doesn't accept false or true as input but wants integer format even though the documentation help says boolean)
What value should we give to not stop at blank row?
I am not sure that this plugin supports keyword syntax. I suggest to provide all parameters in the exact order.
Alright, that worked. Thanks
Unknown said:I am not sure that this plugin supports keyword syntax.
As an aside, could this like.. start being a requirement for new or updated plug-in expression functions, perhaps? It would be one thing if they NEVER took keyword syntax and we could assume it NEVER works, but at the moment it's an uneven mixture and there's no way of telling other than by trying and failing.
Keywords must be passed to plugins by position, right?
docs.appian.com/.../passing-arguments.html
Very true, I would say this plug-in is a bit dodgy.
<smartass-mode>To not confuse anyone, it is the arguments, not the keywords, that must be passed by position.</smartass-mode>
Steven Miccile said:Keywords must be passed to plugins by position, right?
Off the top of my head, but without checking, I was sure there are some plugin expression functions that accept full/normal keyword syntax, whereas some ignore it (or break if you try to use it for partial passing). I'm open to being corrected, of course.