Prevent import synchronizer from creating new elements in Target.

Comments

4 comments

  • Avatar
    Jason Rose

    I feel like this should be possible already but I can't think of any way of doing it so I support this story. A workaround might be having a delete elements SAT straight afterwards that finds anything created by that SAT?

    1
    Comment actions Permalink
  • Avatar
    Soren Staun

    I agree, that's a solution, but

    1. It's also a performance hit. We have situations with 30-60 SATs running in succession to achieve copies/versions of objects, updates of data and relationships and anything that can cut down on SAT execution time is money well spent.

    2. It's also an implementation of an old anti pattern called "The Travelling Gypsies". Basically, you have things appear to make them disappear, then appear, to make them disappear. This creates audit logs inside MooD, CDC records if you're using CDC (build 117 of MooD 15 and forward). It's simply bad design.

    We optimize our SATs in such a way that if we have 5 excel exports, we convert them into 1 excel export with tabs just to not having to open, stream and close files 5 times but only once. Every little performance hit matters in this area.

    1
    Comment actions Permalink
  • Avatar
    Jason Rose

    Yes, completely agreed Soren. It would definitely be better! Faster, fewer needless records, and also in addition less effort to set up in the first place and less likely to make mistakes and delete the wrong thing or miss anything.

    I'm just offering a potential solution for anyone trying to work around this problem right now with existing functionality in case someone is reading this who has this exact issue and can't wait for a future build :)

    1
    Comment actions Permalink
  • Avatar
    Soren Staun

    Completely recognize your problem solving mode, Jason :-) It is viable, but we shouldn't rest on the laurels and ignore the issue. 

    1
    Comment actions Permalink

Please sign in to leave a comment.