Configurations Mass Export > Templates
Answered
It would be great if the Configuration Mass Export Templates would include the Checkboxes:
Example:
Smith-Export without Item Placement Tool
John-Export with Item Placement Tool
Same for Meta-Data:
Smith-Export without U_TEST
John-Export with U_TEST
-
Thank you for your request. It has been scheduled for review by the development team that will get back to you should there be questions.
(Please note that as we are user-driven we can't guarantee that your request will be met unless it gets many votes and/or fit the product vision)
Read more about the Feature Request process here
[Internal Id: 16768] -
Hi Michael
Thank you for the Suggestion. Could you perhaps tell a bit about the use of this use-case as I struggle to envision how this is beneficial? What is the business scenario?
And what to do if you make a configuration that are linked to both Smith amd John? Should it then export in both cases... Similar what should happen to configs that have no user-settings? They technically also should be included in both exports...
It might just be me that lack the vision of the benefit...
-
Hi Rasmus,
this is an Example for some Use Cases:
(I show this Use Cases only with a few UDF. In reality, I have hundreds of UDF, UDT, Formatted Search, Universal Functions, UDO, Function Buttons, Validations, etc.)
I have ONLY ONE MASTER-DB on my own Development-PC.
To this DB I add EVERY feature (General Features, John's Features, Smith's Features and Zulu's Features).
John sells Flowers
Smith sells Fruits
In 2019 I added some UDF
U_GENERAL-TAX
U_GENERAL-NAME
U_GENERAL-YEAR
U_FLOWER-COLOR
U_FLOWER-WEIGHT
U_FRUIT-COLOR
U_FRUIT-WEIGHT
For John I create an Export-Template with:
U_GENERAL-TAX
U_GENERAL-NAME
U_GENERAL-YEAR
U_FLOWER-COLOR
U_FLOWER-WEIGHT
In 2020 I add in my MASTER-DB:
U_GENERAL-XX
U_GENERAL-YY
I open template JOHN and add
U_GENERAL-XX
U_GENERAL-YY
because JOHN doesn't need the SMITH UDF.
One Day later I get a new Customer Zulu.
Zulu sells Flowers and Computers. So, I add
U_COMPUTER-COLOR
U_ COMPUTER -WEIGHT
to my Master-DB.
Then I open the JOHN-TEMPLATE and make a Copy (to ZULU-Template) and I add
U_COMPUTER-COLOR
U_ COMPUTER -WEIGHT
Now Zulu has all (hundreds) Flower-UDF and Computer-UDF.
Next Use Case (a little different):
I create an "AddOn" called EASY-CONTRACT with CONTRACT-UDT and CONTRACT-UDF.
Smith and Zulu would like to buy the EASY-CONTRACT AddOn.
I open EASY-CONTRACT-TEMPLATE and send ONLY these UDT and UDF to Smith and Zulu.
Both import theses UDT and UDF (and UF and Validation etc.) without deleting the old Configurations (because there could be a special Checkbox).
-
It would be awesome. Great usibility benefit for partners to move some customization packages(like an add-on) to another customer-DB. For example we assign configuration categories to almost each entry. Why should not we have a feature to export based on categories and import to another client without delete existing configurations.
Please sign in to leave a comment.
Comments
4 comments