• State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 96 subscribers
  • Views 4047 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Daisy Chain startup configurations in Sync Editor

Robert Byrne
over 6 years ago

Hi,

We have several startup configurations for a Sync Project that use different variable sets to treat different subsets of data.

Is there a standard way to chain these together so they execute one after the other: as one completes the next one starts up?

I was thinking of defining a custom attribute to hold a 'next startup configuration' value and then adding a step to the end of the process chain on DPRProjectionStartInfo to trigger the next startup configuration.

Is that a way to go?

thanks,

Rob.

Parents
  • +1 over 6 years ago

    Hi Rob,

    coming with version 8 you can define a logical group for startup configurations of a sync project and define the concurrence behavior.

    If you choose Postpone and wait only one startup configuration of the group can be started concurrently. If another one will be started, the execution will be postponed until the running startup configuration has finished.

    So in your example, where an execution order is not required you would just simply start all startup configurations at once and let the system do the rest.

    The other available concurrence behaviors are Stop with error and Ignore.

    Hth

Reply
  • +1 over 6 years ago

    Hi Rob,

    coming with version 8 you can define a logical group for startup configurations of a sync project and define the concurrence behavior.

    If you choose Postpone and wait only one startup configuration of the group can be started concurrently. If another one will be started, the execution will be postponed until the running startup configuration has finished.

    So in your example, where an execution order is not required you would just simply start all startup configurations at once and let the system do the rest.

    The other available concurrence behaviors are Stop with error and Ignore.

    Hth

Children
No Data