Document Library Command Bar - Classify and Extract and Automate - unable to hide

[buildbod]

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

Declarative list formatting

Developer environment

None

What browser(s) / client(s) have you tested

• 💥 Internet Explorer
• 💥 Microsoft Edge
• 💥 Google Chrome
• 💥 FireFox
• 💥 Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

Additional environment details

• browser versions
• Microsoft Edge Version 130.0.2849.56 (Official build) (64-bit)
• Google Chrome Version 130.0.6723.92 (Official Build) (64-bit)

Describe the bug / error

The Command Bar Customisation documentation https://learn.microsoft.com/en-us/sharepoint/dev/declarative-customization/view-commandbar-formatting#key lists the Command Bar keys for 'Classify and Extract' and 'Automate' as 'classifyAndExtract' and 'automate' respectively. Setting either or both keys to "hide":true has no effect i.e. the key is not hidden.

In the case of the Automate item. It is possible to setting either 'automateCreateRule' or 'automateManageRules' to be hidden but the subcategory Rules remains e.g.

Steps to reproduce

1. Using the Format view add the following JSON to hide the Classify and extract and Automate options:

{ "$schema": "https://developer.microsoft.com/json-schemas/sp/v2/row-formatting.schema.json", "commandBarProps": { "commands": [ { "key": "classifyAndExtract", "hide": true }, { "key": "automate", "hide": true }, { "key": "automateCreateRule", "hide": true }, { "key": "automateManageRules", "hide": true } ] } }

3. The options will remain visible even though the key is set to hide

Expected behavior

The Classify and extract and Automate commands are hidden.

[buildbod]

With more experimentation, the 'Classify and extract' key can be hidden using viewDocumentUnderstandingModels e.g.

{ "key": "viewDocumentUnderstandingModels", "hide": true }

[tpodugu-ms]

Thank you for reporting this. We will provide an update soon.