Problem with Get-SPOWeb about pnp-powershell HOT 9 CLOSED

Hi Dean - your getting this error as not all of the Web object properties are brought back on calling Get-SPOWeb

Do you get the same issue if you use Get-SPOWeb | Select-Object *

from pnp-powershell.

No, i get a different error
get-spoweb : The request uses too many resources.
At line:1 char:1

• get-spoweb | Select-Object *

• - CategoryInfo          : WriteError: (:) [Get-SPOWeb], ServerException
  - FullyQualifiedErrorId : EXCEPTION,OfficeDevPnP.PowerShell.Commands.GetWeb
  

from pnp-powershell.

Hi Dean,

The Issue is because not all the properties of the Web object are initialised as part of the Get-SPOWeb function.

At the Hierarchical level the web object contains other objects as can be seen below - not all of them are called back as part of the web object as they aren't normally necessary and therefore they are only returned when explicitly called for.

This is one of the drawbacks of CSOM but the additional code to call and return all the web object properties wouldn't be overly worthwhile (in my opinion)

However that being said perhaps there could be an additional switch for the Get-SPOWeb function that would then make that enhanced call.

@erwinvanhunen - Do you think that adding an additional switch would be worthwhile or more of a headache to implement?

from pnp-powershell.

Adding an additional switch would be pretty complex, given that some properties will fail to load if certain features are not active. It would generate quite an additional load.

I created a new cmdlet: Get-SPOProperty which relatively easily allows to load certain properties:

for instance:

$web = Get-SPOWeb
Get-SPOProperty -ClientObject $web -Property Lists

This will load the lists property and if possible return it's value to the output. You can mix and match, so

Get-SPOProperty -ClientObject (Get-SPOWeb).Lists.GetByTitle("Site Assets") -Property Views

will also work.

A shorthand version of the cmdlet parameters is:

Get-SPOProperty $web Lists

First parameter is the object to use, second parameter is the property to load. You can optionally specifiy a list of properties. It will however not output those values by default, e.g. you have to output them yourself:

Get-SPOProperty -ClientObject $web -Property Lists, Title, Id
$web.Lists
$web.Title
$web.Id

The examples above use a web object, but it applies to any of the objects that are being returned by the cmdlets, so lists, views, content types, etc. etc.

from pnp-powershell.

Hello Erwin, it looks like working approach for many SPOWeb properties, but not for Navigation:

PS C:\Windows\system32> Get-SPOProperty -ClientObject $web -Property Navigation
format-default : The collection has not been initialized. It has not been requested or the request has not been executed. It may need to be explicitly
requested.
+ CategoryInfo : NotSpecified: (:) [format-default], CollectionNotInitializedException
+ FullyQualifiedErrorId : Microsoft.SharePoint.Client.CollectionNotInitializedException,Microsoft.PowerShell.Commands.FormatDefaultCommand

from pnp-powershell.

Sorry for the extremely long delay. The reason for you not being able to load the Navigation element this way is that Navigation object is actually a collection of nodes. PowerShell tries to resolve each property of each node, which also haven't been loaded. Hence the error.

It's possible to chain things:

$w = Get-SPOWeb
$navigation = Get-SPOProperty $w Navigation
$quicklaunch = Get-SPOProperty $navigation QuickLaunch
$topnode = $quicklaunch[0]
$ctx = Get-SPOContext
$ctx.Load($topnode)
Execute-SPOQuery

$topnode.Title

Closing this issues.

from pnp-powershell.

Thank you Erwin, and by the way, it even works without spocontext, so it's even better:

$web = Get-SPOWeb;
$navigation = Get-SPOProperty $web Navigation;
$topNavigationBar = Get-SPOProperty $navigation TopNavigationBar;
$topNavigationBar[0].Title;

I tested with SharePoint 2013

from pnp-powershell.

I get the error when adding an item to a tiles list. The item is added but I still get the error on this command:
Add-PnPListItem -List $listName -Web $targetWeb -Values $itemColumns
Why does it work but still return an error? I can't move on afterward.

from pnp-powershell.

@asestromsrud can you share the error your receive?

from pnp-powershell.