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.v1.checkout
.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.v1.order
.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.Note: Once you have added at least one user-defined field, you should call List Data Extension Schemas every time a visitor navigates to your UI, to collect and display the user fields.