Azure Automation
An Azure service that is used to automate, configure, and install updates across hybrid environments.
1,349 questions
Get-PowerBIActivityEvent Error : Attempted to access an element as a type incompatible with the array.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(80, 64%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENP%3C/text%3E%3C/svg%3E)
Nikunj Patel
56
Reputation points
I am facing to powerBI activity using azure account automation runbook work. Successfully logging using Login-PowerBIServiceAccount is working correctly, but with these commands, Get-PowerBIActivityEvent, Get-PowerBIWorkspace I get the error:
Get-PowerBIActivityEvent : Attempted to access an element as a type incompatible with the array.
following version of powerbi module I used in azure automation account. Can someone help me how we can fix this?
$pbiAccount=Connect-PowerBIServiceAccount -TenantId $TenantId -ServicePrincipal -Credential $Credential
"Login with: $($pbiAccount.UserName)"
Get-PowerBIActivityEvent -StartDateTime '2023-07-26T05:00:00' -EndDateTime '2023-07-26T20:59:59' -ResultType JsonString
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 68%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELT%3C/text%3E%3C/svg%3E)
Limitless Technology 44,681 Reputation points2023-07-31T10:56:27.09+00:00 Hello,
The error message "Attempted to access an element as a type incompatible with the array" in the context of using the Get-PowerBIActivityEvent and Get-PowerBIWorkspace commands from the Power BI module suggests that there might be an issue with the data returned by these commands, which is not compatible with the array structure expected by the subsequent operations.
To troubleshoot and resolve this issue, you can try the following steps:
Check Module Version:
Verify that you are using the latest version of the Power BI module in your Azure Automation account. Outdated versions of the module might have known issues that are fixed in newer releases. To update the module, you can use the following PowerShell command within your Azure Automation Runbook:
Update-Module -Name MicrosoftPowerBIMgmt -Force
Verify Account Permissions:
Ensure that the account used to execute the Azure Automation Runbook has appropriate permissions to access Power BI data. The account should have the necessary permissions to query activities and workspaces in Power BI.
Check Cmdlet Parameters:
Review the parameters used in the Get-PowerBIActivityEvent and Get-PowerBIWorkspace cmdlets to ensure they are correctly set and not causing the error. Make sure you are passing valid and supported values for the parameters.
Inspect Error Details:
If the error message provides additional details or error codes, inspect them to get more insights into the issue. The error message might indicate the specific element or operation causing the problem.
Handle Null or Empty Values:
If the cmdlets return null or empty values for some elements, it could cause issues when attempting to access them as arrays. Ensure that your script handles such cases appropriately to avoid errors.
Validate Input Data:
Double-check the input data provided to the cmdlets. If you are passing parameters or variables as inputs, ensure that they contain valid data and are of the expected data types.
Try with Sample Data:
For testing purposes, you can try using the Get-PowerBIActivityEvent and Get-PowerBIWorkspace cmdlets with sample data to see if the error persists. This can help determine if the issue is related to the specific data being queried.
Contact Power BI Support:
If the issue persists after trying the above steps, consider reaching out to Power BI support for further assistance. They can help troubleshoot the issue in more detail and provide specific guidance.
Remember that debugging issues in an Azure Automation Runbook can sometimes be challenging due to limited access to real-time outputs. In such cases, it might be helpful to add logging statements or try the script locally with the same module version to capture detailed information about the error and its cause.
I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.
Hope this resolves your Query !!
--If the reply is helpful, please Upvote and Accept it as an answer–
-
Nikunj Patel 56 Reputation points
2023-07-31T11:59:56.4333333+00:00 lol AI not always resolve the answer. I already went through these and still it notworking.
-
tbgangav-MSFT 10,431 Reputation points2023-08-04T04:29:53.08+00:00 Hi @Nikunj Patel ,
Are you receiving the error in both 5.1 and 7.2 runtime versions of the runbook?
This might be related issue. Try the approach suggested in it.
Looks like it's more of pre-requisite or module dependency issue but not core Azure Automation issue. I have reached out to internal Azure Automation product team to get insights about it. Will keep you updated as I hear more information.
Sign in to comment
Sign in to answer