add_ADLS_csv
add_ADLS_csv
Functions
Name | Description |
---|---|
add_csv_from_blob | Add a csv file store in a ADLS blob container to a dashboard |
add_csv_from_blob
add_ADLS_csv.add_csv_from_blob(
dashboard_path,
account_url,
blob_name,
data_path,=None,
tenant_id=False,
use_saved_storage_key=None,
SAS_url=None,
storage_account_key=True,
warnings )
Add a csv file store in a ADLS blob container to a dashboard
DO NOT HARD CODE CREDENTIALS. Use the use_saved_storage_key option instead.
This function creates custom M code and is therefore more picky than pandas or Power BI desktop. The csv file should probably not have row numbers. (Any column without a column name will be renamed to “probably_an_index_column”) NA values must display as “NA” or “null” not as N/A. If the data is malformed in Power BI, try cleaning it first in python and then rerunning this function.
This function creates a new TMDL file defining the dataset in TMDL format and also in M code. The DiagramLayout and Model.tmdl files are updated to include refrences to the new dataset. Other dumb things: If you get an error when trying to open the .pbip file try changing the combatibility version to 1567 in the semanticmodel > definition > database.tmdl file. Thanks Microsoft for yet again doing a great job with backward compatibility lol. Dashboards created with the create_blank_dashboard() function start with the compatibility version set to 1567, so you should only have this problem with manually created dashboards. I may eventually add an automatic fix for this.
:param str dashboard_path: The path where the dashboard files are stored. (This is the top level directory containing the .pbip file and Report and SemanticModel folders). :param str account_url: The url to your Azure storage account. It should be in the format of https://
:returns: None