Release notes

If this option is allowed by a platform owner, providers can now add dynamic fields to their supply instance.

Dynamic fields (sometimes referred as “specific fields”) are the fields providers decided to add during the runtime, and they are not defined by the platform owner.
Example: On a t-shirt marketplace, the platform owner allows shirts to have a name, a size, and a color and allows providers to add additional info about the product.
Supply fields defined by a platform owner (in this case name, size, and color) are static fields – the platform owner can see those are in their supply type and each t-shirt presented on the marketplace will have those fields.
On the other hand, a dynamic field is a field that a provider adds when adding/editing one or more of their products. In our example, a provider X decides to add a field showing how heavy the tshirts are (now their tshirts have a name, size, color and weight), whereas a provider Y wants to have the sleeve size (their tshirts have a name, size, color and sleeve size) and a third provider Z doesn’t want any additional fields, so their tshirts fields remain name, size and color.

As dynamic fields are so supply-specific that participants cannot filter supplies by dynamic fields when searching and going through them. To get the maximum flexibility out of the dynamic fields and impose the least amount of restrictions, their input type can only be text.

Dynamic fields come with is_variant_identifier and is_variant_specific attributes, meaning that dynamic fields can also create and define product variants.

This feature is followed by some nice backoffice and import updates. Within the backoffice supply details page, you have now a special section with dynamic fields, making them easier to differentiate from the static ones. Additionally, our data import functionality has been enhanced to fully support the importing of supplies with dynamic fields.