Graphql admin API - design settings update error ("branding_settings_not_enabled")

[santoninko]

When I'm trying to call "checkoutBrandingUpsert" mutation on some shops, it throws an error "CheckoutBrandingUpsertUserError", "branding_settings_not_enabled". What does it mean? On some stores it works fine, on others it doesn't. Can't find any reference of "branding_settings_not_enabled" on the internet.

[lizk]

You should verify the store had upgraded to Checkout Extensibility. 

[ClementOutis]

@santoninko Did you find why this error is trigger on some shops ? 

I have the same problems on a brand new dev shop created for test this api.

[santoninko]

Not really 😞

[ClementOutis · Accepted solution]

@santoninko I think I had found why on my side.

I have find that when you query a checkout branding option that you haven't edited yet, you got a null value. But if you try to save this checkout branding option (without changing anything) with the checkoutBrandingUpsert you gonna got this error.

For the API, the null value is not accepted when the field doesn't have been edited previously (if null isn't a possible value for this option).

To avoid this I remove the null values from the result of the CheckoutBranding query.

Like that I can edit the options I want and use the mutation to save them.

If I need to edit new options I add the news ones in my  checkoutBrandingUpsert variables with a good value.

I hope this will help you (if you can understand my bad explanations 🙃)

[santoninko]

Yes, that was it! Thank you.

[ClementOutis]

No problems 😉

Glad it helped!