Include system object tags in solution package / deployment

Simon_
Simon_ Member
edited 12:38AM in Ideas board

What problem are you facing?

When creating / deploying a solution, system object tags set on datasets/views etc. are not included.

What impact does this problem have on you/your business?

We have used system object tags to ensure a core set of tags are consistent across spaces (e.g. input data, output data, schema). When creating a solution, the system object tags are not included.

When deploying the solution to another environment, the system object tags are not included, this requires us to manually add the object tags against each dataset/view. This has to be done each time we deploy the solution, as deploying the solution removes any system object tags set on the dataset/view etc. in the environment we deploy to.

We also use object tags for specific things per space, these transfer through a solution deployment without issue.

Do you have any existing workarounds? If so, please describe those.

Manually add the system tags on each workflow / dataset / view etc.

This has to be done each time we deploy the solution (e.g. pushing changes from test to production), as deploying the solution removes out any existing system object tags set against the dataset/view etc.

Do you have any suggestions to solve the problem? Feel free to add images if this helps.

1
Up
1 votes

Gathering interest · Last Updated

Comments

  • Mirjam Schuke
    Mirjam Schuke Administrator
    edited 4:56PM

    Hi Simon, I'll have a look into this for you, how we can make this more convenient.
    Ok, so as per the documentation Data Quality user documentation | Object tags system tags can be used in multiple spaces across the same environment and also be shared across those spaces. User-defined tags (per space) can be exported and imported via dmx files into other environments.

    So in your solutions case it might make sense to create user-defined tags in the space where you develop the solution and then export/import the file including the user-defined tags to the other environments. Those tags will then also exist in the new environment. This then works the same way as the tags per space you mentioned.

Categories