This article shares some possible use cases you could support, as well as an example flow that could support each use case. You're certainly not limited to these use cases, but they can be a helpful jumping off point as you plan your implementation.
If your functionality requires access to fields that have been added to an object, you might want to retrieve all of the schemas at once. For example, displaying the returned fields to site visitors.
entityFqdn in most events. The Wix eCommerce Checkout FQDN is wix.ecom.*.checkout.
Note: Use a wildcard (*) in place of the FQDN's version number to ensure your code will continue to work when Wix updates the service object to a newer version.
"ARCHIVED". This ensures that any archived fields are returned and provides a complete schema.Display a site-specific field, such as alcohol by volume (ABV) for whiskey orders, alongside fields from Wix eCommerce Orders, to site visitors.
entityFqdn in most events. The Wix eCommerce Order FQDN is wix.ecom.*.order.
Note: Use a wildcard (*) in place of the FQDN's version number to ensure your code will continue to work when Wix updates the service object to a newer version.
wix.ecom.v1.order FQDN and _user_fields namespace to check if a user-defined schema exists._user_fields namespace, as relevant:
_user_fields namespace schema exists, call Create Data Extension Schema with the wix.ecom.v1.order FQDN, the _user_fields namespace and the new JSON schema._user_fields namespace schema already exists, call Update Data Extension Schema with the wix.ecom.v1.order FQDN, the _user_fields namespace and the updated JSON schema. Make sure to specify the entire schema, as any field not specified will be deleted.Note: Once you've added a user-defined field to the site's schema, you should call the relevant GET call for the target API object - in this case, Get Order - every time a visitor navigates to your UI to collect and display the user fields.