Skip to main content
Question

dynamic changedetector - to loop or not to loop?

  • February 26, 2019
  • 2 replies
  • 25 views

oliver.morris
Contributor
Forum|alt.badge.img+14

Hi started to use the new changedetector to identify changes between data stored in a database in sqlserver spatials versus a postgres SDE. I initially started doing it for each table but there are aroun 60 so quickly lost the will to continue.

I worked up the following dynamic tool:

At the moment it only works one feature at a time (currently I am just loading the table name in the first attribute creator.

My question is how should I run this for more that one table at a time. Will it work by passing a list of features to the feature readers or should I basically add this into a loop and just run one at a time through the loop.

I really welcome your recommendations.

Thank you

Oliver

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.

2 replies

ebygomm
Influencer
Forum|alt.badge.img+44
  • Influencer
  • 3429 replies
  • February 26, 2019
Set your attributecreator so that feature is set from a parameter, then set up a second workspace with a workspace runner to run the change workspace once for each table.

oliver.morris
Contributor
Forum|alt.badge.img+14
  • Author
  • Contributor
  • 176 replies
  • February 26, 2019
Set your attributecreator so that feature is set from a parameter, then set up a second workspace with a workspace runner to run the change workspace once for each table.

perfect, with give that a go.