An org-setting write that the API accepts and the studio may not honour

iscustomcontrolsincanvasappsenabled is the org setting that lets a custom page use a code component. You can write it through the Dataverse API. The write succeeds, and reading the column back returns the value you wrote. Whether the thing that consumes the setting changes behaviour is a separate question, and we do not yet have the answer.

Why we do not have it

Our first observation was that Power Apps Studio did not reflect an API write. That observation was worth nothing, three times over:

• API writes were interleaved with a person toggling the same setting in the admin centre, so no run had one cause.
• No propagation window was defined or waited out. The studio reads feature state from a config service that caches it.
• We were watching the wrong thing. We looked for "Get more components" at the bottom of the Insert flyout, which does not exist in that build, so the outcome was never observable at all.

The setting did work once it was On, so the path is not dead.

The part worth taking

Reading a column back is the write echoing, not the consumer honouring. If you want to know whether a platform setting took effect, name the observable thing first. Here it is the Import components panel, Code tab, reached by the folder-and-magnifier icon in the custom page studio, and nothing else.

The controlled test is written down: set it Off through the API, confirm the component leaves that panel, set it On through the API only, then check the panel at five, fifteen, thirty and sixty minutes. If it comes back, the write works and lags. If it never does, the admin centre writes a different store and is the authority. We will publish which when it runs.