List Formatting: `PromotedState` can no longer be updated via `setValue`

[tecchan1107]

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

No response

Describe the bug / error

Previously, it was possible to update PromotedState using setValue, which allowed converting a news post into a page and vice versa.

However, when testing this now, a update message is displayed, but the value is not actually updated.

Is this a bug, or was there a change in behavior or specification?

Steps to reproduce

1. Display the Promoted State column in Site Pages.
2. Apply the promotedstate-demote-news JSON to the column formatting of the displayed Promoted State column.

Expected behavior

The PromotedState column can be updated using setValue, as it was previously.

[Tanddant]

Noticed this as well! - the batch call that's being made just has an empty array for fieldvalues

[Ashlesha-MSFT]

@tecchan1107,
Thanks for reporting this issue.

I’ve been able to reproduce the behavior you described in SharePoint Online. As you noted, updating the PromotedState column using setValue via declarative list formatting shows an update message, but the value itself is no longer updated.
As This did work previously, so at this point it’s unclear whether this is: an intentional behavior/specification change, or an unintended regression.

I’ll be raising this as a bug and checking with engineering to confirm whether there has been any recent change affecting PromotedState updates.
I’ll follow up once I have clarification from the product team.
Thanks again for flagging this.

[RantingLemming]

Confirming the same. Noting that the $batch endpoint itself still supports updating the field so the issue is entirely what @Tanddant noted - the field name/value are not passed to the array. This seems to be what happens if you try to reference a field that doesn't exist, so expecting something is impacting ability for that field being recognized. Also tried testing it with multiple other (valid) field values to similar effect - the other field values get included in the $batch request but "PromotedState" is not.