Skip to main content
Question

How to do DQ of tables with having dynamic names (changing as per release)

  • November 4, 2025
  • 1 reply
  • 9 views

Hello ​@Lisa Kovalskaia ​@anna.spakova 

I have a requirement to do DQ of few tables that have names changing as per schedules of a release. e.g., Table Name could be Table1_release_1 etc. The database and schema are constant. The scope/structure of DQ attributes is mostly same.

For now, I think it will need manual intervention to onboard new objects → Add DQ on attributes and then add monitoring projects manually. Is there any way we can automate this process?

I am using v15.4

1 reply

anna.spakova
Ataccamer
Forum|alt.badge.img+3
  • Ataccamer
  • 211 replies
  • November 6, 2025

Hi ​@mp_ataccamauser ,

there might be a way to replace the table in the existing project with a new version of the table (with the new name) using API. But it is not a recommended approach, although it should work (I’ve done it for a customer for a different usecase, but the ultimate goal was the same). There is not an out of the box feature in the product for this (that wouldn’t require manual effort). A prerequisite also is that the structure of the tables is 100% same, otherwise some DQ rules may fail to be applied on the new table.

For the manual approach, you can use the Import configuration feature that allows to quickly create a new project based on a configuration of an existing one. https://docs.ataccama.com/one/15.4.0/monitoring-projects/monitoring-project-import-configuration.html

If you are okay with creating a new project, that is also possible through API. You can create the project and assign the DQ rules if you know which ones → you can even download the logic and assign rules from the existing project (with the “old” table) and then just apply the same DQ checks on the new table in a new project. Or even in the same project, where you can simply add the new table as a new catalog item.

What is fair to mention is that the APIs in this case are quite complex because of the structure of the metadata model. But if this were an approach you would be willing to take, please let me know, and I can share details for both approaches.

Kind regards,

Anna

Â