Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and a 50 percent discount on exams.
Get startedEarn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
Hello
I'm trying to use the new feature of the API to receive table and columns names (Enhanced admin APIs responses with detailed metadata (currently in Preview)).
However, after following the instructions (setting up service principles with tenant rights , Metadata Scanning) and republishing my datasets, the results of GetScanResult is still empty for the tables field.
For reference, this is what the example in the documentation is showing. List of datasets, with repsective tables and column names. However, in my call, these fileds remain empty even after checking all the requirements and limitations.
"datasets": [
{
"id": "e7e8a355-e77b-4418-a7b8-ae5972fdaa03",
"name": "ExportB",
"tables": [
{
"name": "EIM",
"columns": [
{
"name": "RowNumber-2662979B-1795-4F74-8F37-6A1BA8059B61",
"dataType": "Int64",
"isHidden": true
}
],
Has anyone managed to get this feature to work? Can you help me with figuring out the issue?Thanks for your help
Solved! Go to Solution.
Hi Gilbert
Thanks for the hint. With the resource, I was able to find my mistake.
In the WorkspaceInfo post request, the optional parameter datasetSchema=true has to be set to then get a scanID that returns table and column names in the scanResult call.
Thank you again for the quick response!
I have added parameter datasetSchema=true still table block is showing empty for me.
Hi @lps_pbi
I have not tried it yet, but the blog post from PowerBI.tips is certain to work if you want to give it a try?
Using the Power BI Scanner API to Manage Tenant's Entire Metadata -
Hi Gilbert
Thanks for the hint. With the resource, I was able to find my mistake.
In the WorkspaceInfo post request, the optional parameter datasetSchema=true has to be set to then get a scanID that returns table and column names in the scanResult call.
Thank you again for the quick response!