Hello Team,
I've been testing the store creation using a file this morning and here's some issue I found regarding this processes.
1.1 If the Retail Chain "VTransmit" is set to "SubOne" the stores are being created as SubOne too. It will be nice to have a validation during the finalization of the file import on this specific point.
1.2 Even if we re-select the proper VTransmit, there is no way to recreate the store the right way (HF) because the ID has been used.
1.3 Moreover, we cannot re-activate the store anymore.
1.4 SUGGESTION: add a VTransmit column in the file.
2.1 When importing the file, we need to make sure that the proper system is selected (Insight versus VCloud) even if the file format for those infrastructure is different.
2.2 The system should know the file format and create the store the proper way (Insight or VCloud)
3.1 We need to specify the retail chain name separated by a dot (.). Knowing that the file can only be imported through the retail chain sub-menu, this information could be implicit.
Guest
Hello Team,
We are and will be using more often the spreadsheet files for the store creation in VCloud.
There is two type of store that can be created in V:Cloud and both type of store require specific information in their respective spreadsheet fields
1. Insight store - vcloud_model-stores-creation.xlsx
2. VCloud store - insight_model-stores-creation.xlsx
vcloud_model-stores-creation.xlsx
insight_model-stores-creation.xlsx
With that said, when you drag-and-drop a vcloud file, an Insight store is being created instead. My basic analysis is because the default "installation type" is set to Insight by default.
Even though, since the file have a different structure, th system should be able to automatically create the proper type of store according to it.
A "Nice to have" will be to be able to set the infrastructure type also (HF / Sub1)
And maybe have the same kind of file for the creation/management for users
Thank you,
Hi Emmanuelle, I fully understand that we have limited resource at R&D but making this issue or any other, a reason to not implement solutions/innovations/improvement is slightly awkward.
Hi Alexandre,
Sorry we will not implement this idea for now as we don't have the ressources for it.
I'll let you know if there is a change.
BR,
Emmanuelle
https://ses-esl.atlassian.net/browse/CLA-598