Posted on 30/05/2018 10:33:22
Hi Lars,
answers:
1. Doing it more than once creates duplicates in the Product Fields section of eCommerce, thus we now have alle Custom Fields twice in the list.
That is because in your source xml you have fields defined twice: first time in the <config> section and second time in the <EcomProductField> table section.
2. List field types are lost and have to be revisited. TypeId seems to be in XML, but not used
No the TypeId field is used: check the Dynamicweb database table [EcomProductField], columns: [ProductFieldTypeId], [ProductFieldTypeName]
3. List field select values are not updateded correctly even if we include the appropiate files in the XML (EcomFieldOption).
There seems to be missing a reference in the Config section of the XML
That is not correct. For example consider the twicely imported field "ProductManager", it has two ids in the Dynamicweb database table [EcomProductField]: the one generated from the config section and second provided from the source xml: "FIELD29". So if you browse that field in the Ecom->ProductCatalog->Product fields the first one is from the config section and ineed it has no fields imported, but if you will browse on the next pages and find next "ProductManager" field which was imported from the [EcomProductField] xml it contains the options(db table [EcomFieldOption]):
4. The selected shop for import is not overwriting the shopid found in the XML, thus forcing a find - replace before importing.
I was looking for any available SHOP* id in your source xml field and have not found any, so it is not clear what you mean here. Could you give more details about that?
Regards, Dmitrij