Periodic details 1C 8.3. Creating and recording a new reference item

Hello, our dear colleagues and partners. Over the past month, we received a few questions from users of the program 1C Accounting 8.3 with a request to help set up a list of nomenclature in the program as it was in 8.2. That is, in the old program they could see in the list of the nomenclature of the article or the code of the nomenclature position. It was very convenient. But at 8.3, nothing can be seen and incomprehensible. In fact, everything is very easy to configure. Therefore, we decided to write a little instructions for setting up reference books in the program 1C Accounting 8.3, but this algorithm is applicable in any configuration 1C.

So, in the "Reservations" section, I will operate the Handbook "Nomenclature".

In the list that opens, we see the name of the nomenclature, in which there is no information about the article article. In order to change the help of the directory, use the setting of its shape. Opening the list of commands by the "yet" button, at the bottom we will find "Change shape".

In the form of form, we present all the details of the directory, which can be displayed.

By installing the appropriate checkbox, for example, the "code" and "article" we get a list of the nomenclature in which the code and article are displayed.

However, in this form, some users do not like the reference book either. They want to see the number and article before the name of the goods. It is also very easily solved. Open the list setting form and with the help of blue arrows on the toolbar move the props up or down, depending on how we want to see the list. You can also "drag" details using the left mouse button.

Now the list of the nomenclature is as you wanted to see it.

Experiment with the list settings. Do not be afraid. All I wrote, you can use in any configuration on managed forms and in any reference book, for example, to display a PPC in the Contract Reference or the Contract Certificate in the Agreement Certificate. Do not be afraid that you will "break" in the program.

In extreme cases, you will always save the ability to "set standard settings", which is in the form setting in the "More" section

And further. Sometimes customers call with such a question: "I pressed something and I now name it is not alphabetically. Return everything as I had. " This question is also easily solved. In each directory in the title bar table part there is always a "magic arrow", which indicates the column, which is installed and the direction of this sorting.

You can change the direction of sorting by simply by clicking on this arrow and then the list will be sorted, for example, from I am before A. If we want to sort the goods by code, then for this you need to click on the name of the corresponding "Code" and "Magic Arrogo "will move to another column.

That's it. I hope my tips will help you in working with 1C programs. Work in 1C with pleasure. Join our groups in contact and classmates and you are always the first to know about our new articles and changes in programs.

The user with reference books and documents in 1C consists of filling the fields on the form.

Details 1C are the directory and document fields that are displayed on the form so that the user filled them.

Consider in detail the topic of details in 1C.

What is 1C details

Each reference book and document 1C consists of a set of fields. Such fields are called 1C details (for the 1C programmer).

In the configurator, in the 1C configuration tree, expand any directory or document and you will see a branch of the details. This is a list of details (fields) of the directory.

View as the same details 1c look on the form of the 1C reference book.

Each property of 1C has properties that indicate what kind of value is stored in the prop. (String, number, etc.) and how the user will work with it.

Right-click on any props 1C and click Properties. The list of properties of the selected props opens in the right window.

The main properties of 1C details:

Standard details 1C.

As you notice, there are 1C details on the form of the directory, which are not listed in the configurator: group, name, bik.

In the form of a list of reference book, also there are details of 1C, which are not listed: a removal mark.

These are standard details 1C. What it is? Everyone has a set of details 1C by default. For reference books, for example - code and name. Documents this is the date and number.

Standard details 1C can be viewed as follows:

• Go to the 1C object editor (directory or document) by clicking on it twice with the mouse
• In the window that opens, select the data tab
• Here you can configure standard details Code and reference name
• Click the Standard Details 1C button to view the full list.

General details 1C.

Starting from version 1C 8.2.14 in 1C, a new object 1C appeared - General details 1C. Using it, you can add props (field), which will be present immediately in a variety of reference books and documents.

Properties of total details 1C:

• Auto use - adds total 1C props to all reference books and documents
• The composition - allows you to add a total details of 1C only to the necessary reference books and documents (auto use then not to use to value).

How to add requisite 1c

Right-click on the branch of 1s the desired directory and select Add.

We introduce the name of 1c props, for example, "addiction" and synonym for an office ". Type Let's leave the default line, but put a tick unlimited length.

We will add another props 1C in the same way, just choose the type of Boolean, let's call it "running".

How to derive props on the form 1C (thick client 1c)

We will reveal the branch of the form of the same reference book. To open the form - choose the form of the item and press it twice with the mouse.

Pull the mouse over the edge of the form and stretch it (optional item).

In the configurator panel, click the "Data Placement" button. You can also use the menu / placement menu.

You see - our form details are not bred. Install the checkbox on them. And also ticks insert the inscriptions and place automatically.

How to derive props on the form 1C (subtle client 1C)

We will reveal the branch of the form of the same reference book. Select the form of the element and press it twice with the mouse.

On the Requisites tab, open the Line object. You will see a list of details added earlier in the directory.

Now simply drag from the right window to the left right props and it will appear on the form.

Requisites forms 1C.

In the Tolstaya Client, the form has its own props. They are on the details tab.

These details are not stored in the database, but they can be used on the form for fields that are needed to work with the form.

For example, you added a tick. When it is pressed on the form, something happens. The check mark value for you does not matter (it is not necessary to write it) - it is used only to switch the form when working with it. In this case, as data, you do not use the requisite of the directory, but the form props.

Periodic details 1C.

In 1C version 7.7 were periodic details. Their meaning is: the value of the props is different in different dates. For example, the value on September 1 is one, and on October 1 - another. At the same requisite.

In 1C 8 periodic details no. This is implemented as follows:

In 1C 7.7, the directories had interesting details - periodic, they could remember the value of props with reference to time, it was not so convenient to work with them so that it is very convenient, but for the absence of alternatives. After the transition to 8-ku, many programmers were surprised to find the absence of periodic details in reference books.

Typical tasks that are solved using periodic information registers is storing information with reference to time. Information may be heterogeneous this and the price of the nomenclature, and the employee occupied by the employee at different periods of time, and the parameters of the tax accounting of the enterprise. In 8 analogue of periodic details, periodic registers are reported.

In order to repeat the functional 7.7, you need to do the following:

Create a register displaced "rejoedannectanentragent", indicate that this is a periodic register of information with the frequency of the day.

Now we need to add to the "Data" tab - the dimension "counterpart" type that coincides with the reference book in which we want to implement a similar periodic props functionality. In the details of the details, add the details of the data that are tied to time. For a counterparty, it may be a legal and physical address, the main phone, the name of the head, the main fax, etc.

After saving the configuration, you can access the information register through the side menu (in the controlled application mode), see the screenshot.

In the normal application mode through the "Go button"

But if we look at the completed register, then note that it is quite difficult to understand what information is quite difficult, as we see the entire set of data as an integer, and not only the current information currently.

When the information can be easily mistaken, it is advisable to show the latest information in the counterparty card today. There is no programming here without programming.

To begin with, we will add a group to the form that "contact details" will be added to it. Two props "Manager" and "Phone"

And in the module forms to the event "opening" will hang actions to obtain topical data:

& Cutting Operation Procedure (Refusal) // Insert the VMIST distributor DANI \u003d RECIMATIATUALNIDANI (); Attempt by director \u003d DANI. Kerіvnik; exclusion of detention; Attempting phone \u003d DANI. telephone; exclusion of detention; Extrudresses

The function of obtaining topical data is as follows:

Recycling function () // Insert the VMIST distributor // ((designer__sult_sult // Denmark fragment concerned constructor. // With a re-Viceristan constructor, made by hand the zmіni is improved !!! Request \u003d new request; Inquiry. Text \u003d "Select | PeriodicHeddannіktragencentsrezrevy. Counterparty | PeriodicHeddannіktragencentsrezrevy. Kerіvnik, | PeriodicHeddannіktragencentsrezrevy. Addresses | PeriodicHeddannіktragencentsrezrevy. Telephone |OF | Registerings. Periodichnіdannіktragenent. Circling as periodichennіktragencentsrezrezrevy | Where | PeriodicHeddannіktragencentsrezrevy. Counterparty \u003d & Contract"; Request. Installation parameter (" Contract ", Object. Reference); RESULT REPROVE \u003d REQUEST. Run (); EXCHANDING EXPERIENCE \u003d RESULT SUPPLY. Choose (); Danі \u003d New Structure; While the selection is the following () cycle. // insert the robberization of vibration //SebobadetalCaptism. Packs; Dani. Insert ("Kerіvnik", elegadeatual compensation. Kerіvnik); Dani. Paste ("phone", sampledatalization. Phone); Notify (sampledatvapi. Phone); EndCycle; Return Dance; //)) Designer_Protype_S_Processing_ Endfunction

I used the query, although you can use for these purposes and less bulky design:

Selection \u003d new structure; selection. hold ("counterpart", object); Data \u003d Registribution. Contact_NFORMACIA. Pour the last more (, selection); Report (data. Packs); Report (data. Number ());

Pay attention to the function Get the moretwo parameters of time and selection parameter are passed, but if we need to currently, then the first parameter can be omitted, in the selection the key name must match the valuation of the register measurement.

The main thing is not to forget in the register to set the corresponding ticks on the "Other" tab

If you figure out, a periodic information register is a much more flexible tool compared with periodic details at 7.7. In typical configurations, it is widely used.

Appointment of reference books

The directory stores a list of possible values \u200b\u200bof one or another object or requisite. References are used in cases where it is necessary to exclude ambiguous BBof information. For example, in order for the buyer, the seller, the storekeeper and the director to understand what kind of product is we talking about, everyone should call it equally. And in this case, we need a reference book. Usually, on the trading enterprise, it has the kind of price list.

System 1C: Enterprise 8 allows you to conduct a practically unlimited number of necessary reference books. Each reference book is a list of homogeneous objects: posts, employees, customers, goods, etc. Each such object is called a reference element.

From the user's point of view, it should be borne in mind that the configurator does not create a directory itself as a list of values, but a reference work is being developed, its template. During the configuration process, the structure of the information will be stored in the directory, the screen and, if necessary, the printed representation of the reference book is given various features of its behavior.

Requisites Director (Fields)

As mandatory details, each directory has The code and Name. The code of the reference item can be both numeric and textual. System 1C: Enterprise 8 provides ample information on how to work with directory elements: automatic assignment of codes, automatic control of the uniqueness of the code and others.

In addition to the code and name, in the reference books of the 1C system: the company can be stored any additional information about the reference element. For storage of such information in the directory, additional details (fields) can be created. Using the remunition mechanism of the directory, it is easy to organize, for example, a card file of employees. For example, the Directory of Employees will almost certainly have details position, salary, dataging and others. The company 1C anticipated programmers and introduced two mandatory (predetermined) details: code and name to all reference books: code and name. Indeed, almost any object from real life contains these attributes. For example, for employees the code is a table number, and the name is the name, name and patronymic (FULL NAME). In addition, the use of codes (when using automatic numbering) allows you to easily understand which item was introduced earlier, and what later in the database.

Data types

For each details of the reference book, you must specify the data type, for example, the "number", "line", "date", boolean (truth or lies). These are basic types, but you can specify complex data types. For example, the position props has a data type of position. In this case, the values \u200b\u200bof this props will be selected from the reference book. So the simplest connection between the directories is being implemented when the values \u200b\u200bof the details of one reference book are selected from the elements of another directory.

Hierarchical directories

List of reference items in System 1C: Enterprise 8 may be multi-level. In this case, all rows of the reference book will be divided into 2 types: "Simply" elements of the directory and group of the directory. Groups allow you to switch to the underlying levels of a multi-level reference book. The use of multi-level reference books allows you to organize information input to the directory with the desired degree of detail. Elements and groups of elements in a multi-level directory can be transferred from one group to another.

Subordinate reference books

There may be a subordination relationship between reference books. In terms of relational databases, the "one-to-many" connection is established between the tables. In this case, each element of the subordinate directory will be associated with one of the elements of the owner's reference book. Sometimes it can be said that the elements of one reference book belong to the elements of the other. For example, the system may have a handbook of the contract. Then you can make a subordinate directory customers. This means that the client owns agreements and one client may have several contracts.

Table parts

Starting from version 1C 8.0, the platform implements the ability to set one or more tabular parts in the directory element. This feature is recommended to be used to reflect information associated with this item, but not having its own object entity (for which the subordinate reference books are recommended). For example, for the Directory, the staff may be equipped with tabular parts of education and prepaid. Working with tabular parts is similar to working with subordinate reference books except that the table parts cannot be used as the values \u200b\u200bof the details of other objects.

Where is the software code for working with reference books?

Since to perform the program code, we need to access the database, these slicer code data must be placed in procedures and functions (or modules) servers running on the side. For more information, see section.

1. Link to reference book

To work with the directory from any module, you must first create a link to this directory.

Spseruditors \u003d References. Staff ; // or 2 option
Freightness \u003d reference books ["posts"];

2. Creating and recording a new directory element

Novel \u003d reference books. Staff . Create element ();
Noval. Name \u003d "Petrov Petr Petrovich";
Noval. Salary \u003d 25000;
Noval. Write down (); // It is at this moment that records in the database

3. Creating and recording a new directory group (for hierarchical directories)

New \u003d. Directories. Sydrudniki. To create a group ();

New. Write down ();
// or 2 option
New \u003d References ["Employees"]. To create a group ();
New. Name \u003d "Working";
New. Write down ();

4. Search for a reference item

// If the element is found, it returns, otherwise the value is immediately returned

Found today \u003d springs. Found contact (123); // We are looking for code
Found today \u003d springs. Foundation("Ivanov Ivan Ivanovich"); // Name
Found today \u003d springs. Foundorrow("Salary", 5000); // by requisite

If found by found \u003d Uncertain then
// item not found
Ended;

5. Removing the reference item

SprSotron \u003d Reference books. Staff ;

Springsotr. Remove (); // Direct removal of the current element of the reference book

Springsotr. Setpowers(True); // Removal Mark
Springsotr. Setpowers(False); // Remove the note to remove

// You can check whether the element is marked for removal
// The property of the tag has a type of boolean (truth or lies)

Mark \u003d springs. Petchildren; // Please note: this property
If the mark is \u003d truth then
// element marked for removal
Ended;

6. BRAIN ELEMENTS OF THE COUNCIL

Sampling \u003d References. Employees. Employee();
// Beginning of the bustle elements of the reference book in the cycle
// Actions with the next element ...

EndCycle;

7. Parent. Bruep items inside the group.

The group in terms of 1C is a "parent".

SprSotron \u003d Reference books. Staff ;
Grouping\u003d Springs. Foundation("Working");
Sampling \u003d springs. Choose ( Grouping);
While sample. Next () \u003d 1 cycle

Report ("Officer" + sampling. Name);
EndCycle;

8. Owner. Bruise the elements of the directory belonging to an element of another reference book.

One directory is subordinate to another directories, such as the directory of the tax collectors subordinate to the directorial staff.

Sampling \u003d References. Topics. Choose (, employee); // here employee - link to the element of the directory employees
While sample. Next () \u003d 1 cycle
// Actions with the next element
Report ("Benefit" + sample. Name);
EndCycle;

9. Transaction

When creating a variety of reference items to speed up the work, you can enter into a transaction cycle. In this case, the actual creation of all elements will only occur on the command to fix the transaction (). When using transactions, the action will be either fulfilled entirely (all the elements of the reference book are created), or not fulfilled at all (in the case of any failure there will be no new item, everything will remain as before the transaction starts). Transactions are widely used in the banking sector. After all, no one wants, when sending money, they were safely written off from your account, but because of any failure did not reach the addressee.

SprSotron \u003d Reference books. Staff ;
Stattail();

For nom \u003d 1 to 100 cycle
New \u003d springs. Create element ();
New. Name \u003d "New" + line (NOM);
New. Write down ();
EndCycle;

Fixing Transaction();