How do I update ETIM data with ETIM BMEcat v. 4 transactions (new version)

Last comment 17/05/2018 18:10 by Karl
· Mark as unread
Karl Erik Jessen 2 years ago created
(Reentering this topic without less-than and greater-than characters around tags, as it seems like the editor removes this kind of tags)

The tag PRODUCT_FEATURES (wherein ETIM classification, and ETIM feature values are delivered) is a part of
the T_NEW_CATALOG, T_UPDATE_PRODUCTS and T_NEW_PRODUCTDATA transactions

But according to ETIM BMEcat guidelines (page 40, 6th line) "In this transaction [the T_UPDATE_PRODUCTS], only the transfer of product data, but not of classification systems is possible."

Does this mean that the PRODUCT_FEATURE tag can not be used in T_UPDATE_PRODUCTS transaction?

If this is actually the case I only se 2 possibilities to UPDATE classifikation data

* EITHER flush all old catalog data and use a T_NEW_CATALOG transaction
* OR flush products individually with a PRODUCT tag with mode=“delete” attribute in a T_UPDATE_PRODUCTS transaction, then send the product with updated classification in a T_NEW_PRODUCTDATA transaction, and then eventually send data that can not be delivered within a T_NEW_PRODUCTDATA tag in a T_UPDATE_PRODUCT transaction

Both seems rather tedious, so in reallity I hope I haven't understood this quite correctly.

--
Karl Erik Jessen
Branchehuset/Vvskataloget DK
Marc Habets 2 years ago created
Dear Karl Erik,

To start with the good news: you can use PRODUCT_FEATURES with the transaction T_UPDATE_PRODUCTS! 

This seems to be a copy/paste issue from the original BMEcat documentation. What they mean here is not exchanging ETIM based product data, but the complete classification system itself! So in the original BMEcat you could add the complete ETIM model as well to the file for a NEW_CATALOG transaction, which of course we don't want. 

I will take care that we correct the documentation for the next version. @karlpappas​ can you confirm my answer is correct? I will also check the issue with <> characters and let you know.
in reply to @marchabets:
Karl Erik Jessen I am so glad I was wrong here :-)
2 years ago

Reply

Karl Pappas late but finally I confirm what Marc explained, everything fine
2 years ago

Reply


show 1 other comment(s)
Marc Habets 2 years ago created
If you put a blank space after the < or > then it works, looks like they generate a special command or something, I will try to find the answer ...
Marc Habets 2 years ago created
I got an answer back from the technical helpdesk that operates the platform. As I assumed it has to do with HTML tags, so for now the only solution is to add a space after the < and before the >. 
in reply to @marchabets:
Karl Erik Jessen Thanks for the tip
2 years ago

Reply

Join the conversation
You have to be a registered user to join the conversation.
Topic started 08 May 2018 at 14:18
Reader count 9
Comment count 7