Skip to main content
Solved

Same rows of data aren’t being saved to both writers

  • February 10, 2025
  • 1 reply
  • 21 views

hazira
Participant
Forum|alt.badge.img+2

Hello, I’m new to FME and I’m encountering a problem where the same rows of data aren’t being saved to both writers. I have two writers connected to the same database but with different tables. When the data is processed, the one saved in the shp_db_b table and can be seen, but there’s no output for the dashboard table (Even though it said ‘Translation was SUCCESSFUL’). I think the issue might be with the Aggregator transformer, but I'm not completely sure. I've attached the relevant pictures for reference. 

 

Best answer by redgeographics

Do you have the geometry type set in the dashboards feature type? Many databases require that and if you supply geometry of a different type it'll reject the feature (you may see a warning in the log about that)

Mismatching attribute types can also be a reason, I've had a PostGIS writer dropping features because one attribute was a string rather than an integer value.

View original
Did this help you find an answer to your question?
This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, 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.

1 reply

redgeographics
Celebrity
Forum|alt.badge.img+50
  • Celebrity
  • Best Answer
  • February 10, 2025

Do you have the geometry type set in the dashboards feature type? Many databases require that and if you supply geometry of a different type it'll reject the feature (you may see a warning in the log about that)

Mismatching attribute types can also be a reason, I've had a PostGIS writer dropping features because one attribute was a string rather than an integer value.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings