Dataplex - Publish data scan result to BigqueryUI

[SebasPostigo]

Hello,

I'm automating the creation of datascans through the dataplex python sdk but can't create it with this option checked.

I was reading the documentation for the sdk and the rest api but I couldn't find any information. Any suggestions on how to activate that option through the sdk?

[NorieRam]

Hi @SebasPostigo ,

Welcome to Google Cloud Community!

In your case, you might see this documentation about publishing data quality scans. The publishing option might be unavailable if you lack the required permissions or if another data quality scan is already set to publish results. 

You can also refer to a similar case on what @ms4446 solution about permissions.

“To ensure the Dataplex service account can publish scan results, verify that it has the necessary BigQuery roles. Specifically, the service account needs the `roles/bigquery.dataEditor` role to create tables and insert data.”

While roles like `roles/bigquery.dataViewer` and `roles/bigquery.jobUser` are important for other tasks, they do not suffice for publishing results. To grant the required permissions, navigate to the dataset in the BigQuery console, click "Share," and assign the `roles/bigquery.dataEditor` role to the Dataplex service account.

With that, you can also check the reference that @caryna  gave from this case from a Youtube video explaining Automated data profiling and quality scan via Dataplex.

I hope the above information is helpful.

[SebasPostigo]

Hello @NorieRam.

Thanks for your answer,

I verified the roles and the name of the other quality rules but it didn't help.

What i was looking for was the attribute of the API or SDK in order to mark that check programmatically.

Im automating the creation of data quality scans, so I need to simulate the behavior of this part of the UI but through the sdk or api

[GGreg0946]

This is the top voted bug on the Google Dataplex issue tracker: https://issuetracker.google.com/issues/298572633 somehow this has been reported for over a year and the team at Google has still not fixed it. Add an impacted vote and maybe the team will consider fixing it at some point.