DQ Monitoring project UAT/Test deployment

Thank you very much Maxim Kim,

I have 2 monitoring projects to deploy. Seems like recreation of DQ Monitoring project is the easiest way.

Also is there any recommended practice from Ataccama for such kind of deployments.

I’m in a similar situation and would love to know how you resolved it. Did you have to recreate the monitoring project along with its associated rules in the test environment? Or did you create a deployment plan that included the monitoring project as well as the entities it was applied to in the test environment? Kindly clarify.

I raised this with Ataccama back in February 2024 and they added exporting/importing monitoring projects across environments to some of their feature requests and they advised it likely wouldn’t be available by late v15/v16 so hopefully from v17 onwards it will be available but not guaranteed 😬

I have found it easy exporting/importing DQ rules across environments though using the Export plan Maxim included in the screenshot above

Yes, DQ Rules can be exported, and I have tried before. (although I am still facing some issues in import). But for Monitoring projects, we need to recreate then in TEST and Prod environments. I guess no shortcuts :D

Are the issues with your importing related to DQ rules which contains either a lookup, a group by (aggregated rule) or a convert variable (e.g. convert from string to integer)? If so, I had these issues too and the bug was fixed in v14.5.3 and v15.2.0. If you have an older version I have some manual workarounds which aren’t ideal but helps a little

Mine is already v15.4 Dev and TEST both. But you are right. One of the rule is accuracy rule with lookup table. But before importing DQ rule I already prepared Lookuo table in advance to avoid any issue. But still Import gave errors and then I recreated them in TEST and then Prod. But still your workaround can be helpful for future. Thanks in advance.

And to Susan24us Yes DQ rules can be exported and imported if they are simple as Rianna mentioned above.

Regards,

Ojaswini

Hello ​@Ojaswini, here are my manual workarounds to see if they work for you 🙂

I recommend exporting the “problem” rules you have on their own for these solutions. So only 1 DQ rule per Export/Import.

Solution 1

Export the DQ rule as usual and in the downloaded ZIP folder, open up the text file called “metadata00001rule”.

In the text file, find the code which looks like the below:

Amend the green highlighted part to the ID of the new lookup item you created in the other Ataccama environment you want to import the rule to.

(You can find the ID in the web URL when you have the lookup open - example below).

Save the text file changes you made and import as per the usual process you follow.

Solution 2

Export the DQ rule as usual and this time don’t make any changes to the downloaded zip folder.

In the import upload, select “import as draft and publish”.

Because the rule has an error, it should still be imported but not published. Then find the DQ rule in the “unpublished” area and update the rule implementation to select your newly created lookup item.

As I mentioned they are very manual solutions ☹️ 

Wow that’s interesting Rianna. Thank you for this. Yes, I assumed that the issue might because of Id diff between DEV and TEST but was not sure where and how to correct that. Because Ataccama objects metadata is all about their respective IDs that we see in browser. 

I will definitely try this. Thanks again.