Skip to main content
Solved

Counter generating corrupt values

  • September 21, 2020
  • 5 replies
  • 39 views

Forum|alt.badge.img+1

Hello,

 

I have an FME Desktop workflow within which I have a Counter that is set to start at 700,000, but the final three entries are not rendering with a correct value as per the attached screenshot.

 

The Counter scope is local and I do have a second Counter within this workflow that works fine, although I was having this prior to introducing the second Counter (this has a different transformer name, is also local and starts from 1).

 

I have run this workflow a few times now with Feature Caching On and Off, plus have closed all other FME sessions, but am still getting the issue.

 

Has anyone experienced this before?

 

Thanks,

 

RB

Best answer by ebygomm

Can you try inserting a python caller (doing nothing) before your Counter, it might be a feature table issue. Inserting the python caller will break the feature tables

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.

5 replies

ebygomm
Influencer
Forum|alt.badge.img+46
  • Influencer
  • Best Answer
  • September 21, 2020

Can you try inserting a python caller (doing nothing) before your Counter, it might be a feature table issue. Inserting the python caller will break the feature tables


Forum|alt.badge.img+1
  • Author
  • September 21, 2020

Can you try inserting a python caller (doing nothing) before your Counter, it might be a feature table issue. Inserting the python caller will break the feature tables

Thanks @ebygomm​ that has solved the issue


mark2atsafe
Safer
Forum|alt.badge.img+59
  • Safer
  • September 22, 2020

What version of FME are you using? This issue is reported fixed in 2019.2.3 and 2020.0 (FMEENGINE-61413), so if you are getting the problem in a newer build I'd like to let the developers know.


Forum|alt.badge.img+1
  • Author
  • September 22, 2020

What version of FME are you using? This issue is reported fixed in 2019.2.3 and 2020.0 (FMEENGINE-61413), so if you are getting the problem in a newer build I'd like to let the developers know.

I'm using 2019.2.0.0 so panic over :0


mark2atsafe
Safer
Forum|alt.badge.img+59
  • Safer
  • September 22, 2020

I'm using 2019.2.0.0 so panic over :0

Excellent. Thanks for letting me know.