Powershell: Why does my Google Sheet formula have a leading single quote?

I was recently writing a simple Powershell script to automatically create data in Google Sheets. I used the excellent post from James Chambers to show me the details of the process.

The code is simple enough 

1. Import-Module UMN-Google

2. Use Set-GSheetData to populate the data

It all works until the Hyperlinks I created were being rendered as strings, with leading single quotes. This means they look pretty awful and I dont intend to manually correct them. #defeatsthepurpose.

The solution is to force the Set-GSheetData with -valueInputOption "USER_ENTERED" which then overrides the default behaviour of setting the values to a string.

Simple when you know how.

Comments

Post a Comment

Popular posts from this blog

SharePoint 2013: Error updating managed account credentials

I encountered the following message when trying to change a password for a managed account: Error deploying administration application pool credentials. Another deployment may be active. An object of the type Microsoft.SharePoint.Administration.SPAdminAppPoolCredentialDeploymentJobDefinition named "job-admin-apppool-change" already exists under the parent Microsoft.SharePoint.Administration.SPTimerService named "SPTimerV4".  Rename your object or delete the existing object. The error message is self explanatory - Rename your object or delete the existing object.  I choose the latter. Powershell to the rescue. $job = Get-SPTimerJob -Identity "job-admin-apppool-change" $job.Delete() Reset the password and all should be good.
Read more

Error deploying Nintex workflow: An item with the same key has already been added

My client recently upgraded their version of Nintex Workflow 2010 and suddenly some of my workflows started to fail on deployment. The following error cropped up: Error deploying workflow: Server was unable to process request. ---> An item with the same key has already been added. ---> An item with the same key has already been added. WTF???? A little digging unveiled the problem - I had two items in a 'Create Item' shape with the SAME DISPLAYNAME. I needed to move the second item to a new 'Update Item' shape in order for it to work. I order to get the workflow to deploy, I had to manually remove the 'duplicate' item from the serialized XML. Hooray!! It was then a simple matter of creating a new shape to update the 'duplicate' value.
Read more