topic Re: Using Get-PowerBIWorkspace PowerShell command in Developer

Using Get-PowerBIWorkspace PowerShell command

vrocca — Wed, 25 Jul 2018 16:14:01 GMT

This may be a simple/dumb question, but I'm trying to get a list of Workspaces using PowerShell, and I'm getting an error "Attempted to access an element as a type incompatible with the array"

What am I doing wrong?

Re: Using Get-PowerBIWorkspace PowerShell command

kayu — Wed, 25 Jul 2018 16:32:13 GMT

Hi Victor, would you be so kind to head over to the githup repo of the cmdlets and file this as an issue under: https://github.com/Microsoft/powerbi-powershell/issues? I've seen this error before but it went away after I updated .NET and Powershell. Hope this helps.

Cheers,

Kay

Re: Using Get-PowerBIWorkspace PowerShell command

kayu — Wed, 25 Jul 2018 16:34:34 GMT

Cheers,

Kay

Re: Using Get-PowerBIWorkspace PowerShell command

vrocca — Wed, 25 Jul 2018 18:32:11 GMT

Thanks Kay.

I have PSVersion 5.1 and .NET Framework 4.7. Do you have something different?

Re: Using Get-PowerBIWorkspace PowerShell command

vrocca — Tue, 31 Jul 2018 11:32:26 GMT

It looks like the issue was being caused by a Newtonsoft.Json conflict.

"The issue is likely due to a mismatch in Newtonsoft.Json between the Power BI cmdlets and some other cmdlets loaded into PowerShell session (via profile or calling directly)"

More info here: https://github.com/Microsoft/powerbi-powershell/issues/60

Current workaround is to use Powershell Core

Re: Using Get-PowerBIWorkspace PowerShell command

timmac — Mon, 15 Apr 2019 20:47:29 GMT

I was battling this error as well. However, I was able to get by it by using a user that is a Global Administrator. I would suggest double checking that as well.

Re: Using Get-PowerBIWorkspace PowerShell command

TheFlyingBadger — Tue, 11 Feb 2020 23:43:46 GMT

it's a bit of a necro-thread reply, however i was able to work out what was going on...

Essentially it seems that Powershell only loads one version of each DLL (per session), no matter how many modules you are referencing it from. This of course makes perfect sense - UNTIL you first reference a module which uses an "old" version of newtonsoft.json.dll (I did a search, and had >50 newtonsoft.json.dll files on my PC with many different versions).

So the trick is, at the start of a Powershell session make sure you load a module which references a new enough version of the newtonsoft DLL

this did the trick for me.

if (Get-Module -Name MicrosoftPowerBIMgmt -ListAvailable) { Import-Module MicrosoftPowerBIMgmt -ErrorAction SilentlyContinue #workaround }