Applications before working with hierarchical agents. The operator "in the hierarchy" in the 1s entry is written in the hierarchy in the list

Golovna / Zakhist

We want to discuss everything with you functions of the movie 1s, as well as constructions of movie queries. What is the function of the design? The function is activated with the arms and their possible parameters, and the design is written without the arms. Crazy all designs and functions of mov 1c queries to slow down the process of obtaining data that is both flexible and richly functional. These functions and designs are completely powered, and the functions are also completely powered.

Functions of movies 1s

Fragments of a wise description 1c movie function It is covered much earlier, below the description of the design, we decided to begin to look at the functions themselves. Now let's take a closer look, describing its meaning, syntax and application, and so on:

1. Function DATE HOUR- This function creates a constant field of the “Date” type.

Syntax: DATE HOUR(<Год>,<Месяц>,<День>,<Час>,<Минута>,<Секунда>)

Vikoristan butt:

2. Function Variety- Rotates the difference of two dates in one dimension (day, month, day, year, year, second). The value is transferred to the parameter.

Syntax: REALIZEDDAT(<Дата1>, <Дата2>, <Тип>)

Vikoristan butt:

Request.Text = "VIBRATI | REZNESTDAT(DATETIME(2015, 4, 17), DATETIME(2015, 2, 1), DAY) | YAK Kolvodniv";

3. VALUE function- specifies a constant field with a pre-valued record from the data base, it is also possible to remove an empty message of any type.

Syntax: VALUE(<Имя>)

Vikoristan butt:

Request.Text = "VIBRATI //zoom element | VALUE(Dovidnik.Currency.Dolar) YAK Dollar, //empty message | Physioba) YAK PhysOblichya, / / zoom rahunok |

4. VIBIR function- We have before us an analogue of the design that is corrected in the code, just as it is corrected in 1C queries.

Syntax: VIBIR KOLI<Выражение>TODI<Выражение>Otherwise<Выражение>KINETS

Vikoristan butt:

Request.Text = //if the amount is more than 7500, then there may be a reduction of 300 rubles, //so the function is used //turns the amount - 300 //in the same way, simply write the amount "VIBRATI | VIBIR | WHEN PM nya.Suma > 7500 | TODI TCHNadkhodzhennya.Suma - 300 |

5. Function VIRASITI- allows you to express a constant field with a song type.

Syntax: VIRAZITY(Field Name YA Type Name)

Vikoristan butt:

Another option is to use the VARIATE function in fields of mixed types, where do they get closer? The simplest example is the “Registrar” for any register. Then we may need to check the type with the registrar? Let's take a look at the situation, if we select the "Number" field from the registrar, from which table will the number be entered? The correct answer is from everyone! Therefore, in order for us to perform the procedure, we must specify an explicit type for the additional function of VIRASITI

Vikoristan butt:

Req.Text = "VIBRATI | VIRASITI(Nomenclature.Commentary YAK Row(300)) YAK Commentary, | VIRASITI(Nomenclature.Sum YAK Number(15,2)) YAK Sum |Z | Dovidnik.Nomenclature YAK

6. ISNULL function(alternatively spelled NULL) - if the field is of type NULL, it is replaced by another function parameter.

Syntax: Є NULL (<Поле>, <ПодставляемоеЗначение>)

Vikoristan butt:

It is also important that the NULL type must be replaced FIRST as a value, because Equating the type NULL always leads to nonsense because you equate NULL with NULL. Most often, NULL values are added to the join table (all types are joined except the internal one).

Query.Text = //Select the entire nomenclature and the surplus according to it //if there is a surplus in any nomenclature there will be no field, then the field //NULL will be replaced with the values 0 "SELECT | Nom.Posylannya, | Zalishok |Z |Dovdnik.Nomenclature YAK Nom |Live Z'ednannya RegisterAccumulation.ProductsInWarehouses.Suspended YAK ProductsInWarehousesZalishki |PZ (ProductsInWarehousesZalishki.Nomenclature = Nom.Posilannya)";

7. REPRESENTATION function- Allows you to enter the given fields when asked.

Syntax: REPRESENTATIVE(<НаименованиеПоля>)

Vikoristan butt:

Query.Text = "VIBRATI | REPRESENTATION(Viln_ZalishkiZalishki.Nomenclature) YAK Nomenclature, | REPRESENTATION(Viln_ZalishkiZalishki.Warehouse) YAK Warehouse, |

Designs for mov 1s

Most of all we looked at you functions of the movie 1s, now the time has come to take a look designs for mov zapitiv 1s, the stench is no less important than the roots, let's get started.

1. Design POSILANNYA- is a logical operator for checking the type of message. Most often it occurs when checking the field of the folded type for a specific type. Syntax: POSILANNYA<Имя таблицы>

Vikoristan butt:

Query.Text = //as the type of value of the registrar is Pributkov's document, //then it will be filled in with "Product availability", aka "Product sales" "VIBRATI | VIBIR | KOLI Zalishki.Registrar POSILANNYA Document.""Vitrata"" | KINETS YAK ruhu | Z | Register Accumulation.

2. Design МІж- This operator checks and enters the values of the range indications.

Syntax: MIZH<Выражение>І<Выражение>

Vikoristan butt:

3. Design B and B ІЄARCHY- check whether the values are in the list that is being transferred (as arrays, tables of values, etc. can be transferred to the list). Operator B ІЄARCHY allows you to view the hierarchy (example of the Vikoristan Plan Rakhunkiv).

Syntax: IN(<СписокЗначений>), IN ІЄARCHІЇ(<СписокЗначений>)

Vikoristan butt:

4. CONSTRUCTION SPECIFICALLY- This function allows us to rotate a row from a row template.

Syntax: SUPERBLY"<ТекстШаблона>"

Row pattern options:

% - Sequence that can be filled with as many symbols as possible.

One symbol is enough.

[...] - be it a single symbol, or a sequence of symbols from the square arms located in the middle. The re-arrangement can be set to ranges, for example a-z, which means the last character that goes before the range, including the ends of the range.

[^...] - either a single symbol, or a sequence of symbols from the list in the middle of the square arms, as well as those listed behind the cross sign.

Vikoristan butt:

5. Design PERMITTED- This operator allows you to select records from the database where you have the right to read. These rights cannot be adjusted on the level of records (RLS).

Syntax: ALLOWED to be written after the keyword VIBRATE

Vikoristan butt:

Request.Text = "VIBRATI PERMISSION | Counterparty.Posilannya |Z | Dovidnik.Counterparty YAK Counterparty";

6. Construction of the Size- allows you to select entries that have daily repeat entries.

Syntax: ІЗНІ is written after the keyword VIBRATE

Vikoristan butt:

Request.Text = // selects records for which rights the reader has "VIBRATIY RUZNI | Counterparties. Name | Z | Adviser. Counterparties YAK Counterparties";

Also, the construction of the RIZNI can be compared with the operator ALLOWED and other operators.

Vikoristan butt:

Request.Text = // selects different records for which rights the reader has "SELECT PERMISSIONS | Counterparties. Name | Z | Advocate. Counterparties YAK Counterparties";

7. Design PERSHI- selects the number of records specified in the parameter from the query result.

Syntax: PERSHI<число>

Vikoristan butt:

Request Text = // Select the first 4 numbers of the VMD from the document "VIBRATE THE FIRST 4 | Numbers of the VMD. Posilannya | Z | The document.

8. Design for change- allows you to block a table, which also works in transactions (especially automatic blocking).

Syntax: FOR THE MIND<НаименованиеТаблицы>

Vikoristan butt:

Capt.Text = "REVER |

9. Construction ORDER BY- puts the data in order according to the singing field. Since the field is a message, then when installing the ensign Auto-arrangebath If the ensign is entered, then the messages will be sorted by the seniority of the mailing address in memory.

Syntax: IN ORDER<НаименованиеПоля>Auto-arrangebath

Vikoristan butt:

Request.Text = "VIBRATI | Vilni Zalishki Zalishki. Nomenclature YAK Nomenclature, | Vilni Zalishki Zalishki. CHIVANNYA";

10. Design GROUP BY- it is used to group the rows behind the singing fields. Numeric fields are liable to be violated by any aggregate function.

Syntax: GROUP BY<НаименованиеПоля1>, .... , <НаименованиеПоляN>

Vikoristan butt:

Request.Text = "VIBRATI | GoodsInWarehouses.Nomenclature YAK Nomenclature, | GoodsInWarehouses.Warehouse, | warehouses.Warehouse";

11. Design MAYUCHI- allows you to set the aggregate function of the data collection brain, similar to the DDE design.

Syntax: MAYUCHI<агрегатная функция с условием>

Vikoristan butt:

12. Design INDEXUVATI BY- The search field is used for indexing. The search for indexed fields will be completed before indexing. You can also vikorize virtual tables.

Syntax: INDEXUVATI BY<Поле1, ... , ПолеN>

Vikoristan butt:

13. Design DE- allows you to influence the mind, be it the fields of choice. As a result, the records that only satisfy the mind are wasted.

Syntax: DE<Условие1 ОператорЛогСоединения УсловиеN>

Vikoristan butt:

Request.Text = //selects all entries from any CompensationExcess<>0 і //AmountForRozchCompRemaining > 100 "VIBRATI | CompensationRRemains.Counterparty, | CompensationRRemains.Ditina, | CompensationRRemains.CompensationZashok, | CompensationRpostach. Statti YAK CompensationRPostacs |DE |Com pensionRPOremains.CompensationExcess<>0 | І CompensationRPORemains.AmountForRozchCompRemaining > 100" ;

14. Design of the bag... BEHIND THE COVER- the design specifies the fields that the pouches are affected by and the aggregate functions that are set to the pouch fields. When there are no pouches on the skin field after the design of the pouch, a grouping of data is carried out. The unobtrusive construction of the cover, and the structure will also ensure additional grouping. The butt of the result will be washed down and lowered.

Syntax: BAGS<АгрегатнаяФункция1, ... , АгрегатнаяФункцияN>PZ<ОБЩИЕ> <Поле1, ... , ПолеN>

Vikoristan butt:

Request.Text = "VIBRATI | Rozrahunki.Agreement to Counterparty.Type of Contract YAK TypeDogovir, | Rozrahunki.Agreement to Counterparty YAK Treaty, | Rozrahunki.Counterparty, |

The small circle circles the groupings that were created during the final search, most notably going to the BACK section, and the other to the Contract to Counterparty to Contract field.

What is Dovdnik 1s and why is it needed? The adviser saves mental and permanent information, then. The information may not change in the interim. For example, the “Nomenklatura” agent is responsible for the overflow of goods that are sold or produced. Likewise, the witness can take revenge on the faceless authorities, which describes the element of the witness.

If you take it for the sake of becoming a human being, then here is a list of changes and not changes, so for this purpose the overflow is better suited.

Having created a new document, we will certainly begin the picture.

Let's take a look at all of your bookmarks.

Main

Here you indicate the name (identifier in the database) and synonym (name of the client advisor). It is not necessary to make a comment that can explain the role of the speaker or describe his features.

Hierarchy

On this tab you can adjust the depth of insertion of the addendum elements. For additional purposes, you can manually separate and refine the settings based on certain criteria. For example, “Shafi” products are in one group, and “Stoli” products are in another. In due course, the attorney will represent list of elements. If you put the ensign of the 2nd Archarchical Advocate, the skin element can be subordinated to another element (group). Below are options for adjusting this bookmark and changing the display in the user mode.

Type of hierarchy:

Hierarchy of groups of elements

With this option, nested elements can only be contained in groups (folders).

Here, as you can see, all elements of that group have new icons, and any element can have a contribution.

Place groups on the beast

When this proportion is established, the groups will always be in order, otherwise they will be rearranged in sorting order, for example:

Exchange of several equals of the hierarchy

Since there is no ensign here, the contribution is not interchanged.

Once the ensign is installed, the number of ranks can be indicated below.

Vlasniki

On stock Vlasniki Other agents may be appointed entirely, up to certain purposes. The scheme of the posts of light advisers is similar to the scheme of the posts of a hierarchical adviser, only here, as a father, another adviser appears and is called the leader. In typical configurations, a good idea is to subordinate the “Agreement” agent to the “Counterparties” agent, because You cannot enter into an agreement that is not binding on any counterparty.

The field "List of authorities of an advisor" indicates a list of advisors that contain elements of this advisor.

Below in the “Ordering order” field it is indicated how the elements of this guide will be ordered.

How to recognize a programmatic agent that is hierarchical or not

Why do you need to go to the metadata?

CeІєерхічныйАвідній \u003d Metadata.Авідні.С‚С‚С‚С‚С‚С‚СІєrarchіchny;

Continued to follow...

Dovdniki 1C is a specialized metadata tree object that serves to save static information of a dovdnik nature. For example, in typical configurations you can see the following types: , nomenclature, equipment, main features, etc. The information provided by the advisers will not change. The investigators began to investigate practically all objects in the area as a result of the evidence and evidence information.

Below we will look at the adjustment and design of the appendix from the configurator on the application of the appendix “Nomenclature”.

Basics tab

On the “Basics” tab, the name, synonym, representation of objects, and description of the purpose are indicated.

Tab “Doctor’s hierarchy”

Here the hierarchical nature of the adviser is established.

There are two types of hierarchy in 1C 8.3 - group of elements"ta" elements". It turns out that the first type may have a folder (folder), while the other type may have an element.

“Arrange the groups for the beast” - the ensign indicates for the display of groups in the list form.

Also, in settings, you can divide a number of groups in the hierarchy of the leader into separate settings.

“Vlasniki” tab

The advisor may be subordinate to another advisor. From the looks of the configuration of 1C 8.3, the “Vlasnik” props becomes a simple element. An example of such a connection of providers in the standard configurations “Nomenclature - Units of Variation”, “Counterparties - Contracts of Counterparties”.

The author of the document may be the following metadata objects: , .

"Tribute" tab

Watch 267 video lessons from 1C free of charge:

The most important tab from a programmer's perspective. It contains the details of the agent.

The Adviser contains a set of standard details that are not edited by the 1C 8.2 program; a list of them can be obtained by clicking the “Standard Details” button:

I'll dig into the skin details:

Tse group— props with a Boolean type, which shows the group and the element. Only available to the hierarchical adviser. Bring back respect The important details cannot be changed in the 1C: Entrepreneurship mode.
Code- props, type of row (call row). The number is automatically assigned by the system. As a rule, insurance is obtained as (front code +1). I recommend using the row type itself, since sorting the numeric values will not be as easy as necessary. You can vikoristovat as a tribute to the author in the list and entry fields. As a rule, it is necessary to search for an element under the hour of introduction in a row. If you need to select the Code field, enter zero at the bottom of the row.
Name- Props, obligatory to filling, ordinary type. The maximum length of a row is 150 characters. You can vikoristovat as a tribute to the author in the list and entry fields. As a rule, it is necessary to search for an element under the hour of introduction in a row. If you need to select the Name field, enter zero at the bottom of the row.
Father- Props that may be the type of Dovdnik Posilannya.<ИмяТекущегоСправочника>. Only accessible to the hierarchical adviser. Points to the great father in the hierarchy. If an element or group is found in the root of the Adviser, the value Adviser is indicated.<ИмяТекущегоСправочника>. Empty Posilannya.
Vlasnik- Posilannya on the element-vlasnik of the flow element (group) of the dovdnik. Available only to a subordinated 1C provider.
Vidalennya badge- Props with boolean type. Indicates that the remote icon is displayed in the system. The designation for the deleted element is considered inappropriate for vikoristannya, the protea on the new one may be lost for old documents.
Posilannya- Row type field. For whose details a unique object identifier GUID is saved. Those in the system that are visually depicted under the name “message” are merely a manifestation of the object. Cannot be changed.
Zooming— a Boolean type that represents an element that is intelligible, and above all. Cannot be changed.

The “Data” tab also indicates the data of the adviser in the system; prior to version 8.2.16, the data could have no Code or Name. In new versions of the platform (starting with 8.3), submissions can be described independently in the manager module with the help of the “Processing of Submission Processing” section.

“Numbering” tab

Here the adjustment of the agent for numbering is indicated. It is recommended to use the autonumbering itself. Uniqueness control is a rule that helps if you need to create a unique code. If you try to record an identifier element with a non-unique code, you will see the notification “The identifier code has become non-unique” in 1C.

A series of codes indicates how to number the advisor, you can enter the numbering of the advisor in the context of the leader. For example, the counterparty “Rogi i Kopita” has its own numbering of agreements - “1, 2, 3” or so.

Forms tab

The forms of the witness are described here. If the configuration is launched in both the basic and hardened modes, then there will be two tabs with forms behind them: “main” and “additional” - for the basic and hardened programs.

On this side, the authority of the witness is important - ““. This is a very manual function of 1C 8, which allows you, when filling in the data in the entry field, not to go to the editor, but to type your name, code, etc. and select the required item from the list. It looks like this:

Tab "More"

On the tab you can get quick access to the main modules of the browser – the object module and the manager module.

On the page you can also find a list of the important elements of the browser. Elements that cannot be removed from the Entrepreneurship regime. You can access all the necessary elements from the configurator directly, by name, for example: Authorities.Nomenclature.Service.

This tab also indicates the blocking mode - automatic or blocking. The search for full-text search, as well as additional information about the adviser, is available in the 1C: Enterprises mode.

The “IN HIERARCHY” design in 1C:Enterprise 8.x queries allows you to select ordered elements of a hierarchical configuration object according to a given selection. Today, the article will look at its impact on productivity, as well as on other DBMS platforms and its impact on productivity.

Vikoristannya

Let's take a look at a simple butt of the vikoristan design "IN ІЄARCHІЇ". Before the end of the current campaign, the ordered elements of the hierarchical indicator “Goods” will be removed for the transferred value of the change “Posylannya”.

The test database has the following test data:

Of course, not all of the witness’s records are shown in the image. The screenshot shows the structure of data storage for the hierarchical adviser. The guide table saves 10 groups of the upper level, each of them contains 5 nested groups with 200 elements each.

Let's turn to the test question. The parameter “&Posilannya” is transferred to the group “Group - 1” (excellent screenshot above). Then the result of the search will look like this:

As a result, turn the message to the top group itself (passed as a parameter), and enter the group entries with their elements. Thus, the vicoristic construction “In the Hierarchy” allows you to manually remove hierarchically ordered data.

Syntax of mov queries 1C:Enterprises and classic SQL very similar in these moments. However, for the expression "B ІЄARARCHY" there is no analogue in the language of SQL queries, as, for example, for the expression of platform language "B" there is a similar SQL operator "IN". This is why the platform works from the DBMS with the choice of this operator.

Behind the Lashtunki

Come on, let's see. For the butt of vikorystvutimemo, before writing, it will be written before the author “Products”. We will analyze these platforms for two situations:

As the parameter “&Posylannya” is passed to the upper level group “Group 1” (as we have already done).
The parameter is sent to the group "Group 1 - 1", placed in the upper level group "Group 1".

Now in order. In the first case, the platform contains the following actions on the SQL server:

1. The SQL statement will now be completed by extracting the message from the agent group passed as a parameter, and all its subordinate groups. The result is located in the hourly table "#tt1".

2. At another stage of the conversation, a new question is completed:

The screenshot contains detailed comments on the text of the SQL query. In short, this command allows you to select ordered elements for groups that appear in the time table. Food is running out: “Are the girls going to finish their wedding?” Here the answer is simple: the first step is to remove the subelements for the groups of the first level, which are already located in the time table (section 1). Then another query selects subordinate elements for subordinate groups of another level. There is still one group of leaders on the third level of the hierarchy, which will no longer be resolved.

In our case, the other request is probably an empty result, the fragments for the records, which are located on the 3rd level of the hierarchy, have no subordinate elements (there is no same group there).

3. To extract the end result of the query, the platform forms the following SQL query:

The result of the query itself can be further processed by the algorithms of the installed platform. Thus, the records in the clock table "#tt1" are selected for the purpose of installing a selection from the indicator table "_Reference41".

4. Finally, the 1C:Enterprise 8.x platform deletes the time table “#tt1”, and as a result there is no longer any victory.

At this point, the process of visconning the operator “IN ІЄARCHІЇ” is completed. Let me remind you that we looked at the sequence of actions on the SQL server of Vikonana, when we sent messages on the platform side to the top-level group “Group - 1”. How will the platform behave when the parameter “&Posylannya” is transferred to a group of another level “Group - 1 - 1”? Everything will be in a similar order, except for the current moment: above all, at another stage of the SQL querying platform, it was written that it will be used to remove subordinate elements for the following two "Group - 1 - 1" is not so. It will be asked only once.

On the right is that a number of requests for the content of minor elements lie in a number of groups of the hierarchy. In other words, if one group wants to be located on the equal hierarchy of elements, then it will be defeated ask from point 2.

Productivity boost

Incorrect use of any operator in a sequence can lead to suboptimal system performance. It looks like the operator “IN ІЄARCHY” is not to blame. It is necessary to be careful, however, because the algorithm for connecting SQL queries to the database becomes more complex and thus increases the impact on the DBMS server.

I’ll give an example of a non-optimal question that can lead to the most common names of these dubious inheritances:

VIBRATI Products. Posilannya Z Dovidnik. Tovari YAK Tovari DE (Products. Posilannya V ІЄARARCHІЇ (& Posilannya) ABO Tovari. Posilannya V ІЄARARCHІЇ (& Posilannya1) ABO Tovari. Posilannya V ІЄARARCHІЇ (& Posilannya2) )

As you might guess, this leads to the formation of impersonal SQL queries, which causes a decrease in the productivity of the information system.

Get started!

Visnovki robiti you. I will also say that the operator “IN ІЄARARCHІЇ” is considered a platform for a data composition system, if in mind there is a selection of “U GROUP”, “U GROUP WITH LIST” and others. I don’t think it’s easy to explain that with incorrect manipulations, developers can install a very complex selection and push the search to the 1C server and DBMS many times. Let's change the settings only for the experienced traders.

That’s right, when writing power mechanisms, pay attention to the operator “IN ІЄARCHІЇ”. Very strong on one side and careless on the other.

This section has applied the most typical tasks when working with hierarchical agents.

Separating the elements of a hierarchical adviser from a subordinated given group

To remove the lighter elements of the hierarchical adviser from our queries, the design was transferred to the hierarchical one. Butt of the vikoristannya U ІЄARCHІЇ:

VIBRATE
Nomenclature.
Nomenclature.PurchasePrice
Z

In this application, all records of the Nomenclature that are in the &Group group will be removed, including itself, the subgroups and the elements that belong to the subgroups.

If we are deprived of elements and groups that are directly related to the task of the group, then we can remove such elements by placing our minds on Batko’s field. Butt:

VIBRATE
Nomenclature.
Nomenclature. Name YAK Name,
Nomenclature.PurchasePrice
Z
Dovidnik Nomenclature YAK Nomenclature

DE
Nomenclature.Batko = Group

This will ask you to select the groups and elements that are found in the subordinate group from the &Group.

Checking the presence of subordinate elements in the indicator element

To verify the authenticity of the subordinate entries of the evidence element, you can use a query similar to the one presented:

In the application of which the element is sent, for which it is necessary to verify the presence of child elements, the “Father” parameter is recorded in the field. After this question, it is necessary to check the result completely. If the result is not empty, the records are ordered. Otherwise – no. Butt:

Yakshto Refill.Viconati().Empty()Todi
Report("There are no entries");
Otherwise
Show("Records");
KinetsYakscho;

Removing all the elements

Our products do not have special methods for removing all battery elements. For viconics, it is possible to quickly produce hierarchical results, while removing hierarchical results is optimized for producing results from a large number of records, and is not very effective for removing batches of a single element. For more efficient removal of all the batch records of an element, it is recommended to sort through the batch batches in small portions. Butt:

ExactElementNomenclature = ElementNomenclature;

Until the Truth Cycle
Request.InstallParameter("Flow Element Nomenclature", Flow Element Nomenclature);
Result = Query.Viconati();
Yakshto Result.Empty() Todi
Interrupt;
KinetsYakscho;
Select = Result. Select();
Vibirka.Offensive();
For ColumnNumber = 0 For Result.Columns.Quality() - 1 Cycle
ExactNomenclatureElement = Vibe[ColumnNumber];
Interrupt;
Otherwise
Povidomity(CurrentNomenclatureElement);
KinetsYakscho;
KіnetsCycle;

Yakshto ExactElementNomenclature = Dovidniki.Nomenclature.EmptyPosylannya() Todi
Interrupt;
KinetsYakscho;
KіnetsCycle;

In which application, all the information for the message recorded in the change Element Nomenclature is displayed in the service notification window. Each cycle has 5 batches of sent messages.

Since the number of sources in the adviser is limited and small, it is possible to remove all the sources with one query without a cycle.

The appearance of the hierarchical adviser in the world

To identify the hierarchical adviser from the savings of the hierarchy, it is necessary to use a formula similar to the current one:

VIBRATE
Nomenclature.
Nomenclature. Name YAK Name,
Nomenclature.PurchasePrice
Z
Dovidnik Nomenclature YAK Nomenclature
IN ORDER
Name: Hierarchy

This query selects all records from the editor and creates an order hierarchy. The result will be the ordering behind the name of the hierarchy.

In order for the groups of the speaker to be located more than elements, it is necessary in this sentence to replace the proposition ORDER BY on the step:

IN ORDER
Nomenclature.CeGroup ІЄARCHYYA,
Name

The result, as before, will be the ordering behind the hierarchy, the groups will be divided into more elements.

It is also possible to replace the proposition ORDER BY with the proposition auto-order. And here the result of the ordering will be consistent with the adjustments of the interpreter, then. If it is stated in the document that the guilty groups will be paid more for the elements, then they will be paid more.

It is also possible to create a hierarchical structure of the adviser with the help of bags.

VIBRATE
Nomenclature.
Nomenclature. Name YAK Name,
Nomenclature.PurchasePrice

Z Dovidnik. Nomenclature YAK Nomenclature

DE
(Nomenclature.TseGroup = FALSE)

ORDER BY Name

Removing pouches from hierarchy

To remove pouches from a hierarchy, you must enter the keyword HIERARCHY in the BAGS proposition after entering the field for which pouches will be allocated. An example of the "Nomenclature Turnover" with the content of bags from the hierarchy:

VIBRATE

Z

Nomenclature ІЄARCHY

As a result of this request, bags will be released not only for the skin category, but also for groups that are subject to the same category.

In case there are no need for pouches by elements, but only need pouches in groups, we need to use the design of a TILKA HIARCHY in the pouches. Butt:

VIBRATE
Appearance of NomenclatureTurnover.Nomenclature YAK Nomenclature,
The appearance of the Nomenclature of Turnover. Nomenclature.
AppearanceNomenclatureTurnover.QualityTurnover YAKKilkistityTurnover
Z
Register Accumulation. The appearance of the Nomenclature.
BAGS BAG(KilkistObig)
Nomenclature TILKI ІIRARCHY

As a result of this query, there will be sub-records without nomenclature groups.

Functions of movies 1s

Designs for mov 1s

Main

Hierarchy

Hierarchy of groups of elements

Place groups on the beast

Exchange of several equals of the hierarchy

Vlasniki

How to recognize a programmatic agent that is hierarchical or not

Basics tab

Tab “Doctor’s hierarchy”

“Vlasniki” tab

"Tribute" tab

“Numbering” tab

Forms tab

Tab "More"

Vikoristannya

Behind the Lashtunki

Productivity boost

Get started!

Editor's choice