Skip to main content

Improve Release copy process

Some examples of current challenges:

  • The current process is managed in a static pop‑up window.

  • The Sources replacement step requires to manually update potentially dozens of target entries within the pop‑up, instead of substituting the source, e.g., ECC_US to ECC_EU.

  • It does not allow copying by blocks, i.e. a full copy is the only option.

  • Even if the job fails, a new release may be partially created.

Idea for improvement: dedicated section for release copies including:

  • Configuration and preview side by side

  • Allow execution by blocks, e.g. copy by subject area, by dataset

  • Dataset design copy decision, i.e. create a new datasets or reuse

  • Process monitoring

  • Backend code support

  • Releases comparison post copy: datasets, mappings, reports, ETLs, code…

This section could also manage additional features related to development reusability within Migrate.

Status: Planned1 comment

Log in to comment and vote

Comments1

  • Kevin McDonald

    Team•

    Apr 27

    Hi Ana - Thanks for reaching out and sharing your feedback. We’ve received it and are reviewing it with the team.

    If we have any follow-up questions or need more details, we’ll be in touch. We appreciate you helping us improve.