Can you please explain what was changed in 8.2.8 with the CountOccurencies function? I have been running this fine in the previous versions and now I am getting very strange results in the set variable commands using the following command for example:
{STRING(CountOccurencies|{TASK(8a980837-2c29-442d-9b82-3c4898d56f63,StdOut)}|060CHK)} used to sample values:
1 file result was previous: 0 and now: 213. (0 was correct)
a different file result was previous: 0 and now: 4043 (0 was correct)
the same file (different search string) result was previous: 21 and now: 4043 (21 was correct)
I have confirmed the StdOut of the TASK called by straight OUTPUT and now it appears it has something with the search string length and length of files?
Any help would be appreciated as I am not finding a true pattern here.
Thanks,
Curtis
Edited by moderator
2017-09-12T14:55:38Z
|
Reason: Not specified