Using Microsoft.Graph PowerShell Module to Update a Sharepoint List

I've been working on a big VMware automation project for a customer who wants to use their Sharepoint site as the source of authority for configuration files.  They are using Microsoft Graph to give me access to that environment, so my permissions do not extend to the standard PnP.Powershell module and I've been learning the Microsoft.Graph module instead.

We came across an issue when using the new-MgSiteListItem cmdlet though, where we were getting error messages like "Field 'title' is not recognized."  In this case, there was a field called Title and the configuration that we'd passed the cmdlet specified Title, but the internal workings of the cmdlet were converting the first character to lowercase and thus the whole thing wasn't working.  But, there's an easy work-around!

The Microsoft.Graph PowerShell module has a catch-all cmdlet: Invoke-MgGraphRequest.  With it, you can use the Graph API directly, without having to worry about headers and authentication and stuff (since that part is managed by the Connect-MgGraph cmdlet)!  And fortunately, there's an easy-to-use API call that'll do exactly this!

So, the work-around is pretty easy.  First, I need to construct a new list item object.  If I had a list with these columns: Title, ReleaseDate, IMDBLink

I would do something like this:

$movie = new-object pscustomobject

$movie | Add-Member -Type NoteProperty -Name "Title" -Value "Spider-Man: No Way Home"

$movie | Add-Member -Type NoteProperty -Name "ReleaseDate" -Value "12/17/2021"

$movie | Add-Member -Type NoteProperty -Name "IMDBLink" -Value "https://www.imdb.com/title/tt10872600/"

Now that I've got my Sharepoint List Item object created, I need to wrap it up in an object that could contain the metadata that Sharepoint loves so much.  In this case, we only need a "fields" property, so I'll do it like this:

$sharepointItem = new-object pscustomobject

$sharepointItem | Add-Member -Type NoteProperty -Name "fields" -Value $movie

...and now we're ready to invoke that API call!

Invoke-MgGraphRequest -uri "v1.0/sites/$siteID/lists/$listID/items" -method POST -body ($sharepointItem | convertto-json)

And that's it!  The API is expecting that new row to be described in JSON using the structure that we created with the nested objects, so we simply convert that to JSON and pass it as the body of the API call!

P.S. That SiteID is the same SiteID that you'll use for any of the Graph powershell stuff.  I get my ListID by using: (Get-MgSiteList -siteId $siteID | ? {$_.displayName -eq "MyFavoriteMovies"}).id

Comments

Post a Comment

Sorry guys, I've been getting a lot of spam recently, so I've had to turn on comment moderation. I'll do my best to moderate them swiftly after they're submitted,

Popular posts from this blog

Clone a Standard vSwitch from one ESXi Host to Another

One of my customers is standardizing the configurations on their HP C7000 enclosures (they've been set up at various sites by various administrators with varying involvement from the architecture team).  As such, we need to stand up some temporary resources so that we can take down the main enclosure for reconfiguration.  That's fine, we can easily ship a smaller enclosure to each site for temporary compute resources.  Some of the sites are using Standard vSwitches, so we need to be able to quickly copy the networking configuration over from their existing blades to these new, slightly different blades.  As I see it, we had 2 good options: 1) Capture a Host Profile with the desired vSwitch configuration.  Delete every other component of the Host Profile so that only the networking section is applied; design the new ESXi hosts so that the vSwitches'll work with the old vmnic-to-vswitch configurations. 2) Write a script to clone the vSwitch from ones ESXi host to another.
Read more

PowerShell Sorting by Multiple Columns

PowerShell's Sort-Object cmdlet is super useful, especially when preparing output for human consumption.  A few people have found my blog while looking for more information about its use, specifically while looking for how to sort by multiple columns (well, properties, technically).  I've never done so (much less written about it), so I hope those folks found answers elsewhere.  But, it got me curious... and it turns out that it's really easy. The Technet article on Sort-Object has the answer directly spelled out: just use commas to create a list of properties to sort by (in order to precedence).  Let's look at some examples!  First, prepare a variable with some good sortable data: $myData = get-eventlog System -newest 25 And then we can get to sorting!  Say you want to sort primarily by EntryType (Warning, Information, Error) and then by Source.  Easy-peasy: $myData | sort EntryType,Source How about if you want it to be in descending order?  Yeah, there&
Read more

Deleting Orphaned (AKA Zombie) VMDK Files

A problem that most Virtualization Administrators need to deal with is Orphaned VMDK files (or Zombie VMDK files, as some people call them).  These are Virtual Machine hard drive files that are just hanging out, taking up storage, but are attached to no VMs.  How can this happen?  Well, the most common way is when an administrator needs to delete a VMDK but isn't quite ready to commit... so, after pressing "remove", they select "remove from virtual machine" rather than "remove and delete files".  The intent is always good: "I want to be able to restore this if it turns out to be necessary... so I'll just come back and delete it next week if nothing breaks!"  But, of course, next week something else happens and the file doesn't get deleted.  After a little while, it turns into "which files did I rename, again?" and nothing seems to happen. So, how do you deal with these orphaned files?  Well, a few years ago I found a scrip
Read more