WEBVTT Kind: captions Language: en-US 00:00:10.440 --> 00:00:16.040 Hello, this is Franck from Sitolog. Today we're going to talk about Merlin's characteristics. So, 00:00:16.040 --> 00:00:21.640 there's quite a bit to show you. The first thing is going to be how to 00:00:21.640 --> 00:00:26.000 display product characteristics in the top table, in the product table. Then, 00:00:26.000 --> 00:00:34.160 I'm going to show you how to filter them. Then we're going to look at the characteristics tab here. 00:00:34.160 --> 00:00:38.760 Uh, in this tab, I'm going to show you how to associate and modify product characteristics 00:00:38.760 --> 00:00:44.240 for several products at once. For example, we'll also see at the bottom how to create 00:00:44.240 --> 00:00:49.360 characteristics. We'll also see how to duplicate characteristic values ​​between 00:00:49.360 --> 00:00:55.360 different characteristics. Quite an interesting feature. We'll also see, always from 00:00:55.360 --> 00:01:01.080 this tab here, how to filter products at the top based on characteristic values, what 00:01:01.080 --> 00:01:08.040 we call ascending filters. And finally, at the end, a quick overview of the 00:01:08.040 --> 00:01:13.360 import tool, which also allows you to create or modify characteristic values ​​in 00:01:13.360 --> 00:01:17.920 products. So how do you import characteristics? So first part, 00:01:17.920 --> 00:01:22.880 we're going to start by displaying the characteristics in the product table up there. So I'm going 00:01:22.880 --> 00:01:27.400 to right-click on this bar to save a little space. I don't know if this is a little 00:01:27.400 --> 00:01:33.200 technique you already know. And then, uh, to view the characteristics, 00:01:33.200 --> 00:01:37.920 we're simply going to configure the columns of this table. So for that, I remind you, 00:01:37.920 --> 00:01:43.920 you click on column, you go to the right tab, eh, product characteristic and 00:01:43.920 --> 00:01:49.800 so on. So what concerns us is the product table and you go all the way down. 00:01:50.680 --> 00:01:57.240 Here, you have a section called one column per characteristic. So you drag it 00:01:57.240 --> 00:02:04.200 to the right. So, a little reminder, the columns that we place here in the configuration, we 00:02:04.200 --> 00:02:10.560 can move them, eh, reorder them, we can keep them but deactivate them. This allows 00:02:10.560 --> 00:02:16.000 us to say, we don't display this or that value, this or that column while keeping uh in 00:02:16.000 --> 00:02:23.480 our setting. Uh, we can also change their width from a numerical point of view. And finally, 00:02:23.480 --> 00:02:27.800 we can change their title, eh. For example, the supplier reference column, I can very 00:02:27.800 --> 00:02:35.520 well name it, uh, something else, reference of my suppliers, for example. There you go, something 00:02:35.520 --> 00:02:40.720 like that. Okay, that was just a little reminder because we often ask the same question. So, 00:02:40.720 --> 00:02:45.400 I added a column per characteristic which is here. Another little note. You see that 00:02:45.400 --> 00:02:52.760 it is marked with 3 minuses in red here. That means that it is a section that will 00:02:52.760 --> 00:02:58.840 significantly slow down the display. So, there aren't many sections of this type. Uh, 00:02:58.840 --> 00:03:02.680 in the list, there must be three or four. I'm not even sure I can find them. There you go, we have some 00:03:02.680 --> 00:03:06.520 here, we have some that concern the photos and then maybe some that concern 00:03:06.520 --> 00:03:12.240 the variations, sorry, here. There you go. And then finally the characteristics. So that 00:03:12.240 --> 00:03:15.440 slows down the display quite significantly simply because it 00:03:15.440 --> 00:03:20.120 greatly complicates the read requests at the server level and some servers may have 00:03:20.120 --> 00:03:24.760 difficulty producing the requested results. Okay, however, it doesn't crash anything, 00:03:24.760 --> 00:03:31.240 it just might slow down your workflow a little. So I'm validating this configuration. 00:03:33.240 --> 00:03:37.960 So, it's refreshing. Before commenting on the display, just to 00:03:37.960 --> 00:03:41.600 point out that I advise you not to do exactly what I just did, 00:03:41.600 --> 00:03:45.520 that is to say, modify your current configuration, but rather to create a 00:03:45.520 --> 00:03:52.320 configuration specific to this type of work. So you call characteristics for example, 00:03:52.320 --> 00:03:56.160 eh. You see, I do it to modify my prices for my texts and various things, the 00:03:56.160 --> 00:04:00.480 stocks. And then the same when I go to work on the characteristics, I create a 00:04:00.480 --> 00:04:06.400 characteristic configuration which also normally contains this section. Okay, apparently I removed it, 00:04:06.400 --> 00:04:10.720 so I'm going to add it again. This allows me to show you the technique again. I click on column. I 00:04:10.720 --> 00:04:15.760 go to the bottom of the list in the product tab. I take one column per characteristic, 00:04:15.760 --> 00:04:23.520 I drag it and I validate. There you go. So what Merlin does after that is that it refreshes 00:04:23.520 --> 00:04:30.800 the display of my products. So of course according to my category selection here. So 00:04:30.800 --> 00:04:34.720 currently, I'm asking it for all the women's products in recursive mode, that is to say women 00:04:34.720 --> 00:04:42.560 and subcategories of women. So it displayed all these products to me according to the fact that they 00:04:42.560 --> 00:04:46.680 belong to the category or categories that I selected. So a filtering by 00:04:46.680 --> 00:04:51.760 category by default. And then above all, I end up with three new columns here which 00:04:51.760 --> 00:04:56.440 correspond to the different characteristics of my different displayed products. 00:04:57.000 --> 00:05:02.280 So here, it's a dynamic display. So the number of columns that you will have 00:05:02.280 --> 00:05:08.920 here depends on your database, depends on your products. If I didn't have any products in 00:05:08.920 --> 00:05:14.160 my list here which contained a value of the composition characteristic, at that point, 00:05:14.160 --> 00:05:18.800 this column would not have been displayed. So if you select absolutely all the products 00:05:18.800 --> 00:05:24.480 in your database, you will end up here with as many columns as there are characteristics 00:05:24.480 --> 00:05:29.000 associated with at least one product. So in some cases we may find ourselves with a very large 00:05:29.000 --> 00:05:35.760 number of columns. So what is important to mention right away is that these columns 00:05:35.760 --> 00:05:41.600 here in this table are not editable. I cannot modify the word viscose. I cannot 00:05:41.600 --> 00:05:45.760 delete it. I cannot replace a characteristic value. I also cannot 00:05:45.760 --> 00:05:51.040 add a column of characteristics not yet associated. This is purely for display, it is 00:05:51.040 --> 00:05:57.680 information. So what is the point of having this information here? There are at least two. 00:05:57.680 --> 00:06:06.960 For example, you can sort, so not sort but yes classify or sort according to a composition, finally 00:06:06.960 --> 00:06:14.400 according to one characteristic or another or two with a click control. You can also 00:06:14.400 --> 00:06:19.960 create column filters. For example, here, I right-click, I click on 00:06:19.960 --> 00:06:26.760 filter on this column. I will ask it contains or equal to cotton. I validate. I only have 00:06:26.760 --> 00:06:32.760 products that contain cotton. So this is often quite useful for making a 00:06:32.760 --> 00:06:36.640 quick selection of products based on certain characteristic values. Later, I 00:06:36.640 --> 00:06:41.640 'll show you something else, an even more advanced method, I would say more practical for filtering 00:06:41.640 --> 00:06:45.640 products based on characteristic values. This is called ascending filters. 00:06:45.640 --> 00:06:51.240 So we'll see that later in the video. The second reason why it can be 00:06:51.240 --> 00:06:57.120 interesting to display the characteristics is mainly for exporting the data. 00:06:57.120 --> 00:07:02.040 If you need to export to a marketplace that asks you for the characteristics, 00:07:02.040 --> 00:07:08.440 well, you'll display them like this. Then, select your lines, do a group action, 00:07:08.440 --> 00:07:15.640 click on export. You choose what you want to export. So in this case, for 00:07:15.640 --> 00:07:20.280 us, it's just the product table. So I'm just going to take the products and you export 00:07:20.280 --> 00:07:25.640 with the parameters you want. So there are two main types of export. There's 00:07:25.640 --> 00:07:31.320 this one. So when we choose the first two options here, which provides a file that is perfectly 00:07:31.320 --> 00:07:37.400 suited to reimporting into a Prestashop database, either the same one 00:07:37.400 --> 00:07:42.000 or another, possibly even in another version of Prestashop. Merlin will be 00:07:42.000 --> 00:07:48.440 able, thanks to these columns here, to reimport the characteristics, recreate them, recreate their 00:07:48.440 --> 00:07:52.800 values, and automatically reassociate them with the products in a single operation. 00:07:53.640 --> 00:08:00.640 And then the second format, this one at this point, creates a file exactly as it is 00:08:00.640 --> 00:08:06.480 displayed here. So it's not intended for reimporting into Prestashop, it's more intended 00:08:06.480 --> 00:08:11.320 for marketplaces or other tools for which you need a format 00:08:11.320 --> 00:08:15.640 identical to what you have up there. So the second part, the characteristics tab. So I 00:08:15.640 --> 00:08:20.760 'm going to restore the interface. I right-click again on this bar to bring up the 00:08:20.760 --> 00:08:26.080 bottom part, and I'm also going to delete my thread that I have here. So I go to this column, click 00:08:26.080 --> 00:08:33.480 Right and delete the thread from this column. Good. So in this tab, you have two parts. 00:08:33.480 --> 00:08:41.080 In the top part, we will be able to display, visualize sometimes in a certain way modify 00:08:41.080 --> 00:08:45.320 the characteristic values ​​associated with the products that are selected above. 00:08:46.160 --> 00:08:52.320 And then in the bottom part, we will be able to visualize all the existing characteristics 00:08:52.320 --> 00:08:57.040 in the database as well as their values. Create new characteristics and new 00:08:57.040 --> 00:09:03.400 values. Also duplicate characteristic values ​​from one characteristic to another. 00:09:03.400 --> 00:09:08.680 So let's see that. So I'm going to reduce the bottom part to have a little more space 00:09:08.680 --> 00:09:13.320 here so that it's more understandable. So I'm going to start by selecting several products at the 00:09:13.320 --> 00:09:17.080 top. Voz, we're going to take all the products there that are displayed and I'm going to click on 00:09:17.080 --> 00:09:23.440 display. So, what the program does is that for each of these products up there, it 00:09:23.440 --> 00:09:29.520 went to get the value of the characteristics already associated that we find here. So there, 00:09:29.520 --> 00:09:34.520 we have the product numbers, characteristic numbers, the name of the characteristic, 00:09:34.520 --> 00:09:40.040 the ID of the characteristic and its value. We can perhaps rebalance 00:09:40.040 --> 00:09:45.480 the display a little. This also allows me to show you that here in all the tables, 00:09:45.480 --> 00:09:51.200 you have what is called the table menu. I don't know if I've already talked about it. And you have 00:09:51.200 --> 00:09:57.920 a function here for automatically adjusting the column width. Another little tip, 00:09:57.920 --> 00:10:02.040 here it's not very clear because I no longer have what we call the separators 00:10:02.040 --> 00:10:06.760 or the breaks. I'm going to recreate the breaks. So the breaks are brown or beige lines 00:10:06.760 --> 00:10:12.040 that actually group the values ​​of the common values, so the product lines. 00:10:12.600 --> 00:10:18.960 Look, I do it in ID product. Here, I right-click, I'm going to add a break 00:10:18.960 --> 00:10:26.720 on this column. And automatically, you see, my lines are grouped by set of, how to 00:10:26.720 --> 00:10:33.280 say, products, eh, by product. So here in PR3, I have all the properties of product 3 here 00:10:33.280 --> 00:10:41.600 all the properties of product 2. So here you have, uh, the values ​​associated with product 00:10:41.600 --> 00:10:49.880 2 for example. So product 2, it's this one, it's the blouse. So that's information. 00:10:49.880 --> 00:10:55.560 You can also modify this information, that is to say for example if I modify 00:10:55.560 --> 00:11:03.640 the cotton composition here to something else, well you click there on the word cotton and it opens you, 00:11:03.640 --> 00:11:10.720 uh, the selector eh. So you can either choose an existing standard value from 00:11:10.720 --> 00:11:17.560 the list like viscuse, or I'm going to do it here for short sleeve, uh here in the bottom part, 00:11:17.560 --> 00:11:23.760 create what we call a custom value. So a custom value, I'm going to call it 00:11:23.760 --> 00:11:28.920 perso 1. A custom value is a characteristic value that cannot be 00:11:28.920 --> 00:11:35.520 used by another product. So it's a unique value. In which case should we use 00:11:35.520 --> 00:11:38.640 standard values ​​and in which case should we use custom values? So that 00:11:38.640 --> 00:11:43.000 's a Prestashop or e-commerce problem. It's not entirely specific to Merlin, but I 00:11:43.000 --> 00:11:49.760 'll explain it anyway. A standard value like short sleeve or all those that are there. 00:11:50.480 --> 00:11:57.720 If at some point you modify the name, the value, at that point, the 00:11:57.720 --> 00:12:04.480 modified value will apply to all the products that are associated with that value. So on the one hand, 00:12:04.480 --> 00:12:10.720 it's practical. But on the other hand, perhaps if your values ​​are, for example, 00:12:10.720 --> 00:12:15.280 lengths or dimensions, and at some point you want to modify this value because the 00:12:15.280 --> 00:12:19.800 dimension of the product changes, at that point it's better to choose a custom value because 00:12:19.800 --> 00:12:25.320 you don't necessarily want to impact the dimension of the other products as well. There you go. So 00:12:25.320 --> 00:12:28.880 the choice between a standard value and a custom value is up to you. It's 00:12:28.880 --> 00:12:35.440 not a rule, a golden rule. So here I chose a custom value. I validate. 00:12:37.800 --> 00:12:43.040 And I find myself here with my property now custom 1. And see a little information 00:12:43.040 --> 00:12:47.960 in the custom column, I have a checkbox in French 00:12:47.960 --> 00:12:53.800 that tells me it's a custom value. So as you can see, this table 00:12:53.800 --> 00:13:01.120 Here, it displays the characteristics, allows me to modify them one by one, to define whether they are 00:13:01.120 --> 00:13:07.840 custom values ​​or not, and then finally, it also allows me to unassociate them, basically to delete them. 00:13:08.400 --> 00:13:13.240 So, for example, if I want to remove my custom value here, this property, 00:13:13.240 --> 00:13:19.520 and also the composition of this product, well, I select both and I click 00:13:19.520 --> 00:13:26.520 on unassociate. It asks for confirmation before deleting. I delete. There you go. 00:13:26.520 --> 00:13:31.400 So both products have lost these two characteristics. 00:13:31.400 --> 00:13:37.000 Just a quick note, when you modify characteristic values ​​in this table, 00:13:37.000 --> 00:13:43.480 you can notice that here in the top left, the refresh button flashes. So this is the 00:13:43.480 --> 00:13:48.120 case when you actually have the characteristic columns included in your 00:13:48.120 --> 00:13:52.760 display, as was the case earlier, what I showed you first, in fact. 00:13:52.760 --> 00:13:57.400 So the refresh button here tells you that the data displayed in this table is not 00:13:57.400 --> 00:14:02.440 necessarily synchronous with the data in the database. So the data in the database has been 00:14:02.440 --> 00:14:08.240 modified via the middle table here. But to save time, Merlin doesn't 00:14:08.240 --> 00:14:13.240 automatically refresh the data up there synchronously. It would slow down the application too much. So it's up to 00:14:13.240 --> 00:14:17.400 you at some point if you want to because you need the information that's there 00:14:17.400 --> 00:14:21.840 to export it or whatever. At that point, you have to click on the refresh button like I'm 00:14:21.840 --> 00:14:27.040 doing now. to refresh the data at the top and therefore have it synchronous with the table 00:14:27.040 --> 00:14:35.400 below. There you go. So I'm going to reselect everything again to refill my table. 00:14:36.840 --> 00:14:42.480 So, another note, you don't have in this table apart from the unlink button here, 00:14:42.480 --> 00:14:48.920 so mass deletion, you don't have a mass copy or 00:14:48.920 --> 00:14:53.520 multi-line modification function as is the case on the products table for example or practically all the 00:14:53.520 --> 00:14:59.200 other tables. We'll see in a moment that all multi-line modifications are made 00:14:59.200 --> 00:15:04.600 from finally the tables at the bottom here and the button here which is currently grayed out which is called 00:15:04.600 --> 00:15:08.760 associate value. So we'll see that in a moment, but I'll show you anyway, so we'll 00:15:08.760 --> 00:15:14.800 expand a little. You have functions for filtering or sorting, etc. You can copy 00:15:14.800 --> 00:15:18.520 values, but you don't have the two bottom lines, you know, which allow you to copy a 00:15:18.520 --> 00:15:23.400 line into a selection of other lines. So we don't work that way on this table. 00:15:25.400 --> 00:15:29.320 So the mass processing is done from the bottom part here of the 00:15:29.320 --> 00:15:34.640 characteristics tab. So the first operation is to display the characteristics present 00:15:34.640 --> 00:15:41.680 in the database. So by clicking on the little button here, eye or display. There you go. So all 00:15:41.680 --> 00:15:46.920 the existing characteristics are listed. If I select one that contains values, 00:15:46.920 --> 00:15:54.320 they are listed. Here, I have secondary tables here that give me the translations 00:15:54.320 --> 00:16:01.040 into the different languages ​​present in the database. Here also the translations of the values 00:16:01.040 --> 00:16:07.400 ​​of the different characteristics, and finally, on the right, a tab to define custom values 00:16:07.400 --> 00:16:13.320 . We saw earlier, we created one. We can also create them here. So, 00:16:13.320 --> 00:16:17.720 I was saying this part at the bottom here will allow me to make mass modifications, 00:16:17.720 --> 00:16:22.680 that is to say to change the characteristics of the products selected above. So for that, 00:16:22.680 --> 00:16:29.840 you just have to choose one or more different characteristics 00:16:29.840 --> 00:16:37.760 with a control. So here my different values ​​are displayed. So that's practical 00:16:37.760 --> 00:16:41.800 too. I'm going to put back here a break that is normally present by default that I 00:16:41.800 --> 00:16:47.840 had to delete. So I'm adding a break so that I find here a grouping 00:16:47.840 --> 00:16:53.920 by characteristic. So I first have the compositions at the top then the styles at the bottom. 00:16:54.680 --> 00:17:03.120 Well look, I'm going to choose a composition and I'm going to choose with a control a style 00:17:03.120 --> 00:17:09.720 a military style. There you go. So I have two values ​​that are selected here. I have 00:17:09.720 --> 00:17:14.680 x products selected up there. So I might not do it on all of them. We're going to simplify 00:17:14.680 --> 00:17:20.560 a little. We'll leave it like that. We'll do it on all of them. So I have all my products selected, 00:17:20.560 --> 00:17:26.000 my values ​​selected. All I have to do is click here on the associate value button. So 00:17:26.000 --> 00:17:30.640 that associates the values ​​at the bottom with the product selected at the top and so it will update 00:17:30.640 --> 00:17:35.880 the table here in the center. I click. There you go, it performs the operation. It's finished. It did 00:17:35.880 --> 00:17:45.360 n't even take a second. And you see, I have the military style that has been added everywhere 00:17:45.360 --> 00:17:52.760 and also my composition which has become either. So there was a replacement of the 00:17:52.760 --> 00:17:56.400 composition value because all the products already had a composition and from memory 00:17:56.400 --> 00:17:59.640 the products didn't yet have a style and now they have a 00:17:59.640 --> 00:18:06.240 style characteristic which is military. So if I modified a value, for example the style, I made a mistake, 00:18:06.240 --> 00:18:09.880 I didn't want the military but I wanted the rock, it's just as simple. I select 00:18:09.880 --> 00:18:14.720 my rock value and I click again on associate value and automatically all the products 00:18:14.720 --> 00:18:22.920 change to rock value in rock property in the style characteristic. To delete a 00:18:22.920 --> 00:18:27.760 property, again, I showed you earlier, you click here in the 00:18:27.760 --> 00:18:32.040 middle table and ungroup. So, if you want to save time, for example, to avoid 00:18:32.040 --> 00:18:35.960 selecting all the styles, if I wanted to delete all the styles for all these products, 00:18:35.960 --> 00:18:42.240 I would use a filter. I would right-click here on the word style. Filtered on this column 00:18:42.240 --> 00:18:48.480 equals style. I validate. I could also have done it on the value by the way. 00:18:48.480 --> 00:18:54.160 Uh, so filter only the rocks. There, I have my thread which was which has, sorry. So I have 00:18:54.160 --> 00:18:59.200 all the styles. I select all the rows with the button and I ungroup. 00:19:01.160 --> 00:19:06.960 I delete. So there, I have, uh, apparently all my rows which have disappeared but in fact 00:19:06.960 --> 00:19:10.760 only the styles. Why don't the other rows appear? Simply because I 00:19:10.760 --> 00:19:15.120 left my filter here, eh. So characteristic equals style. So now I just have to 00:19:15.120 --> 00:19:22.440 delete this filter. So if, as is the case here, the column is empty, it's an interesting case. 00:19:22.440 --> 00:19:26.520 Uh, when there are no lines, sometimes you can't filter, you ca 00:19:26.520 --> 00:19:31.200 n't, excuse me, unfilter. So at that point, you have to use the function that's there, which I 00:19:31.200 --> 00:19:37.360 've already shown you, perhaps the red filter here that removes all the column threads. And so, 00:19:37.360 --> 00:19:42.400 we end up with all our products that no longer have style-type characteristics. 00:19:42.400 --> 00:19:47.760 Let's now see how not to associate but to modify a characteristic value. For 00:19:47.760 --> 00:19:54.760 example, I would like to replace the word "be", the value "be", with the word "be natural". So, 00:19:54.760 --> 00:20:00.320 I could of course go to the bottom table, look for the material composition then the 00:20:00.320 --> 00:20:06.040 "be", and once I've found it, modify it. But already a very practical shortcut. I just have to 00:20:06.040 --> 00:20:10.880 click on one of the lines here that contains this value. For example, the first one here "be", 00:20:10.880 --> 00:20:15.880 and you see that the bottom tables have automatically synchronized. In any case, 00:20:15.880 --> 00:20:20.160 they point today, finally now, sorry, to the value "be". All I have to do 00:20:20.160 --> 00:20:24.560 is modify my value. So I can do it here, but it's more practical to do it 00:20:24.560 --> 00:20:30.560 in the translations table. Here, I directly replace "either" in editing with "either natural." 00:20:31.720 --> 00:20:39.720 I'll also do it for English while I'm at it. We'll do "natural silk." There you go. 00:20:39.720 --> 00:20:45.760 So, my modification is made here. It's important to understand that at the same time 00:20:45.760 --> 00:20:49.520 as I did it, it was made in the Prestashop database. The modification is 00:20:49.520 --> 00:20:55.680 made instantly. So in Prestashop, it's done. In the table here in the middle, "either natural" 00:20:55.680 --> 00:20:59.680 was modified at the same time. So there, there is an automatic synchronization of the display 00:20:59.680 --> 00:21:03.680 for more clarity. On the other hand, once again, here, you see in the top table, 00:21:03.680 --> 00:21:11.560 the refresh button is flashing, that is to say that the information here has not been updated 00:21:11.560 --> 00:21:17.280 . Besides, it's been a while since I updated it because the notion of the fact that the 00:21:17.280 --> 00:21:21.120 products are in themselves is not even displayed. So if I really wanted to have the information 00:21:21.120 --> 00:21:26.600 correct at the top, I start the operation again, I click on refresh and at that moment, 00:21:26.600 --> 00:21:33.720 we find the composition information, which is natural. Here, we're going to reselect everything. So, 00:21:33.720 --> 00:21:37.760 this synchronization at the top, eh, refreshing the top table, 00:21:37.760 --> 00:21:42.040 honestly don't do it every time. Uh, it's only to be done when you've finished 00:21:42.040 --> 00:21:46.240 working on your characteristics because the tables, the top table, 00:21:46.240 --> 00:21:52.520 the columns, uh, of characteristics, once again, are only informative. So you 00:21:52.520 --> 00:21:58.760 don't risk overwriting your data with the fact that they are not synchronized. 00:21:58.760 --> 00:22:05.280 So I would like to point out that the modifications in these different tables 00:22:05.280 --> 00:22:09.360 here support multi-line modifications like Magic Edit. 00:22:10.000 --> 00:22:14.000 Here, I have selected several values. For example, let's imagine that I'm going to add 00:22:14.000 --> 00:22:22.440 a common word to the end of all these values. Uh, so, I'm going to select them all. 00:22:22.440 --> 00:22:26.920 I'm going to right-click in my menu. So, you don't see it here, but 00:22:26.920 --> 00:22:32.960 the Magic Edit tool appears. I select it. My Magic Edit tool appears. So here, 00:22:32.960 --> 00:22:36.720 this isn't a training course on Magic Edit, so I'll do it very quickly. I'm just going to use 00:22:36.720 --> 00:22:42.160 the tool, not this one, but add some text in front. Here, or sorry, rather at the end. And I 00:22:42.160 --> 00:22:47.280 wanted to add the brand of these materials at the end. So here, I added my brand name, 00:22:47.280 --> 00:22:55.800 a space. I don't know the brand name, but I have my brand name. There, I apply it, and 00:22:55.800 --> 00:23:03.360 you see, I have all my values ​​that have been modified in a single step. So you can 00:23:03.360 --> 00:23:08.120 do this on the values ​​of the characteristics but also on the names of the characteristics 00:23:08.120 --> 00:23:12.720 themselves in this table here or in this table there. Let's see, for example, how to modify the 00:23:12.720 --> 00:23:17.120 values ​​of so-called personalized characteristics. So, we'll start by creating some. I'm going to 00:23:17.120 --> 00:23:22.280 choose a single product in the top table. So, it already has two characteristics. I'm going to 00:23:22.280 --> 00:23:29.880 create a weight and a personalized weight for it. So, I'm going to create a new value. So, 00:23:29.880 --> 00:23:38.480 I'm going to click here on customize and I'm going to give it a weight of 310 g. 00:23:39.640 --> 00:23:45.040 So I'm just going to put the value 310. There you go. And once it's created here, 00:23:45.040 --> 00:23:47.880 so there it's stored in the database if you like in the form of a value, it's not 00:23:47.880 --> 00:23:54.680 yet associated with the product. So now I'm going to associate it with the product. So my 00:23:54.680 --> 00:24:03.160 weight with a custom value of 310 g is associated with my product. If I want 00:24:03.160 --> 00:24:08.520 to modify this value at some point, I have several ways of doing it. I can either delete it, 00:24:08.520 --> 00:24:14.560 so unassociate it and recreate a new custom value, or directly here. 00:24:14.560 --> 00:24:19.720 So select it in the middle table and here in the bottom table, simply modify the 00:24:19.720 --> 00:24:28.760 value. For example, there's a small adjustment, it weighs 311 g. So I modify my value. 00:24:28.760 --> 00:24:34.360 Then I actually have the choice. You can either just do what 00:24:34.360 --> 00:24:38.680 I just did because in fact already at this stage the modification is taken into account 00:24:38.680 --> 00:24:42.800 but you can also, it's the old method, the prestapressing one. You had to 00:24:42.800 --> 00:24:47.280 click again on associate the value. But if you don't do it in 00:24:47.280 --> 00:24:53.320 Merlin, it works too. Okay? So simply editing here is enough. 00:24:55.000 --> 00:24:58.480 So, as a reminder, a custom value is a value that is specific to a single product, 00:24:58.480 --> 00:25:03.320 which cannot be shared between two products. So, it is not possible to modify a 00:25:03.320 --> 00:25:09.320 custom value at the same time on two or more products. However, you can create a 00:25:09.320 --> 00:25:15.280 custom value on different products in bulk, even if it's the same value. I'll try 00:25:15.280 --> 00:25:20.440 to show you this with an example. So, I'm going to take two products. We're going to take these two 00:25:20.440 --> 00:25:28.120 products here, which I call the label generator. I'm also going to associate a weight with them. So, I 00:25:28.120 --> 00:25:34.120 click on the weight characteristic, I go to custom value, I check the option, and I 00:25:34.120 --> 00:25:42.880 create a custom value of 500 g for them. So, what happens? And I associate. So, in fact, 00:25:42.880 --> 00:25:49.640 my two products end up with a value of 500 g, but it's called custom. 00:25:49.640 --> 00:25:54.360 That is to say that in the database, although it is the same value, we have two different lines and 00:25:54.360 --> 00:26:00.000 we can independently modify this value for one product or the other. For example, 00:26:00.000 --> 00:26:07.360 I will take the first product here, the value 500, I will modify it, I will change it to 501. 00:26:08.200 --> 00:26:14.080 I will do this quickly with a copy and paste to do it in all the languages. I 00:26:14.080 --> 00:26:18.320 will show you the trick. Simply, if you have a lot of languages, avoid 00:26:18.320 --> 00:26:22.920 editing it line by line. You have a mass copy function here. So there you go, I modified 00:26:22.920 --> 00:26:28.840 my custom 501 value. So it modified it on product number 8 but it did not modify it 00:26:28.840 --> 00:26:34.840 on product number 9. This one still has a custom value of 500. But initially, 00:26:34.840 --> 00:26:39.360 I created my two values ​​in a single operation by selecting the two lines in 00:26:39.360 --> 00:26:46.640 the top table before checking customize, entering my value and clicking on associate. 00:26:46.640 --> 00:26:50.720 So, how do we create standard values ​​and not personalized ones? Well, 00:26:50.720 --> 00:27:00.600 it's not more complicated. We start by choosing our characteristic. For example, style. Here, 00:27:00.600 --> 00:27:06.480 we have the existing values. And to create a new style, well, I click on the plus button in the 00:27:06.480 --> 00:27:15.480 table here of values. I just have to enter my value. I'm going to call it modern. I validate 00:27:15.480 --> 00:27:21.920 and my new characteristic value here is created. I have it here in French. I can have fun 00:27:21.920 --> 00:27:28.320 translating it into English. Here, I'm going to remove the e. There you go. Good. And now, this 00:27:28.320 --> 00:27:35.160 standard value can be associated with several products. So here, I have, uh, from memory, two products that 00:27:35.160 --> 00:27:40.560 are selected. There you go. If I select my modern value, I show you again, 00:27:40.560 --> 00:27:49.440 I associate it and my modern style is associated with my two products to create values, 00:27:49.440 --> 00:27:53.880 new values ​​in a new characteristic. So creating new 00:27:53.880 --> 00:27:58.720 characteristics, how do we do it? Well, it's the same thing. You also have a plus button here. 00:27:58.720 --> 00:28:07.680 So we're going to create, for example, a characteristic that I'm going to call, uh, the designer. 00:28:07.680 --> 00:28:15.400 There you go, I validate. So my designer characteristic is created, selected here at the bottom. 00:28:15.400 --> 00:28:20.680 All I have to do is create values, either personalized or, again, standard. 00:28:20.680 --> 00:28:23.360 I'm going to create, for example, two values, one that I 00:28:23.360 --> 00:28:34.640 'm going to call Ali's designer and another that I'm going to call, I do it twice, Leo. 00:28:34.640 --> 00:28:42.280 There you go. Now let's suppose that I don't want to create new values ​​by entering them 00:28:42.280 --> 00:28:48.480 manually as I just did, but copy the values ​​that were created in a 00:28:48.480 --> 00:28:53.880 certain characteristic, create them in another characteristic without having to retype everything. Well, 00:28:53.880 --> 00:29:00.760 I just have to select them, excuse me, select the characteristics into which I want to copy 00:29:00.760 --> 00:29:04.840 . So I already have designer here. For example, I'm going to copy them 00:29:04.840 --> 00:29:10.960 into style. So I also select style by doing a check. So, in fact, we have to 00:29:10.960 --> 00:29:14.960 do things in the right order. We have to start by selecting the two styles, finally the 00:29:14.960 --> 00:29:20.000 two characteristics. I'll get there. So designer, my source and style, my target. Then, 00:29:20.000 --> 00:29:26.440 select the values. I select Léo and Dali. And here, you have a copy 00:29:26.440 --> 00:29:32.440 /duplicate button. So this will copy these two values, let's say in the two characteristics, 00:29:32.440 --> 00:29:40.160 but since they are already in designer, it will copy them only in style. I duplicate and 00:29:40.160 --> 00:29:45.680 that's it. And you see, if I only go to style, I have my characteristics, 00:29:45.680 --> 00:29:51.760 my previous characteristic values, and then here Dali and Léo have been added. 00:29:53.040 --> 00:29:57.280 Now let's talk about deleting characteristic values, or even 00:29:57.280 --> 00:30:01.840 entire characteristics. Now, I would really like to draw your attention. I almost want to shout to 00:30:01.840 --> 00:30:08.040 wake you up because this is really a trap. Let me explain. Let's say I delete the 00:30:08.040 --> 00:30:15.800 modern style here because I want to recreate it, modify another one, replace it with something else. 00:30:15.800 --> 00:30:20.000 If I do this directly, that is, I take the modern style and I click on the minus 00:30:20.000 --> 00:30:27.480 here, what will actually happen? So Merlin warns me but most people like me 00:30:27.480 --> 00:30:31.560 don't really read the information in detail and will click delete. But what will 00:30:31.560 --> 00:30:35.800 happen in this case? Not only will the modern style be deleted from the database 00:30:35.800 --> 00:30:41.360 , but it will no longer be available for the products. And so all the products for 00:30:41.360 --> 00:30:45.520 which the modern style was associated will lose this association and therefore will lose 00:30:45.520 --> 00:30:55.160 the style characteristic. Look, I do it, I delete. Here, the button tells me to refresh 00:30:55.160 --> 00:30:59.720 because the data is no longer synchronous. If I refresh, my two products also no longer have the 00:30:59.720 --> 00:31:03.520 style. So, I can't tell you the number of times I've seen people who 00:31:03.520 --> 00:31:08.520 deleted a characteristic value and ended up with hundreds of products 00:31:08.520 --> 00:31:14.200 having lost the deleted characteristic. Well, not just the value but no longer having 00:31:14.200 --> 00:31:19.360 the characteristic at all. So if you have to, if that's what you want to do, great, 00:31:19.360 --> 00:31:25.720 that's fine. But if you simply want to replace one value with another, one value with another 00:31:25.720 --> 00:31:31.560 , excuse me, it's better to select the value in question, for example, natural, 00:31:31.560 --> 00:31:36.880 brand name here. And in fact, if you want to remove this term brand name, 00:31:36.880 --> 00:31:43.040 well modify your value. Don't delete it to replace it with another. You delete it, 00:31:43.040 --> 00:31:48.400 you rename it, you modify it and at that moment your products, all the products that are 00:31:48.400 --> 00:31:52.600 associated with this value are modified but they do not lose the composition, they do not lose 00:31:52.600 --> 00:31:58.280 the characteristic. So it's exactly the same for the characteristics themselves. 00:31:58.280 --> 00:32:02.640 For example, let's take designer that I just created with Léo and Dali. I'm going to take Dali, 00:32:02.640 --> 00:32:09.800 I'm going to associate it with my two Hauto products. There you go. If I delete my 00:32:09.800 --> 00:32:16.440 designer characteristic with the minus button here and I confirm, well my two products, finally all 00:32:16.440 --> 00:32:23.080 the products that had a designer property either, that is to say it is lost permanently. 00:32:24.040 --> 00:32:30.320 This is also why sometimes it is better to create custom characteristics like 00:32:30.320 --> 00:32:38.760 here the weight of 501 and 500 for the other product because if I modify them or delete them again 00:32:38.760 --> 00:32:42.960 it only does it for one product. So here for example if I want to delete this value 00:32:42.960 --> 00:32:49.800 501 and well I can do it. I just have to unassociate, I delete. So I have the first 00:32:49.800 --> 00:32:54.080 product has lost its weight, but the second has kept its weight of 500 because in fact the 00:32:54.080 --> 00:32:59.280 two values ​​are really unassociated because they are personalized. So a question 00:32:59.280 --> 00:33:05.040 that comes up frequently is how to order the characteristics on your site? Well 00:33:05.040 --> 00:33:11.120 in Prestashop you have a section called position that you see here in Merlin entitled 00:33:11.120 --> 00:33:16.880 pause containing values ​​from 1 to the number of characteristics. Well it is this 00:33:16.880 --> 00:33:22.400 number in fact this position which defines the display order. To change the display order of the 00:33:22.400 --> 00:33:27.520 characteristics on your product page, simply use Merlin to click on the title 00:33:27.520 --> 00:33:34.840 of the position column until you sort the rows here in ascending order of position and have this 00:33:34.840 --> 00:33:41.120 little cursor here in the shape of a vertical V. Then take the values ​​you want 00:33:41.120 --> 00:33:45.400 to move, for example, composition that I would like to put in second place here. So I take it, 00:33:45.400 --> 00:33:50.960 I click here, I drag it and I release it. And so automatically, you see, Merlin 00:33:50.960 --> 00:33:58.240 has recalculated the display order of each of the rows. Another method is 00:33:58.240 --> 00:34:04.840 to sort automatically according to a given property, for example in ascending order 00:34:04.840 --> 00:34:12.400 of ID or in alphabetical order of the name of the characteristics. So for that, I start by 00:34:12.400 --> 00:34:16.440 clicking on the column that interests me. So for example, characteristic here, so in this 00:34:16.440 --> 00:34:23.200 alphabetical order, I select all my rows. I go to the position column and I will 00:34:23.200 --> 00:34:29.160 use a property of the Magic Edit tool to automatically recalculate these position values 00:34:29.160 --> 00:34:34.840 ​​here. So I click in the column, I'm going to choose Magic Edit in the entire column from 00:34:34.840 --> 00:34:42.560 the menu. Magic Edit opens and I'm going to use the bottom tool which is called add index. 00:34:42.560 --> 00:34:48.120 actually a sequence or a series of numbers and I'm going to ask it to count from 00:34:48.120 --> 00:34:57.400 1 by incrementing from 1 to 1. Of course, I don't put a separator and I apply. So there, I made a 00:34:57.400 --> 00:35:06.000 mistake, it actually added my series to the end of my content. So I'm going to cancel. In fact, 00:35:06.000 --> 00:35:11.440 I forgot to start by emptying the content. So I choose delete the content. 00:35:11.440 --> 00:35:18.560 Complete deletion. and my index addition setting that I reset to 1 and I apply. And there, you see, 00:35:18.560 --> 00:35:26.160 I have my positions which go from 1 to 6 according to the alphabetical order of my characteristics and I 00:35:26.160 --> 00:35:35.080 save and I close. To be really complete on this alphabetical order sort function, 00:35:35.080 --> 00:35:42.000 I would have to show you a property, finally an advanced setting of Merlin. So, 00:35:42.000 --> 00:35:44.480 I'm not going to show it on the bottom table, otherwise you won't see it, but I'm going 00:35:44.480 --> 00:35:50.280 to do it on another column here at the top. Look, when I right-click in a column, 00:35:50.280 --> 00:35:56.000 in the menu that appears here, so we have the magic edit function that I just used, 00:35:56.000 --> 00:36:00.120 but here you have a new function called sort option. 00:36:00.800 --> 00:36:05.880 which allows you to define how the sorting will be done when I click on the 00:36:05.880 --> 00:36:12.720 column title. And in particular, you have functions like this one that allow you to take into 00:36:12.720 --> 00:36:18.920 account the numerics within the strings. Because in a classic alphabetical order, well, 00:36:18.920 --> 00:36:25.720 the number 10 comes before the number 2. And yes, in alphabetical order, 1 0 comes before 2. 00:36:25.720 --> 00:36:31.640 Whereas if we really want to sort by taking into account the numerical order, then 00:36:31.640 --> 00:36:35.520 you have to check this option. And you have other options here to ignore or 00:36:35.520 --> 00:36:40.320 take into account accents, capital letters, spaces, and so on. So a whole bunch of 00:36:40.320 --> 00:36:46.960 possible options so that when you click on the feature title, your rows are well 00:36:46.960 --> 00:36:55.120 ordered according to the order you want. We're now going to talk about the concept of a bottom-up filter. 00:36:55.800 --> 00:37:00.400 So, what does this somewhat barbaric term mean? At the beginning of the training, 00:37:00.400 --> 00:37:07.040 I showed you that you could sort products by, for example, right-clicking in one 00:37:07.040 --> 00:37:12.840 of the characteristic columns. For example, either natural filter on this column and equal 00:37:12.840 --> 00:37:17.880 to either natural. And there, I have more than the products in either natural appearing with my 00:37:17.880 --> 00:37:23.400 column filter visible here. So that's practical, it's quick, except that it requires first 00:37:23.400 --> 00:37:28.960 displaying all the products and then once all the products are displayed, 00:37:28.960 --> 00:37:34.520 which can be relatively long when you have a lot of them, you also have to think about displaying the 00:37:34.520 --> 00:37:43.400 characteristic columns and finally setting this filter. So there is a much 00:37:43.400 --> 00:37:48.200 faster method, especially when you have a lot of products, which we call bottom-up filters, which will 00:37:48.200 --> 00:37:54.080 give us the same result. So I'm going to remove my pre-filter, or rather my column thread 00:37:54.080 --> 00:37:59.200 here. There you go, delete all the column threads. And then I'm going to go to my bottom table 00:37:59.200 --> 00:38:06.360 here in the characteristics tab and let's suppose that I want to see that the maxi dresses, okay, 00:38:06.360 --> 00:38:11.120 these are the products that have the maxi dress property. So, I go to properties. 00:38:12.360 --> 00:38:17.920 So first, I'm going to deactivate the display of the center here to show that we don't need it. 00:38:17.920 --> 00:38:22.600 I'm also going to deactivate the display of the characteristics columns to show 00:38:22.600 --> 00:38:29.920 that I also don't need it. So I remove it, I validate. The display is redone. You see, 00:38:29.920 --> 00:38:34.000 I no longer have my characteristics displayed anywhere. So I come back to the bottom, I have my 00:38:34.000 --> 00:38:40.200 characteristics table, I go to my property characteristic, I look for my value here which is called 00:38:40.200 --> 00:38:48.480 Maxyob and you see you have a column here represents a blue filter. Well, I'm going to check 00:38:48.480 --> 00:38:54.960 this box. So that tells me that I'm setting up a filter going up on this 00:38:54.960 --> 00:39:02.120 characteristic and I'm even going to select two. I'm also going to take short dress. So 00:39:02.120 --> 00:39:10.040 I take two characteristics. Here we also see the presence of a filter. Basically, 00:39:10.040 --> 00:39:14.280 it's just an indication telling me that there are wires that have been put in place on certain 00:39:14.280 --> 00:39:19.720 values ​​of the property characteristic. Now I just have to tell it to take 00:39:19.720 --> 00:39:30.760 these filters into account to display my products up there, taking this filtering into account. 00:39:30.760 --> 00:39:37.240 I have several ways to do this. Either I click here, you see, on this little icon to 00:39:37.240 --> 00:39:46.920 display these options and click on the pre-filter option, it's called pre-filter up on 00:39:46.920 --> 00:39:55.680 products or another way to click here on another pre-filter and click here on pre-filter up 00:39:55.680 --> 00:40:01.680 from characteristic. It's exactly the same function. So I'm going to do it there. I click here, 00:40:01.680 --> 00:40:10.960 I refresh and there I will normally have all the products that respect my bottom filter. 00:40:10.960 --> 00:40:15.280 So what filter did I put that means I no longer have any products? But if I look 00:40:15.280 --> 00:40:23.960 closely, I put a type E pre-filter. So I asked it to respect two properties. I'm going to 00:40:23.960 --> 00:40:30.000 ask it to show me the products that have the short dress characteristic and the 00:40:30.000 --> 00:40:35.280 maxi robe characteristic. Both at the same time, but I don't have any. In fact, I need to put the 00:40:35.280 --> 00:40:40.760 property where. So in order for it to display the products that have either 00:40:40.760 --> 00:40:47.400 a short dress or a maxi dress as a property characteristic. This time, I refresh. And there, I have 00:40:47.400 --> 00:40:53.760 products. So, I have three. We'll check that these three products have one of these two 00:40:53.760 --> 00:41:03.720 characteristics by displaying their value. There, it tells me that product 4 has a 00:41:03.720 --> 00:41:14.480 short dress as a property. If I select all the products, property 5 is a maxi dress and product 00:41:14.480 --> 00:41:21.160 6 is also a short dress. We can clearly see that these three products meet my condition. So, 00:41:21.160 --> 00:41:28.040 once again, what's the point of doing this? Well, I can absolutely 00:41:28.040 --> 00:41:34.240 select my entire site. So I go to category, all categories in 00:41:34.240 --> 00:41:43.360 recursive mode, display, and the search is super fast because this ascending prefilter acts at the 00:41:43.360 --> 00:41:48.880 SQL query level directly when searching for products in the database. And 00:41:48.880 --> 00:41:55.480 so it only returns the three lines. Few Prestashop users know this, but 00:41:55.480 --> 00:42:02.200 product features in Prestashop can be activated in one or more 00:42:02.200 --> 00:42:07.800 stores when you are in a multi-store configuration. That is, a feature 00:42:07.800 --> 00:42:11.440 can exist in one store and not exist in another store. And that's up to you to 00:42:11.440 --> 00:42:15.880 define. So in Prestashop, it's very complicated to do. On the other hand, in Merlin, 00:42:15.880 --> 00:42:21.760 it's very easy. In fact, if I go to the features table here, 00:42:21.760 --> 00:42:27.360 I'm going to make a little space. So in the bottom table and I pull the horizontal scroll bar on 00:42:27.360 --> 00:42:32.040 the right, you see four columns appearing here representing little houses 00:42:32.040 --> 00:42:37.840 1 2 3 4 simply because I am currently in a four-store configuration. 00:42:38.480 --> 00:42:44.040 And so for each of these four stores, I have checkboxes here indicating that 00:42:44.040 --> 00:42:49.120 such and such a property, such and such a feature is or is not defined in such and such a store. And there, 00:42:49.120 --> 00:42:55.960 I can in a very very simple way, for example, height, width and weight, define that 00:42:55.960 --> 00:43:00.200 these characteristics are no longer available in shop 2 and shop 4. There you go, 00:43:00.200 --> 00:43:06.840 in one click, it's done. Also note that if you click on pre-filtering, 00:43:06.840 --> 00:43:11.360 here, you have an option that allows you to pre-filter on the selected shops, 00:43:11.360 --> 00:43:17.200 that is to say, to display in the tables at the bottom here only the characteristics that are 00:43:17.200 --> 00:43:24.520 associated with the selected shop, in the shop tab of the control panel. So, 00:43:24.520 --> 00:43:31.960 I disconnected Merlin and reconnected it to a version of Prestash Shop in 174 to show you 00:43:31.960 --> 00:43:39.240 the concept of multiple characteristics. Indeed, from version 173, Prestashop has changed the 00:43:39.240 --> 00:43:44.640 behavior of the characteristics management in order to allow associating several values 00:43:44.640 --> 00:43:50.120 ​​of the same characteristic with the same product, which was not the case until now. in the 00:43:50.120 --> 00:43:54.680 exercises we saw just before, you can go back and see each time we added 00:43:54.680 --> 00:44:00.520 a characteristic with the button associated with a product, if this product already had a value of 00:44:00.520 --> 00:44:04.920 This same characteristic, at that time, there was a replacement. Well, from 173, 00:44:04.920 --> 00:44:10.200 it's different. This notion of multiple characteristics that you see here detected by Merlin, 00:44:10.200 --> 00:44:16.120 it indicates multiple allows you to associate several values. I'm going to show what that gives here. So 00:44:16.120 --> 00:44:20.680 I'm going to display finally select my products, display the existing characteristics. So 00:44:20.680 --> 00:44:28.720 I see that there is already one for product number 10. Just select that one. There you go, 00:44:28.720 --> 00:44:33.400 I'm going to display the characteristics. So here, we have a characteristic called frame size. I 00:44:33.400 --> 00:44:41.680 'm going to see what we have in it. And we have several. We have materials. Okay? Currently, 00:44:41.680 --> 00:44:46.720 this product has a lineage value characteristic. Well, if I choose, for example, 00:44:46.720 --> 00:44:53.680 several characteristic values ​​like cotton and wool that I associate with this product, you 00:44:53.680 --> 00:44:59.320 see that these cotton and wool characteristics have been added to those that already existed. In fact, 00:44:59.320 --> 00:45:03.720 we can have as many values ​​of the same characteristic associated with a product as we 00:45:03.720 --> 00:45:09.680 want. So this behavior is present by default on pressop 173. I repeat, it seems to me that 00:45:09.680 --> 00:45:14.360 it can be deactivated. It seems to me that it's a parameter. I should check. In any 00:45:14.360 --> 00:45:20.160 case, parameters can be adjusted in the back office. And for versions before this version of 17, 00:45:20.160 --> 00:45:25.040 in fact, there were modules, like the multiple characteristic module from the 00:45:25.040 --> 00:45:29.280 Presta module company, but there are at least two others on the Presta Adon website that do 00:45:29.280 --> 00:45:34.000 the same thing. And all these modules are known by Merlin, which detects them automatically. 00:45:34.000 --> 00:45:37.520 So from the moment you install a multiple characteristic module, you 00:45:37.520 --> 00:45:42.960 end up with this type of behavior where, I repeat, the values ​​are no longer replaced but 00:45:42.960 --> 00:45:49.600 are added to the list of characteristics of a product. When we display the 00:45:49.600 --> 00:45:55.160 characteristic columns in the top table, I will do it by refreshing. A priori, 00:45:55.160 --> 00:45:59.160 excuse me, in this configuration, I don't have them. So I go back to product. 00:46:00.040 --> 00:46:04.040 I'm going to take, as before, one column per characteristic. That's it, to add them. 00:46:04.040 --> 00:46:10.440 So I was saying when we display them in this table and a product has several values ​​of the 00:46:10.440 --> 00:46:17.000 same characteristic, so we saw that our product had two, well we have two columns, 00:46:17.000 --> 00:46:22.840 one per value. So why this behavior? It's completely normal. In fact, it allows you 00:46:22.840 --> 00:46:28.560 then when we import to be able to import these two values ​​while having only one 00:46:28.560 --> 00:46:34.560 line per product. We'll see that in a moment when we see how to import 00:46:34.560 --> 00:46:41.080 characteristic values. So, let's now see how to import characteristics, that is to say, both 00:46:41.080 --> 00:46:45.640 create new characteristics, create new values ​​and associate them 00:46:45.640 --> 00:46:50.840 or not with products via import, so via a CSV or Excel file. 00:46:51.680 --> 00:46:55.200 So, I'm not going to give a complete course on importing, that's not the goal, 00:46:55.200 --> 00:46:59.120 but just show the specific part of the characteristics. So, I'm going to go quite 00:46:59.120 --> 00:47:05.440 quickly over certain parts. So, I launch the import tool, you already know that. I'm going 00:47:05.440 --> 00:47:15.280 to immediately create a new source that I'm going to call demo characteristic. I'm going to take this. 00:47:15.280 --> 00:47:21.160 Control C just to copy it, reuse it later. There, I do as usual, 00:47:21.160 --> 00:47:25.320 I'm going to look for a file and I'm going to take here characteristic words that I prepared 00:47:25.320 --> 00:47:32.880 and I open it. There, my file is selected. I tell it that it's about product. Okay, the rest 00:47:32.880 --> 00:47:37.760 I don't touch. I'm just going to show you the contents of the file. So, I do edit here 00:47:37.760 --> 00:47:43.680 which opens the internal Excel file editor. So, here is the contents of my file that I 00:47:43.680 --> 00:47:48.120 prepared in advance. I put two lines, one for the one line for product 1, one line for 00:47:48.120 --> 00:47:55.800 product 2 with their number simply and then two characteristics, a composition and a height. 00:47:55.800 --> 00:48:02.080 So, I didn't choose at random. Composition, it's a characteristic that already exists. Cotton 00:48:02.080 --> 00:48:08.760 already exists. Leather doesn't exist. Height doesn't exist at all. So what I expect from the program, 00:48:08.760 --> 00:48:17.440 This is to create the new composition. Value to cook to create a new composition, sorry, 00:48:17.440 --> 00:48:24.080 a new one, excuse me, I'll get there, a new characteristic named height with two 00:48:24.080 --> 00:48:32.040 new values, Arthur and Étienne, and to associate these four values ​​with my products 1 and 2, 00:48:32.040 --> 00:48:38.680 close that, so step 2, we do as usual. I'm going to create a new model. I give it 00:48:38.680 --> 00:48:47.320 a name out of habit, the same name as my source. I validate. It reads my file with my 00:48:47.320 --> 00:48:54.520 different columns. Look what it did. Composition, it recognized it all by itself. Merlin knows 00:48:54.520 --> 00:48:58.920 that there is already a characteristic called composition. So it did the mapping. It tells me 00:48:58.920 --> 00:49:04.160 that it is an ID, a characteristic value that it has directly associated with the correct 00:49:04.160 --> 00:49:11.840 characteristic, composition. And it suggests to me, finally, it makes it as a choice, as 00:49:11.840 --> 00:49:17.120 anticipation, that it is a value inside the column and to write it if it does not exist. 00:49:17.120 --> 00:49:21.840 That corresponds exactly to what I want, so I check it. For height, however, he doesn't know what 00:49:21.840 --> 00:49:27.360 it is. That's normal, it doesn't exist yet. So I'm going to help him a little. So I'm going to create my 00:49:27.360 --> 00:49:39.040 page myself and I go to the very bottom of the list. So you don't see. So I'm going to shift that, 00:49:39.040 --> 00:49:42.720 hoping that this time you can see. There you go. So at the very bottom 00:49:42.720 --> 00:49:50.920 here, the penultimate line, you have ID or value of characteristics. So I'm going to choose that. 00:49:50.920 --> 00:49:57.640 Minimize. There you go. So ID or value of characteristics. In the list here, 00:49:57.640 --> 00:50:02.440 I have the list of characteristics that already exist, so composition, paper, etc., 00:50:02.440 --> 00:50:09.600 but my height characteristic doesn't exist. So Merlin offered to create a new one 00:50:09.600 --> 00:50:14.320 from the name. Exactly what I want. So it will take the title of my height column 00:50:14.320 --> 00:50:20.400 to create a new characteristic. And then third choice, you have to tell it what 00:50:20.400 --> 00:50:25.640 my column contains. It could be identifiers, it could be values, with the recommendation 00:50:25.640 --> 00:50:29.960 not to create them if it doesn't exist. So use only the one that already exists or, 00:50:29.960 --> 00:50:34.720 on the contrary, create them if they don't exist. And then the third choice is that it can also create 00:50:34.720 --> 00:50:40.120 custom values. So we've already seen what that is. So product-specific values ​​that cannot 00:50:40.120 --> 00:50:44.280 be shared between multiple products. So here, 00:50:44.280 --> 00:50:50.840 I'm going to ask it to create them if it doesn't exist and I check them. And finally, well, this is 00:50:50.840 --> 00:50:55.880 my key. So, it didn't recognize it, I hadn't named it correctly. I'm going to help it a little 00:50:55.880 --> 00:51:04.960 by indicating that it's the product ID and I check it. That's it, that's it for step 2. Step 3, 00:51:04.960 --> 00:51:11.480 well, I just have to choose my key carefully here. Since I've just mapped a section containing 00:51:11.480 --> 00:51:16.200 the product IDs, by default, that's what I'm going to choose. Identifier, I could have put 00:51:16.200 --> 00:51:23.280 another column with the references, supplier reference or barcodes. As usual, 00:51:23.280 --> 00:51:30.840 I click on display. He confirms to me that these two products 1 and 2 do indeed exist. And look 00:51:30.840 --> 00:51:35.680 what he did. The composition characteristic here is in gray. That means it 00:51:35.680 --> 00:51:42.400 already existed. On the other hand, this one is written in green. That means he just created it for me and he 00:51:42.400 --> 00:51:49.120 gave it the number 6. The database gave the number 6 to this new characteristic. In 00:51:49.120 --> 00:51:55.120 the columns here, I have the values. So, if they already exist, they are indicated in black with 00:51:55.120 --> 00:51:59.880 their number. If they don't exist, they are indicated in red with a question mark. 00:51:59.880 --> 00:52:04.000 So, a priori, he didn't find any. So, I admit that I expected him to 00:52:04.000 --> 00:52:09.040 find the cotton characteristic. Probably in the database, it's not written exactly 00:52:09.040 --> 00:52:13.880 like that and for him it's a new characteristic. So we'll let him do it, 00:52:13.880 --> 00:52:21.280 we'll check later if he's actually right or not. So I select these two lines. I'm 00:52:21.280 --> 00:52:27.960 going down to step 4. So in step 4, I'm not going to do much. I'm not going to ask it 00:52:27.960 --> 00:52:32.280 to create the products. I don't have any imported images. So basically, I don't have to touch anything. If you want 00:52:32.280 --> 00:52:36.440 For more information on all these options, I invite you to watch the import tutorial. 00:52:36.440 --> 00:52:42.960 That's not the purpose of this one. And finally, step 5. All I have to do is click on either import 00:52:42.960 --> 00:52:47.360 or schedule the import to do it later or to do it repeatedly 00:52:47.360 --> 00:52:53.680 and schedule it for a given date. So I'm just going to import now. 00:52:54.760 --> 00:53:01.240 So the program launches, it tells me that it has updated the two products 1 and 2. There you go. 00:53:01.240 --> 00:53:08.000 So we're back in the main window. So we'll immediately see our two products 00:53:08.000 --> 00:53:16.640 1 and 2. So here they are. So take a good look. Indeed, in my product 1, I have 00:53:16.640 --> 00:53:24.480 a cotton composition, an author Arthur for the 2 leather and Étienne. And we can see that it 00:53:24.480 --> 00:53:30.520 has created a new characteristic called height with two values ​​Étienne and Arthur. And 00:53:30.520 --> 00:53:36.520 then in composition, I have leather which has been created and cotton as well. Indeed, I didn't have a 00:53:36.520 --> 00:53:41.000 cotton composition. I thought that was the case. Quite simply, I had confused it, I think, with 00:53:41.000 --> 00:53:45.800 frame size. There you go, which actually contained a cotton value. But in composition, I didn't have one 00:53:45.800 --> 00:53:50.920 . So, it created my four values ​​as requested and it 00:53:50.920 --> 00:53:56.440 associated them with my two products. So, if I quickly go back to the import with this little button here, 00:53:56.440 --> 00:54:02.480 I'll remind you of the trick. We see here that in the import table, in addition to giving me the information 00:54:02.480 --> 00:54:08.200 that it updated the products, in fact, we see that in the lines, it replaced the 00:54:08.200 --> 00:54:12.840 values ​​in red with values ​​in green like cotton Arthur and the question marks with 00:54:12.840 --> 00:54:20.720 the number of the characteristic values ​​that it created. So just a little other information. 00:54:20.720 --> 00:54:28.360 If we go to step 4 here, you see here it's grayed out because it's only 00:54:28.360 --> 00:54:34.880 informative and it's checked. It tells me that we are in operation, uh, how can I say 00:54:34.880 --> 00:54:39.160 multiple characteristics because actually, I have just imported into my site which is 00:54:39.160 --> 00:54:45.960 still in inversion in sorry in version 174, so configured in multiple characteristics. 00:54:45.960 --> 00:54:52.880 So if I import several values ​​of the same characteristic, for example, several compositions 00:54:52.880 --> 00:54:57.720 in the same product, well, these values ​​will be added. They will not be replaced, 00:54:57.720 --> 00:55:03.520 they will not replace each other but will be added, accumulated. If I want to avoid this behavior, 00:55:03.520 --> 00:55:10.400 I just have to check this option here, replace rather than add. There you go. So when it is checked 00:55:10.400 --> 00:55:14.160 here, I will end up with the old operation typically of version 16 00:55:14.160 --> 00:55:19.960 where the values ​​replace each other where a product can only have one value of the same composition. 00:55:21.080 --> 00:55:25.640 If you want to import several values ​​of the same characteristic to a product, 00:55:25.640 --> 00:55:29.200 you just have to multiply the columns. So for example, if you want to give two 00:55:29.200 --> 00:55:35.200 different compositions to the same product, you put two columns with different values 00:55:35.200 --> 00:55:40.520 ​​of composition characteristics. But be careful, you really have to give them a 00:55:40.520 --> 00:55:45.080 different name for your columns, eh. You can't have two columns called composition, 00:55:45.080 --> 00:55:49.200 it won't understand. So in this case, you have to name one composition one and the other composition 00:55:49.200 --> 00:55:55.840 2. And at your step 2, obviously since the name won't correspond to a 00:55:55.840 --> 00:56:00.440 given characteristic value, it won't do the mapping automatically. You will have your 00:56:00.440 --> 00:56:08.520 composition one and composition 2 and here it will probably mark something as new to create, 00:56:08.520 --> 00:56:12.400 doesn't understand what it corresponds to. At this point you will have to help it simply tell it for the two 00:56:12.400 --> 00:56:17.360 columns to map them to the composition section. There you go. So you do that twice in two 00:56:17.360 --> 00:56:23.600 different columns again with different titles and you can thus import 00:56:23.600 --> 00:56:29.800 multiple characteristic values. So either on condition of being in 73 at least or by 00:56:29.800 --> 00:56:35.160 having installed a multiple characteristics module. So there you go importing 00:56:35.160 --> 00:56:39.840 characteristics. It's not very complicated with Merlin. You just have to think about the fact that you have to 00:56:39.840 --> 00:56:46.600 put each characteristic in a separate column, like here composition or height. If 00:56:46.600 --> 00:56:52.320 I want to put two compositions and well it will need a third column with a different name and 00:56:52.320 --> 00:56:58.360 map them to the last one finally the penultimate one, excuse me, uh here property in the list 00:56:58.360 --> 00:57:04.720 which is called ID or characteristic value. Then, either ask it to create a new one 00:57:04.720 --> 00:57:11.600 if it does not yet exist, or to use a characteristic already existing in the list and 00:57:11.600 --> 00:57:16.680 then define whether or not it should create the new values. You can also update 00:57:16.680 --> 00:57:21.360 product characteristics by having columns that contain only the numbers, 00:57:21.360 --> 00:57:25.880 the characteristic identifiers, finally the values ​​of existing characteristics. In this 00:57:25.880 --> 00:57:32.520 case, you will choose identifier here. If you make a mistake, if it contains identifiers and 00:57:32.520 --> 00:57:37.360 instead you put value, in fact, it will not understand more exactly, it will execute what 00:57:37.360 --> 00:57:42.320 you ask it. That is to say that it will create as value the numbers of the characteristics that 00:57:42.320 --> 00:57:48.960 you put in your file. So it will not be the expected result of course. There you go, 00:57:48.960 --> 00:57:55.240 this part on importing ends uh this training on characteristics. 00:57:55.240 --> 00:57:59.480 I hope I've been thorough, otherwise I'll definitely add more sections. Thanks and see you soon.