Supplies are limited. Contact info@espc.tech right away to save your spot before the conference sells out.
Get your discountScore big with last-minute savings on the final tickets to FabCon Vienna. Secure your discount
Here is my PowerShell script:
$credential = New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList "APPID", ("Secret" | ConvertTo-SecureString -AsPlainText -Force)
Connect-PowerBIServiceAccount -ServicePrincipal -Tenant "TenantID" -Credential $credential -Environment "Public"
Export-PowerBIDataflow -WorkspaceId "eae420bb-eb1b-40a5-90d6-a057156bdcc6" -Id "459dc124-187d-48cf-9888-4f2be43f61bf" -OutFile C:\Users\chbonier\Documents\DTF
Here is the error :
Export-PowerBIDataflow : Failed to write dataflow with ID 459dc124-187d-48cf-9888-4f2be43f61bf to file C:\Users\chbonier\Documents\DTF. Message: L'accès au chemin
d'accès 'C:\Users\chbonier\Documents\DTF' est refusé.
Au caractère Ligne:6 : 1
+ Export-PowerBIDataflow -WorkspaceId "eae420bb-eb1b-40a5-90d6-a057156b ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : WriteError: (Microsoft.Power...PowerBIDataflow:ExportPowerBIDataflow) [Export-PowerBIDataflow], Exception
+ FullyQualifiedErrorId : Failed to write dataflow with ID 459dc124-187d-48cf-9888-4f2be43f61bf to file C:\Users\chbonier\Documents\DTF. Message: L'accès au chemin
d'accès 'C:\Users\chbonier\Documents\DTF' est refusé.,Microsoft.PowerBI.Commands.Data.ExportPowerBIDataflow
Why access to the path is refused ?
Thanks In Advance,
Charline
Solved! Go to Solution.
HI @Charline_74,
According to The error message, it seems like these scripts failed to access to the specific path. I'd like to suggest you check the permissions of the PowerShell and folder if it allows to execute these operations.
In addition, you can also try to change the absolute path to relative path if it helps with these process.
Regards,
Xiaoxin Sheng
HI @Charline_74,
According to The error message, it seems like these scripts failed to access to the specific path. I'd like to suggest you check the permissions of the PowerShell and folder if it allows to execute these operations.
In addition, you can also try to change the absolute path to relative path if it helps with these process.
Regards,
Xiaoxin Sheng
User | Count |
---|---|
10 | |
5 | |
4 | |
4 | |
3 |
User | Count |
---|---|
14 | |
9 | |
5 | |
5 | |
4 |