|
Klassiske filtyper er ikke lenger tilgjengelige for bruk fra og med januar 2021. Du kan overføre klassiske filer eller laste ned en PDF-fil. Finn ut mer

Automating Dev to UAT Promotion Without Recreating Objects – Guidance on Using Chains

Besvart
Be om demo

Hi everyone,

We’re currently working with multiple Workiva workspaces — Development, UAT, and Production — and looking to streamline our promotion process between these environments.

Right now, when we import updated Wdata or Wdesk objects (like tables, queries, or spreadsheets) from Dev to UAT, the system tends to recreate these objects with new IDs, rather than updating the existing ones. This breaks existing integrations, automations, and folder structures — adding significant overhead.

We're exploring whether this process can be automated using Workiva Chains, ideally in a way that:

  • Overwrites or updates existing objects instead of recreating them

  • Preserves object IDs where possible

  • Maintains references, such as:

    • Linked spreadsheets to Wdata queries

    • Associated automations like sheet locking/unlocking

  • Preserves or replicates folder structure and permissions

  • Can be scaled across multiple environments (Dev → UAT → Prod)

We’re comfortable using APIs or Chain Portability features if needed.

Would love to hear from anyone who has tackled this before or has guidance on best practices here.

Thanks in advance!

Best regards,
Somu Pavan

1

Kommentarer

1 kommentar

Dato Stemmer
  • Jeff Hickey

    Hi Somu Sri Pavan Sundeep,

    Anytime a new Workiva object is created, it gets it's own unique static ID. This is why, for example, if you import a Wdata Table, it has it's own unique ID which is different from the original Table that was exported. Workiva object IDs cannot be edited.

    If you want the object ID to persist, but don't want any data in the object, you would need to clear the object rather than trying to recreate it. Since this will keep the ID intact, it will also maintain references to the object (Query source, automations, etc) as well as the folder structure and permissions. If needed, permissions can be modified via the Prototype Platform API.

    If you did go the with Chains, you could make use of Workspace Variables to assist with the promotion process between Chain Builder Environments. This is similar to environment variables when scripting.

    0

Logg på for å legge inn en kommentar.