Explain the structure of the directory "Values of filters of categories Socket" (because there are disagreements with the logic in the socket cabinet)
The system has a directory "Rozetka filter values" that works on the basis of automation "Rozetka category filter values"
And here there is a certain conflict with the outlet
The essence of the conflict is that, for example, there is a category Socket = 4636407
In OneBox there is a directory "Filters of categories Socket"
If you filter all the filters that are available for this category (4636407)
So there is a filter with the code = 249703 (Print)
If you filter all the values in the Rozetka category filter values by this filter code, there will be approximately 41 values
That is, the structure is quite clear, there is a category (1), the category has filters (2), the filters have values (3).
But the problem is that on the outlet, if you download the directory from the office, it becomes clear that different filter values are used for different categories, that is, it is not so simple that all 41 values are used for any category where there is a "Print" filter, for example, for category 4636407 (T-shirts for boys) for the value "Print" you can transfer only 6 values:
4140073 Inscription
4140078 Strip
4140083 Drawing
4140128 Plain
4140288 Ukrainian symbols
4222045 Dinosaurs
And for category 4636383 (Polo for boys), you can already transfer 18 values:
4222024 New Year
4222027 Zigzag
4222030 Diamonds
4222033 Lips
4222036 Avocado
4222042 Butterflies
4222045 Dinosaurs
4222051 Unicorns
4222054 Fruits and vegetables
4222063 Cats
4222066 Birds
4222072 Snowflakes
4222075 Zebras
4222078 Rabbit
4222081 Panda
4222084 Owls
4222087 Sheep
4222090 Anime
And here several questions arise:
1. What is the basic logic of using Rosek's guides in the system (that is, how was everything conceived during development)?
2. How can you make it so that the system shows 6 values for category 4636407, and 18 values for 4636383, i.e. as it is displayed in the socket cabinet (it seems that the directory lacks some field that could be additionally filtered, or maybe it is necessary to make some 4 directory that will build a connection between these directories)?
Original question is available on version: ua
And here there is a certain conflict with the outlet
The essence of the conflict is that, for example, there is a category Socket = 4636407
In OneBox there is a directory "Filters of categories Socket"
If you filter all the filters that are available for this category (4636407)
So there is a filter with the code = 249703 (Print)
If you filter all the values in the Rozetka category filter values by this filter code, there will be approximately 41 values
That is, the structure is quite clear, there is a category (1), the category has filters (2), the filters have values (3).
But the problem is that on the outlet, if you download the directory from the office, it becomes clear that different filter values are used for different categories, that is, it is not so simple that all 41 values are used for any category where there is a "Print" filter, for example, for category 4636407 (T-shirts for boys) for the value "Print" you can transfer only 6 values:
4140073 Inscription
4140078 Strip
4140083 Drawing
4140128 Plain
4140288 Ukrainian symbols
4222045 Dinosaurs
And for category 4636383 (Polo for boys), you can already transfer 18 values:
4222024 New Year
4222027 Zigzag
4222030 Diamonds
4222033 Lips
4222036 Avocado
4222042 Butterflies
4222045 Dinosaurs
4222051 Unicorns
4222054 Fruits and vegetables
4222063 Cats
4222066 Birds
4222072 Snowflakes
4222075 Zebras
4222078 Rabbit
4222081 Panda
4222084 Owls
4222087 Sheep
4222090 Anime
And here several questions arise:
1. What is the basic logic of using Rosek's guides in the system (that is, how was everything conceived during development)?
2. How can you make it so that the system shows 6 values for category 4636407, and 18 values for 4636383, i.e. as it is displayed in the socket cabinet (it seems that the directory lacks some field that could be additionally filtered, or maybe it is necessary to make some 4 directory that will build a connection between these directories)?
Answers:
Good day.
Yulia wrote:
1. What is the basic logic of using Rosek's guides in the system (that is, how was everything conceived during development)?
The outlet issues 2 directories according to your accesses:
- categories
- category options
We import them as is into 3 separate directories - categories, filters, filter values.
Yulia wrote:
2. How can you make it so that the system shows 6 values for category 4636407, and 18 values for 4636383, i.e. as it is displayed in the socket cabinet (it seems that the directory lacks some field that could be additionally filtered, or maybe it is necessary to make some 4 directory that will build a connection between these directories)?
Click I do not see a simple possibility in the implementation of this issue.
As I understand it, you need to import the 3rd directory (value of options) with a specific binding to a category (and not only a filter) - this is possible in the implementation, but you need to change the entire logic of actions (automations) and blocks in the system to work correctly with the new structure directory
That is, I will give you 2 ratings:
1. make a new version of directory automation to import a directory of filter values with binding to a category - 2 hours
2. modification of actions and blocks in the system that work with these directories under the new structure (in the form of settings) - 6 hours
That is, the version of finalizing the directories and logic of all interconnected actions/blocks will take 8 hours.
Yulia wrote:
1. What is the basic logic of using Rosek's guides in the system (that is, how was everything conceived during development)?
The outlet issues 2 directories according to your accesses:
- categories
- category options
We import them as is into 3 separate directories - categories, filters, filter values.
Yulia wrote:
2. How can you make it so that the system shows 6 values for category 4636407, and 18 values for 4636383, i.e. as it is displayed in the socket cabinet (it seems that the directory lacks some field that could be additionally filtered, or maybe it is necessary to make some 4 directory that will build a connection between these directories)?
Click I do not see a simple possibility in the implementation of this issue.
As I understand it, you need to import the 3rd directory (value of options) with a specific binding to a category (and not only a filter) - this is possible in the implementation, but you need to change the entire logic of actions (automations) and blocks in the system to work correctly with the new structure directory
That is, I will give you 2 ratings:
1. make a new version of directory automation to import a directory of filter values with binding to a category - 2 hours
2. modification of actions and blocks in the system that work with these directories under the new structure (in the form of settings) - 6 hours
That is, the version of finalizing the directories and logic of all interconnected actions/blocks will take 8 hours.
25.05.2023, 10:15
Original comment available on version: ua
Maksym Vadimovych Tyndyk
OneBox production wrote:
We import them as is into 3 separate directories - categories, filters, filter values.
1. Where can I read or where is the information on how and where to use these 3 guides (so that everything works correctly)?
Maksym Vadimovych Tyndyk
OneBox production wrote:
I understand that you need to import the 3rd reference (option value) with a specific binding to the category (not just the filter)
2. It turns out that if this is implemented, there will be a directory that will contain the fields Category ID + Filter ID + filter value, that is, something similar to the files attached above (those files that can be downloaded from the socket cabinet)?
3. In theory, this will be a fairly large directory, because there are approximately 7,000 categories, if there are 20 filters in each and 20 values in each filter, then this results in a table with approximately 2,800,000 entries (7,000*20*20), this is a normal table for system work?
25.05.2023, 16:26
Original comment available on version: ua
Yulia wrote:
1. Where can I read or where is the information on how and where to use these 3 guides (so that everything works correctly)?
Try searching the forum for topics related to the Socket.
In short:
- an additional product field is created, which is connected to the directory of Sockets categories
- product automation populates filters in the product based on the selected category in the product
- it is also possible to fill in a separate block of the interface according to the filters of the Outlet in the product and upload them to the Outlet by automation
Yulia wrote:
2. It turns out that if this is implemented, there will be a directory that will contain the fields Category ID + Filter ID + filter value, that is, something similar to the files attached above (those files that can be downloaded from the socket cabinet)?
You will not only have a directory with a filter+value pair, but also a link to a category (category + filter + value).
That is, if the filter value 1 is used for X categories - there will be X entries in the directory.
Yulia wrote:
3. In theory, this will be a fairly large directory, because there are approximately 7,000 categories, if there are 20 filters in each and 20 values in each filter, then this turns out to be a table with approximately 2,800,000 entries (7,000*20*20), this is a normal table for system work?
In theory, yes, it will be a much larger directory, since 1 value of 1 filter can be used in several categories (if not dozens of categories). Probably for this reason, the guides are made more simplified.
A table of several million records in the database is a relatively normal table for correct operation in the system.
25.05.2023, 16:34
Original comment available on version: ua
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
Copyright © OneBox 2024
