Cli-microsoft365: spo listitem set SingleMetadataField

[ahyland]

When executing the cmd:

o365 spo listitem set -u "https://tenant.sharepoint.com/sites/sitecol" -i "9" -t "All Documents" --SingleMetadataField "Term Name|448496d0-f253-46a1-ad02-5e6d84f84b58;"

I get the error:
'448496d0-f253-46a1-ad02-5e6d84f84b58' is not recognized as an internal or external command,
operable program or batch file.

When running the following:

o365 spo listitem set -u "https://tenant.sharepoint.com/sites/sitecol" -i "9" -t "All Do cuments" --SinglePeopleField "[{'Key':'i:0#.f|membership|[email protected]'}]"

I also get a similar message:
'membership' is not recognized as an internal or external command,
operable program or batch file.

Running version: 1.22.0

Not sure if I am doing something wrong here or if an issue.

[waldekmastykarz]

In which shell and on which OS are you seeing this?

[ahyland]

Hi Waldek,

This is on Windows 10 using Windows PowerShell version 5.1.17134.590

[VelinGeorgiev]

Seems that the | char is causing the issues when cmd or powershell , I found some documents saying the ^ should escape the | char and thread it as text so I tried specifying term value like that "'Term name'^|GUID", but it did not work for me. Reference to the source I used: https://www.robvanderwoude.com/escapechars.php

@waldekmastykarz, I am thinking on we can simplify that to the user so just term guid is passed or just user email is passed as option value and then the cli does the | concatenation on the background.

[phillipharding]

The command below works when using a bash shell on macOS

spo listitem set -u https://contoso.sharepoint.com/sites/somesite -t "Library Title" -i <id> --MetadataFieldName '`Label|Termguid`'

Sounds like it could be similar to #625

spo customaction set with --clientSideComponentProperties param results in invalid JSON object

[waldekmastykarz]

@VelinGeorgiev I would prefer avoiding introducing any specific constructs in the CLI if it's a shell-specific thing. Let's see if there are any known issues and ways around it.

[waldekmastykarz]

@ahyland could you please try what @phillipharding proposed and see if it helps?

[ahyland]

@waldekmastykarz I have just tried this now using Windows PowerShell however I get the same output.

'448496d0-f253-46a1-ad02-5e6d84f84b58`' is not recognized as an internal or external command,
operable program or batch file.

[waldekmastykarz]

Unfortunately, I can't reproduce the issue. When I try to execute the exact command, it's working just fine. I'm using:

• CLI v1.22.0
• PowerShell 5.1.17134.407
• Win 10

Anything else that I could try?

[ahyland]

@waldekmastykarz could you please give me the cmd you have run so I can give it a try. Thanks!

[waldekmastykarz]

It's exactly what you put in your original issue:

o365 spo listitem set -u "https://tenant.sharepoint.com/sites/sitecol" -i "9" -t "All Documents" --SingleMetadataField "Term Name|448496d0-f253-46a1-ad02-5e6d84f84b58;"

[ahyland]

Hi @waldekmastykarz sorry for the delay in getting back to you.

I have had other users test this and they confirm that they have the same issue?

[VelinGeorgiev]

I @ahyland , I can also reproduce it. I do not have enough time to troubleshot and see If I can find a solution. I will try to find some time until the end of the week so see if I can find working solution.

[VelinGeorgiev]

I have tried several more things, but I am running out of options here.

I am thinking of enhancing the CLI and introducing our own special character combination for the input when we have to use | char to make it work with Windows cmds that do not accept that. For example encodeURIComponent('|') resolves in %7C. We can look for %7C input and send it to the apis as | char. This way we will escape death by windows cmd.

Example:

--SingleMetadataField "Term Name%7C448496d0-f253-46a1-ad02-5e6d84f84b58;"

to be translated and send by the CLI like

--SingleMetadataField "Term Name|C448496d0-f253-46a1-ad02-5e6d84f84b58;"

@waldekmastykarz what do you think?

[waldekmastykarz]

@VelinGeorgiev what configuration have you used to repro the issue? As I mentioned, using

• CLI v1.22.0
• PowerShell 5.1.17134.407
• Win 10

everything is working as expected

[VelinGeorgiev]

Here is what I have

• CLI v1.22.0
• I used cmd.exe (have not tested in the PowerShell console, but I can)
  

[waldekmastykarz]

It could be, that in cmd, you'd need to wrap quotes in another pair of quotes. It could be that the first pair of quotes get removed and what's passed into the cmd is the raw | which is parsed as piping rather than a command argument.

[VelinGeorgiev]

I tried dozen combinations . Nothing worked for me.

[waldekmastykarz]

I'll see if I can repro it with cmd. 👍

[waldekmastykarz]

Unfortunately, I still can't repro it. I tried in both cmd.exe as well as cmder and in both cases the command as mentioned literally in the original comment works as expected. What am I missing guys?

[waldekmastykarz]

Closing due to lack of response