1b.app
Link copied -

Correctness of import - export of product characteristics from prom

Prom in the unloading has such entities "Name_Characteristics" (for example, volume), "Measurement_Characteristics" (for example, liters or miles of liters) and "Value_Characteristics" (for example, a digital value) . For example, the characteristic Volume-l-1 is unloaded. In Boxing, there is no concept of "characteristic measurement" and it goes into boxing as Volume -1l. When importing back to prom, there is no longer a characteristic measurement field, and prom does not accept this as its own characteristic, but as a custom one, and it turns out Volume 1l. And sometimes duplication occurs and the characteristic is displayed as Volume 5l.l.l.l.l.l.
Original question is available on version: ru

Answers:

Суханіцький Андрій OneBox CORP
OneBox Corp - Інтегратор
Personal license
This functionality already exists.
In the settings of each filter there is a field https://prnt.sc/udafdd where the unit of measure is set.
At the same time, in the product filters, in the filter value, you do not need to specify "l", that is, if the filter value is "5 l", then you just need to set 5
08.09.2020, 01:44
Original comment available on version: ru

Yes, I see that this field is unloaded, but we don’t create characteristics in the box, but import them from a promo XML file, it has a value (if I’m not mistaken, “unit”), but box, as I understand it, does not see it and this field imports something into the characteristic (Volume ( L) / 5 or V Value Volume / 5L
08.09.2020, 11:36
Original comment available on version: ru

Суханіцький Андрій OneBox CORP
OneBox Corp - Інтегратор
Personal license

Zubarev Sergey
Client wrote:
Yes, I see that this field is unloaded, but we don’t create characteristics in the box, but import them from a promo XML file, it has a value (if I’m not mistaken, “unit”), but box, as I understand it, does not see it and this field imports something into the characteristic (Volume ( L) / 5 or V Value Volume / 5L

The bottom line is that you need to specify the unit of measurement once for each characteristic and then load.
If you have a characteristic value of "5" in your XML file, then 5 will be loaded and, when unloaded, it will unload "Measurement_Characteristics" to it.
If in your file the value is uploaded as "5 l", then you can configure the action when saving the product card, which will change the filter value simply to "5"
08.09.2020, 11:47
Original comment available on version: ru

No, I'm not talking about that, I'm talking about importing, this is how the characteristic looks like in the prom https://skr.sh/s43ZIOmwXKj? and this is how it enters the box after importing https://skr.sh/s43wHdOp4Lg
08.09.2020, 19:08
Original comment available on version: ru

Суханіцький Андрій OneBox CORP
OneBox Corp - Інтегратор
Personal license

Zubarev Sergey
Client wrote:
No, I'm not talking about that, I'm talking about importing, this is how the characteristic looks like in the prom https://skr.sh/s43ZIOmwXKj? and this is how it enters the box after importing https://skr.sh/s43wHdOp4Lg

As far as I understand, you use this action https://prnt.sc/uduzii
Now your characteristics are unloaded without the unit parameter https://prnt.sc/udvfaq
How to unload this parameter via xls I wrote above.
For now, to resolve the issue, you can:
1) Set the unit of measurement for filters (as described above)
2) In order to correct the position of the goods in the box and upload to the site - you need to set up an action in product automation like this https://prnt.sc/udvioq
And then for such values https://prnt.sc/udvj3q will change to such https://prnt.sc/udvjpl
Then you need to update all products - this will work for you when loading products with samples and should correct all filters.
After that, the goods are uploaded to the site with the correct values.
That is how your situation is resolved.
08.09.2020, 23:17
Original comment available on version: ru

It's hard to call it a solution, I have several dozens of such characteristics and do I need to create actions for each? I already have 20 of them, besides, the next time I import the situation will repeat itself and this eternal treatment will not solve this problem once and for all, moreover, there are absolutely the same characteristics, for example, Volume (l) and Volume (ml) in boxing characteristics, this is absolutely the same characteristics and guess which of them (l) and which (ml)? Wouldn't it be easier to make a tick for each characteristic - only a numeric value, so that even if some literal data enters this field, it would automatically be cleared and only the numeric value would be recorded.
09.09.2020, 15:01
Original comment available on version: ru

Суханіцький Андрій OneBox CORP
OneBox Corp - Інтегратор
Personal license

Zubarev Sergey
Client wrote:
It's hard to call it a solution, I have several dozens of such characteristics and do I need to create actions for each? I already have 20 of them, besides, the next time I import the situation will repeat itself and this eternal treatment will not solve this problem once and for all, moreover, there are absolutely the same characteristics, for example, Volume (l) and Volume (ml) in boxing characteristics, this is absolutely the same characteristics and guess which of them (l) and which (ml)? Wouldn't it be easier to make a tick for each characteristic - only a numeric value, so that even if some literal data enters this field, it would automatically be cleared and only the numeric value would be recorded.

You do not have units of measurement in the prom, so they are unloaded, it is logical that now you need to correct what happened in the end. To avoid such a problem, you need to initially think over the algorithm for working with products. As for the fact that the values will be overwritten when imported from the prom - yes. But since the actions will be configured, they must again change the values to the correct ones. You can make a revision, I think that it will not take more than 2 hours. Or you can wait.
I described the solution to the current problem, it's a long time, but you only need to do it once, then it will work fine, do it or not, think for yourself, there is a solution.
09.09.2020, 15:33
Original comment available on version: ru

not quite so, in the prom all the units of measurement were initially spelled out correctly, but when importing from the box, the prom could not understand these values and the prom did not create portal ones (with prescribed units), but user characteristics that naturally do not have units, if you can make a revision so that when exporting from XML, the characteristics, units and values fall into place, then consider this revision
09.09.2020, 16:06
Original comment available on version: ru

Give an answer for improvement.
11.09.2020, 10:51
Original comment available on version: ru

Please join the conversation. If you have something to say - please write a comment. You will need a mobile phone and an SMS code for identification to enter. Log in and comment