New command: spo list defaultvalue clear

[milanholemans]

Usage

m365 spo list defaultvalue clear [options]

Description

Clears default column values for a specific document library

Options

Option	Description
-u, --webUrl <webUrl>	URL of the site where the list is located.
-i, --listId [listId]	ID of the list. Specify either listTitle, listId, or listUrl.
-t, --listTitle [listTitle]	Title of the list. Specify either listTitle, listId, or listUrl.
--listUrl [listUrl]	Server- or site-relative URL of the list. Specify either listTitle, listId, or listUrl.
--fieldName [fieldName]	Internal name of the field to clear over the entire list. Specify either fieldName or folderUrl, but not both.
--folderUrl [folderUrl]	Clear all fields of a specific folder. Specify either fieldName or folderUrl, but not both.
-f, --force	Don't prompt for confirmation.

Examples

Remove all default column values from a library

m365 spo list defaultvalue clear --webUrl https://contoso.sharepoint.com/sites/Marketing --listTitle Logos

Clear a field from all folders of a library

m365 spo list defaultvalue clear --webUrl https://contoso.sharepoint.com/sites/Marketing --listTitle Logos --field Company

Clear all fields from a specific folder

m365 spo list defaultvalue clear --webUrl https://contoso.sharepoint.com/sites/Marketing --listTitle Logos --folderUrl "/sites/Marketing/Logos/Contoso"

Default properties

No response

Additional Info

No response

[waldekmastykarz]

I find it confusing that we use column in the command name, but field as the option to refer to the column. I suggest we align them. Since we use field everywhere else, I suggest we use field.

Are there other operations that we might want to do on a list column? If so, we should consider using the spo list field defaultvalue verb format to accommodate future changes.

[martinlingstuyl]

I believe this is not about default values set on fields, but library default values, set on field/folder combinations. This is a spo legacy feature that by the way I've seen odd behavior with in modern document set forms.

field defaultvalue would be less clearly referring to that.

[waldekmastykarz]

I understand that. I only find it confusing that we're referring to the same thing using two different words in one command. Have we considered dropping the field/column part altogether and using something like spo list defaultvalue [verb] and then use unknown options that represent field internal names to set/clear values?

[milanholemans]

In the UI, it's called column default values:

That's why I choose this name, so people can easily find it as command. I understand that it might be confusing, what't the difference between a column and a field. However field defaultvalue might be confusing with setting a default value on a list field.
I'm not really sure why we would need unknown options?
I already made the list command: #6404, however I have no issues implementing your feedback in this command.

[waldekmastykarz]

I'm not really sure why we would need unknown options?

Say we'd allow:

spo list defaultvalue clear --field1 --field2 --field3

Then field1, field2 and field3 must be unknown commands.

An alternative is to require users to run the command 3 times one for each field, with an option like --fieldName <fieldName>

[waldekmastykarz]

That's why I choose this name, so people can easily find it as command. I understand that it might be confusing, what't the difference between a column and a field.

That's a typical inconsistency in the UI, like both webs and site collections being both called sites, that I believe we shouldn't copy.

[milanholemans]

An alternative is to require users to run the command 3 times one for each field, with an option like --fieldName <fieldName>

Personally I would opt for this option. I'm thinking it might become confusing if you are using unknown options.

Could something like this work?

m365 spo defaultvalue clear --webUrl https://contoso.sharepoint.com/sites/Marketing --listTitle "Logos" --fieldName Company

m365 spo defaultvalue clear --webUrl https://contoso.sharepoint.com/sites/Marketing --listTitle "Logos" --folderUrl "/sites/Marketing/Logos/Contoso"

[martinlingstuyl]

So with the first example you are clearing one field default, but with the second example you may be clearing multiple field defaults, depending on the folder value.

Seems logical to me. I'd prefer this to unknowns as well.

[milanholemans]

That's the idea yeah, if you specify only fieldName, we remove the field from all folders. If you only specify folderUrl, we clear all fields from that specific folder.

[Jwaegebaert]

Naming consistency can be such a hassle. I think going with the more generic defaultvalue approach is a solid choice. I'm also a fan of avoiding unknown options. The examples you shared look clear, and I feel this is the best way to go.

[waldekmastykarz]

An alternative is to require users to run the command 3 times one for each field, with an option like --fieldName <fieldName>

Personally I would opt for this option. I'm thinking it might become confusing if you are using unknown options.

Could something like this work?

m365 spo defaultvalue clear --webUrl https://contoso.sharepoint.com/sites/Marketing --listTitle "Logos" --fieldName Company

m365 spo defaultvalue clear --webUrl https://contoso.sharepoint.com/sites/Marketing --listTitle "Logos" --folderUrl "/sites/Marketing/Logos/Contoso"

Good rationale. Let's roll with it.