@chau

You create only 1 object.

You reset the counter every iteration, of which you have one.

You have no index to increment as well.

Setting the "maximum iteration count" attribute to 3, just sets a limit to the iterations.

But you have only 1 object so you have just 1 iteration.

It's a mandotary parameter when using blocking tranformers in loops.

With some effort you can even use this parameter.

Basically it looks like a loop but it is limited to 1 run and there is no index or any other test to loop.

Try creating more then 1 object and run the script.

Have fun

Gio

Hi @gio, I get inspector data in my FFS files for three iterations. And even if I only iterated once, can we then still agree on, that I should expect output from the inspector in the custom transformer for that iteration?

@chau

Here is a sample of it working as you expected.

This is fme2018 so you need to do @Value($(ITERATION_COUNT_ATTR)) to acces it.

I think you are misunderstanding my question. The custom transformer is just a mock-up, I am talking about results from inspectors not showing up in the Data Inspector window in FME 2020.

@chau

Yes, that is what you'd expect.

OK, mock up was not represantitative. Sit will never loop more then once.

I assume, that my sample does not show it either then as i now understand it to be a 2020 issue.

2020 version. Not tried it. If it 's got issues i wont be doing that soon then.

Thats for Safe hen.

GReets

Gio

I don't think inspectors in linked custom tranformers (which it must be if it is blocking and looping) ever trigger the inspection window to open, I'm not sure if that is expected behaviour or not

yes they do (or did if you use 2020 appearently)

My example is linked and it does Inspect (2018 version).