Could you share a screenshot of your workspace so we have a better idea of what you're trying to do?

Hi @redgeographics below is a screenshot.

Counter_4 is the one that outputs the strange values. Counter_3 works as normal.

I can't seem to reproduce this, I've attached my little testcase if anybody else wants to take a stab at this (or if you want to send it in to Safe's support).

If you could try running that test workspace and see if you get the correct results that could actually be quite useful (it may be an issue with your source data)

Counter_issue.fmw

Thanks for looking at this @redgeographics. I ran that workflow you sent through and it worked fine for me. But when I copied the transformers into my existing workflow and connected it up , I got the same issue. I have now found a work-around which means I don't have to use the Counter anymore...

Hi,

What was your solution @aquamarine ?

Thanks in advance

Hi,

 

I'm having almost the same issue. When counting the result from sql executor it returns whats seen in the inspector, but counter works fine for the initiator.

What was your solution @aquamarine ?

Thanks in advance

 

I wonder if this is related to the bulk mode issue that was affecting the statistics calculator

https://knowledge.safe.com/questions/102959/incorrect-results-from-statisticscalculators-cumul.html

If you put a python caller in front of it (doing nothing) does it fix it?

Hi,

 

I'm having almost the same issue. When counting the result from sql executor it returns whats seen in the inspector, but counter works fine for the initiator.

What was your solution @aquamarine ?

Thanks in advance

 

Hi @jonathanklarup Try a PythonCaller as @ebygomm suggested, or an Offsetter, or an AttributeKeeper - all of these are transformers which will split up the feature tables. See the explanation here: https://knowledge.safe.com/questions/105599/why-is-my-counter-transformer-giving-me-a-weird-va.html

worked like a charm, thank you @danatsafe