Transcription
Let's answer the age-old question in the 1C world. The difference between a catalog and an information register. The question is very fundamental, very important, very old. Often the question arises, what is better to use in a specific situation: an information register or a catalog? The short answer to this question will be this: you need to use your brain. A catalog stores an object of analytical accounting, and an information register stores state indicators. In fact, that's the short answer. Well, now let's look at the differences between these two objects in the 1C configurator. We will run through some scenarios in the system, and answer this question in more detail. The difference between a catalog and an information register. I have opened the configurator. We will work on the 1C ERP base. We will create a new extension. We will open the configuration block. We will go to configuration extensions. I have several extensions created here. Let's create one so that our test is clean, new. We click add. We specify the name of the extension. We click OK. We also uncheck the safe input option. We also uncheck the protection against dangerous actions. In most cases, I always do this, because in most cases it only interferes. And here our extension is created. We double-click on it. It appears in the left part of the screen. Let's close the previous extension I was working with. Here. And in the upper part, we see our main standard configuration. And in the lower part, our extension will be. If it looks different for you, there are several options here. When we click on this particular extension window, it might look like this. But I prefer it when the extension and the main configuration are fixed on the left and separated. To do this, we select the "free" view and move it to the left part of the screen. And we move our main configuration in the same way. Everything, now we have a convenient layout. At the top, we see our configuration, at the bottom our extension. Well, let's create an information register. Our business case will also be simple. Let's say it will be related to production. Let's come up with a business case now. To create an information register, we find the item in our extension "Information Registers". We click add. Here we specify the name of our information register. The name should be without spaces. Well, the synonym is the name that can have spaces, right? That is, a more convenient name for our information register. Then we go to subsystems. Here we can add our information register to subsystems. Let's create a subsystem so that our test is, as it were, clean. And all the documents that we will create, catalogs, will be in our subsystem. We click, find the "common" menu item in our extension, click add, and create our new subsystem. Let's call it "tests". Everything, we don't need anything else here. We click close. Everything, we have created the subsystem. And here our subsystem has appeared. We select the "tests" option so that our information register is displayed in our subsystem. We move on. And in the "data" tab, we see three fields that we can enter: dimensions, resources, and attributes. We see that standard attributes are available. These are period, registrar, line number, activity. Yes, let's see what determines whether we will use the period, registrar. To do this, let's go to the "main" item. And here we see, we need to specify the periodicity, mode, and recording mode for the information register. If we specify in periodicity that it is non-periodic, we will not specify, well, the system will not record the period, i.e., the date. Let's specify, for example, periodicity within a day. Well, let the recording mode be subordinate to the registrar, right? Here we have two options. Independent is when we will manually enter information into this register in the system, and subordinate to the registrar is when, after posting documents, this information register should receive information, new records should be created in this information register. Let's consider all these options. Let's specify that it will be an independent information register at this stage. Then we will create a new information register that will be subordinate to the registrar. Let it be independent. We go back to the data tab. And here we see, in the standard attributes, the period field has already been activated. Let's figure out what to enter into each of these, what will be our dimension, resource, and attribute. I've come up with a small business example here. Let our information register contain this information. That is, within the date, we want to see by employees, in which shifts they worked, in which workshop, on which machine, their defect percentage. Let's decide what from this will be a dimension. A dimension is a rule in an information register that values must be unique within the dimensions. That is, if, for example, the date is a dimension, well, it is already a dimension, right, then the information register will not allow recording a value. It will not allow these two values, because it is for one date, even though two different people worked, the system will not allow it. Therefore, we need to make the employee a dimension as well. If the employee is also a dimension, then in such cases the system will allow us to post all these records in the information register. Well, let's make the rest four values resources. Let's enter these values into the system, into the information register. Let's call the first dimension "employee". Let the field type be string, length 100. Let's create a resource. This will be "shift". Let it be a string, length 10. Next. "Workshop". Data type. String. Length 100. "Machine" also let it be length 100. The next resource is "defect percentage". Let it be a number, length 2, precision 2, and non-negative. Let's close here. For the changes to take effect, we need to update the data configuration or press F7. The system provides information that a new data object has appeared. We click accept and click start debugging F5 to launch the system in debugger mode in user mode. The system has launched. In the lower left part of the screen, we see the subsystem we created. Here we see our information register. Let's open it. So, here we indicated that our information register is independent. Yes, here we indicated that it is independent. This means we will enter values manually. Well, let's create a value. Specify the date. Let's specify the employee. First shift. Machining workshop. Machine 23AV. Defect percentage. Let's specify 0.2. Save, close. Let's create another value. Let's copy. We only specified one dimension in the configurator. Employee. The date is our second dimension. Let's try to save and close in this format. The system gives a message that a record with such key fields already exists. Let's change the employee's name. The system allowed saving. This is how dimensions differ from resources. Let's create another information register, but this time it will be subordinate to the registrar. Let's click copy. Let's open it. Recording mode, subordinate to the registrar. Let it also be in our subsystem. Let it have the same data. And here we see the "registrar" tab has appeared. Whereas in the independent information register, this tab is not activated. Let's create a document for this information register, after posting which values will be created in the information register. Let's find the "documents" tab here, click add. Let's call the document "production output", also include it in our subsystem. And in the data tab, in the attributes, let's enter all our values, the same as in the information register. Date, employee, type string, length 100 characters, shift, string, length 100 characters. Let's copy. It will be workshop. Let's copy machine and copy defect percentage. Here the data type is number, length 2, precision 2, non-negative. Let's go to "movements". And here we will specify to which information register we want the data to be written. Let's select our information register, "new registrar", and go, open the movement constructor. Here you can click "fill expression". Well, and since our names match the attributes in the information register, everything is filled correctly. We click OK. [music] Yes, the system will give us code. Here we can just close it. Let's click update database configuration and click start debugging. Let's open our subsystem. And here we don't see our new information register, because it is no longer independent. That is, we do not enter values into this information register manually, but it is subordinate to the registrar. Let's open the "production output" document, create a new one, and see how the record in the information register works. So, let's specify the date. Employee Ivanov Sergey. Shift, second shift, workshop, machining, machine twenty-third, defect percentage 1%. Post and close. Everything, the document is posted. And let's open our information register. To do this, we will use functions for technical specialists. We enter "information register new". And here we see the value. Let's create one more value, one more document. Let's copy. So, we can't have the same. Let's say Sergey Ivanov Maxim. Post. Everything, we see that values are falling here. Information registers have a large number of possible use cases, from maintaining currency exchange rates to using them in a quality control subsystem, where, for example, for batches, for series, we can enter a quality control flag, whether quality control has been checked for the series or not. Well, now let's create several catalogs and see in practice how a catalog differs from an information register. Let's find the "catalogs" folder in our extension. Let's create a new catalog. Let it be the enterprise production structure, where we will specify the workshop structure. Let's fill in the name. Let's specify the subsystem. And in the data tab, we already see the first difference from an information register. Let's open the information register settings. Subordinate to the registrar. Let's also open its data tab. And yes, in the information register, we see that we have three data types that we can enter: dimensions, resources, attributes. But in a catalog, we have, accordingly, only two types: attributes and a tabular section. Well, let's make the first attribute "name of the department", length 100. And the second attribute - the number of people in the department, the number of employees. Let's also look at the standard attributes. And here too, we see a difference from the standard attributes of an information register. Here we see, yes, the key difference between a catalog and an information register is the reference. There is no reference in an information register. Using this reference, we can use this catalog in other 1C system objects. We cannot use an information register by reference, because there is no reference. We also see several other elements that are not in the information register. Deletion mark, code, name, but the main difference, of course, is the reference. Let's update the configuration, launch the system. In our subsystem, we will see the catalog. Let's create several objects, several elements. Let it be "production". Number of employees eight. Let's create "accounting". Five employees and "administration". Four employees. Well, let's create a few more production departments. Production South, Production East. Now let's create another catalog, let's call it "machines", include it in our subsystem. And in the data, let's also specify. The name will be standard. Let's specify the cost. And let's specify our department to which this machine is assigned. Here, in the type, we will specify a reference to the catalog. Catalog, reference, production structure, specifically in our extension. We click OK. We click update configuration, accept, and launch. Let's open our subsystem. Here we see the new catalog, "machines". Let's create a name. Let it be machine 3. Cost 300,000 rubles. Department. And here we see, yes, the possibility of our possibility of reference. And here we see the elements. In our catalog "production structure". We can specify any element, save, close. And in this form, we see, yes, the filling of our catalog. Machine five, cost there 20,000 rubles. Department, save, close. Thus, yes, the key difference between a catalog and an information register is referentiality. A catalog can be used in other catalogs and other objects. And from an information register, you can only pull information. That is, you cannot select a counterparty from an information register in an invoice. A catalog has object-oriented data storage, while an information register has non-object-oriented storage. And here on the screen, I have listed the main differences between a catalog and an information register. These are the main parameters for determining which is better to use: a catalog or an information register for a specific task. Mhm.