PI Importer Max Count lowered?

[#1]

Hey,

I just noticed that with the "newer" PI importer it's possible to pass a list with AF paths instead of just one AF path. 

But here's the problem: Why does the max count gets decreased with every PI tag more in the AF path list? Before with only a single PI tag I could get up to 1.000.000 rows but with every PI tag my old max count gets divided by the amount of PI tags. This is very sad, due to the need of the filter function inside of the PI importer. Is there a workaround?

[#2]

Where did you get the 1 million rows reference from?  I am coming up against this same issue. 

If I try to pull 8 tags, I got an error that I've exceeded the maximum count of 18750.

If I try to pull 9 tags, I got an error that I've exceeded the maximum count of 16666.

Multiplying tags * these errors, it looks like my max is 150,000?  

Changing the "Max Count" doesn't seem to impact this.  The only way around the error seems to be to reduce the number of tags.

I can't find any reference in the documentation on what the max count is.

[#3]

I raised the "max count" value when pulling for 1 single tag and I got an error when I went over 150,000.  When I drop the Max Count to 150,000, it will run.  I don't understand why this wouldn't be documented for this function.

The work-around I've found is to pull each individual tag and then concenate the tables.  The Timestamps will all go into the same column and the other columns stay separate.  Then you can sort by the Time Stamp column.