RELATED IDEAS
Make it more efficient to work with renaming fields for digital Storefronts, when you have a large number of stores
Please, fill in the below fields to enable the processing of your idea.
Who would benefit? |
PIM admin users setting up digital storefronts would benefit from being able to manage the field renaming on a general level that can be applied to several stores. |
What impact would it make? |
This would make it easier to maintain the field names and you would not need make changes in each store when you want to make an update. |
How should it work? |
Make it possible to create field rename templates that can be applied to one or more stores and when changes are made in the template, to change or add a new field renaming, it will be updated in all stores using this template. |
Why is it needed? |
Sometimes the field names that have been setup in the PIM doesn't make sense to use publicly in the digital storefront and you want to use field names that is more suitable in this context. Using field renaming is also a way to control the field names in the export file to get other column headers than the field type id. |
Additional feedback, background or context:
In Brand Store v2 it's now possible to create a Config Template with a configuration that can be reused in many stores that should share the same configuration when it comes to what data types and fields to share. The renaming of fields can also be done as part of the config template and be done in one place that can then be shared in multiple stores, see attachment for more guidance on how this works.
Store config templates can be created either based on an existing store configuration from the Review step in the Store wizard where you can select "Save" next to "Config template" OR you can go to the Templates tab in the Store Admin and start by defining the config template.
To use a config template as the basis of the configuration you select a config template on the Basic step in the Store wizard.