Skip to main content
Solved

Counter does not start at chosen value (FME 2020.0.0.1 build 20202

  • August 17, 2020
  • 6 replies
  • 184 views

michiedem
Contributor
Forum|alt.badge.img+7

I am having a problem with the counter transformer in multiple workbenches on multiple machines: It ofthen does not start at the set value (ussually 0 or 1). For instance; The counter in the image is set to start at 0. However: When I run the workbench it starts at 577. I have no clue at al why it does that.

 

counter

 

When I use featurecaching and I run the whole workbench one by one transformer it will start at 0. But ONLY when I manually start every single transformer before the counter.

 

I have this on this machine and another computer in completely different workbenches.

 

I use the counter to merge features. the workbench stops because it can not merge features based on wrong counts.

 

 

Best answer by ebygomm

it is set to global (standard settings)

In which case you probably want it set to Local

"Specify whether the scope of this counter is Global (throughout the entire workspace) or Local (for this transformer only). Global counters with the same Counter Name will share the same counting sequence, while Local counters will each have a unique counting sequence."

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

6 replies

ebygomm
Influencer
Forum|alt.badge.img+44
  • Influencer
  • 3427 replies
  • August 17, 2020

Do you have the Count Scope set to Global or Local?


michiedem
Contributor
Forum|alt.badge.img+7
  • Author
  • Contributor
  • 52 replies
  • August 17, 2020

it is set to global (standard settings)


ebygomm
Influencer
Forum|alt.badge.img+44
  • Influencer
  • 3427 replies
  • Best Answer
  • August 17, 2020

it is set to global (standard settings)

In which case you probably want it set to Local

"Specify whether the scope of this counter is Global (throughout the entire workspace) or Local (for this transformer only). Global counters with the same Counter Name will share the same counting sequence, while Local counters will each have a unique counting sequence."


michiedem
Contributor
Forum|alt.badge.img+7
  • Author
  • Contributor
  • 52 replies
  • August 18, 2020

In which case you probably want it set to Local

"Specify whether the scope of this counter is Global (throughout the entire workspace) or Local (for this transformer only). Global counters with the same Counter Name will share the same counting sequence, while Local counters will each have a unique counting sequence."

I'll try and will let you know. Thank you!


jan-henk
Contributor
Forum|alt.badge.img+2
  • Contributor
  • 3 replies
  • May 15, 2024

Hello, I am experiencing the same problems with the counter transformer as michiedem.

The transformer is set to the default settings, but I want it to start with number 1.

However, when the workflow runs for the first time, it starts completely somewhere else.

And when I start the counter transformer myself, it does start with 1.

Does anyone have any idea? It doesn't matter whether I set the counter to local or global.

 

 


AliAtSafe
Safer
Forum|alt.badge.img+24
  • Safer
  • 164 replies
  • May 22, 2024

Hi, @jan-henk.

I tested out your scenario and found that local works on the first run after closing and re-opening the workspace. I’ll look into it and get back to you.