1C 8 CCD custom settings. Selects in reports

We looked at the settings of the reports implemented on the basis of the SCD. Now we will analyze more subtle and detailed settings for the report options. The "Advanced" window of the report option settings is called by the "More" command - "Other" - "Change Report Option".

The change window of the report option is divided into two parts:

1. Report structure.

2. Report settings.

The section of the report version structure is similar to the Structure tab of the standard report settings. Assignment and configuration of groups is considered in detail in Part 1 of Articles.

Table of the status of a report option, except directly columns with groups, contains several additional columns:

The report option settings section gives the user wide opportunities for configuring the report to their needs. It almost completely coincides with the standard report settings discussed in part. 1. Consider all tabs of the section and mention differences.

The settings section consists of the following tabs:

1. Parameters. Contains the parameters of the CCD accessible to the user.

The CCC parameter is a slight value used to obtain a report data. It can be a value of the condition for selecting or checking data, as well as an auxiliary value.

The parameter table is presented in the "Parameter" format - "value". If necessary, you can change the values \u200b\u200bof the parameters. Pressing the "Custom Settings Item Properties" button opens up user element settings.

In this window, you can choose whether the item will be enabled in user settings (i.e., the user is visible when setting up a report), set the element representation and edit mode ( fast access In the report header, the usual report and inaccessible settings).

The properties of the user settings element also have grouped fields, fields, selections and conditional design elements.

2. Custom fields. Contains the fields that the user itself is formed on the basis of the data selected by the report.

The user can add two types of fields:

New field choice ...
New field expression ...

Selection fields allow you to calculate the value on a given condition. The selection field editing window contains a header field and a table in which the selection, value and representation of the field are specified. The selection is a condition, depending on which the desired value will be substituted.

For example, we calculate the assessment of the number of sales. We will assume that if less than 10 units of goods sold, they sold little, and if more than 10 units are a lot. To do this, set 2 the values \u200b\u200bof the calculated field: the first will be with the selection "The amount of goods is less than or equal to" 10 "", the second with the selection "The amount of goods is larger than" 10 ".

Expression fields allow calculating the value using arbitrary algorithms. They can use the functions of the query language and the built-in programming language 1c. The expression field editing window contains two fields for expressions of detailed and final entries. The final entries are groupings configured in the "Report Structure" area, they need to use aggregate functions ("sum", "minimum", "maximum", "quantity").

For example, we calculate the average percentage of the discount. The average percentage of the discount is calculated by the formula: [Sales amount without a discount] - [Sales amount with a discount] / [Sales amount without a discount]. It must be remembered that the sales amount without a discount can be zero, so we use the selection operator to check. We obtain the following expressions:

· For detailed records:

Choice

When [Sales Amount without Discount] \u003d 0

Then 0

Otherwise [Sales amount without a discount] - [Sales amount with discount] / [Sales amount without a discount]

the end

· For final entries:

Choice

When the amount ([Sales amount without a discount]) \u003d 0

Then 0

Otherwise, the amount ([Sales amount without a discount]) - Amount ([Sales amount with a discount]) / Amount ([Sales amount without discount])

the end

As mentioned earlier, in the expression of the final entries we use the aggregate function "Amount".

3. Grinded fields. Contains the fields by which the result of the report option will be grown. Grinding fields are configured separately for each of the groups, but you can set common grouping fields for the report option, if you select the root of the "Report" in the structure. You can add a field from the report result, a user field or select the auto field, then the system will select the field automatically. Also, this tab allows you to change the procedure for grouping fields.

4. Fields. Contains fields that will be displayed in the result of the report option. Fields are configured separately for each of the groups, but you can set common fields for the report option if you select the "Report" root structure in the structure. You can add a field from the report result, a user field or select the auto field, then the system will select the field automatically. Also, this tab allows you to change the order of fields.

Fields can be grouped to logically select any part of the report or set a special arrangement of columns. When adding a group, the "Location" column becomes active and allows you to select one of the location options:

Auto - the system has fields automatically;
Horizontally - fields are horizontally;
Vertically - fields are located vertically;
In a separate column - fields are located in different columns;
Together - fields are located in one column.

5. Selection. Contains the selections used in the report version. Setting up the selections was considered in detail in part 1 of this article. Selects are configured separately for each of the groups, but you can set general selection for the report option, if you select the "Report" root structure in the structure.

6. Sort. Contains the sorting fields used in the report version. Setting up the sorting fields was considered in detail in terms of this article. Sorting is configured separately for each of the groups, but you can set common sorting fields for the report option, if you select the "Report" root structure in the structure.

7. Conditional design. Contains the conditional design elements used in the report version. Conditional registration was considered in detail in terms of this article. Conditional design is configured separately for each of the groups, but you can specify common conditional design elements for the report option, if you select the root of the "Report" in the structure.

8. Advanced settings. Contains additional settings Report decoration. Allow you to choose common appearance Report, location of fields, groups, details, resources, results, set the chart settings, control the output of the header, parameters, and selection, determine the position of the resources and fix the header and the grouping columns of the report version.

In conclusion, I would like to note that the report settings can not only be saved as a report version, but also to upload to the file ("More" - "Save Settings"). To download, select "Load Settings" and select the saved file. Thus, we can transmit the settings of the report option between different bases that have the same configuration.

Based on this, we can summarize that the user can not only configure the report to his needs, but also save its settings and use them later if necessary.

I suppose there is no need to tell what the CCD is, the settings linker and in general the entire set of objects designed to work with the CCD. The main directions of use, not counting the cider actions in the code, these are dynamic lists and reports, and in both cases "behind the scenes" there remains very significant functionality. We often do not even think about what the logic of the behavior and the relationship of all participants in the process, because Usually we solve enough simple tasks or rely on the default platforms. But, where there are defaults, there is an internal logic, a "bearish service" 1C, to overcome the fruits of which is sometimes difficult to achieve the desired effect and is unclear, and it is enough just to use the toolkit.

Those who wish can skip part 1-4 and immediately go to the examples.

I will try to stay at work slightly in more detail. selected SCD For the case of their applications in the reports. I believe, behavior in dynamic lists, for a number of reservations, will be close. So, selection in reports, a bit of theory and then specific examples.

Used SP 8.3.6 and above, sections of ITS (paragraph 10.3.7.5, etc.), the book "Professional development in the 1C-Enterprise system 8" (Kazan, 2012, the second volume). In the book, E.Hrustalava, there was nothing intelligible on this topic.

Part 1

The configuration of the settings, as is known, there are collections "Settings", "Fixed settings" (hereinafter "FN") and "Custom Settings" (hereinafter "Mon"). The report may have several options, while the relationship between the option, N, Mon and FN is very peculiar. Also, we will not forget about the source of available settings, and its "progenitor", which the scheme itself usually has its own default settings.

* Settings - settings created in the configurator mode and changeable in the edit mode of the report version;

* Custom-intensified - settings that change the user in "1C: Enterprise" mode is purely interface;

* Fixed-in-section - those settings that are set from the embedded language, incl. implicitly set by the system. This property includes selection values \u200b\u200bthat are transmitted to the form with its parameters ("Selection" structure).

Settings and FN are similar to the device and have a collection of "Selection" type "Selection of data layout" type, available for changing the composition at any time of the existence of the report. At the same time, the settings are available for an interface change through the editing of the option, and the FN is not available at all. Mon, in turn, this is a "porridge", where the equal elements can be both "selection" and individual objects of the "Data layout element" (so-called. Nested object). Despite the presence of appropriate methods, it is impossible to change the composition of the collection of the PN elements, if this is the name of the reported, and not made "from scratch" by the designer - 1C will report that "the Collection of Custom Settings cannot change its composition, as it is related to the layout settings data. " It is said: "The property is not available for recording using the built-in language.", But as we will see later, you can influence the Mona. "Porridge" objects has internal connections - It is checked for consistency of conditions in the formation of a report, and when changing the composition. We read to ITS: "The elements that themselves are noted as custom will be added. For example, the selection element will not be placed in the user selection, which is marked as a user. The elements containing custom elements will not be added. For example, a group of conditions will not be added if the elements marked as custom are present in this group. For nested items, the Modatization Property is not analyzed. They are added or not added together with parent elements. " Thus, the "seniority" of objects is inexplicable. At the same time, it is possible to obtain an effect when the interface will allow you to specify contradictory selections for the option and its mon, as well as inside the PN.

It would seem that the "older" is an option. But clicking on "More" / "Change option" and confirmation of changes in the form that matches the form event handler , while the selection appears in the "Basic" panel on the form called from "Settings ...", and appears on the form of a report, but it is not shown on the "Selection" tab; Moreover, either it appears immediately and on the main form of a report, and on the form of "settings ..." (if there is a "Turn on the Custom Settings" flag), or there is no there. But in any case, on the "Selection" tab of the form "Settings ..." it will not be. The difference between the "Main" tab of the "Settings ..." and the main form of the report is determined by the "Edit Mode" field (normal - only in "Settings", fast - also on the form of the report itself), but this, I think everyone knows everything. By the way, the values \u200b\u200bof "selection" and "fast" are not synchronized and can contradict each other, but "fast" on the form of a report and on the form of settings is rigidly synchronous. So, when editing the option, it itself becomes changed (but its ID and name do not change), but the PN remains not modified (that is, even if we are talking about them, i.e. about the flag of the inclusion of a particular element in Mon ).

Clicking on the "Select option ..." and confirmation of changes in the form that appears in the following order of events:

PrialozhvyadanianTanserver

Private-binding user-based equipment

At the same time, neither the variant nor pn is no longer changed. From here it is clear that the option and settings are related, then by no means directly.

Pressing the "Settings ..." and confirmation of changes in the form that opens only an event Private-binding user-based equipment (At the same time, the PN becomes changed, but the representations and key (if there were no) are not received; if "fast" is included for the elements of the "Selection" object, then besides the "selection", it is actually its elements as a field, i.e. . behaves similarly to nested items. These settings are saved when closed and restored at the next input to the form. The option it touches and does not change.

Pressing "More" / "Install Standard Settings" in the form of settings (as well as item " Standard settings"In the editing of the option) calls only an event Private-binding user-based equipment. In this case, the option becomes changed, but the PN is changing. If the option has been changed before this, it remains modified (neither the reset of the change flag, nor the reset of actually made settings happens).

Pressing the "Custom Settings Item Properties" in the structure tree on the form of the version add an "Selection" object, and it turns out empty and is not synchronized with the existing option selection and existing selection elements. The option does not change in any way.

From here Recommendation: If you need to set some selections in the configurator mode, so as not to bother with the code and so that in this case it was not in the version, but would be in the report interface - you should manipulate non-elements of the selection of the option, changing their properties, and the selection itself , buttons "The properties of the element ..." and "Custom Settings".

Adding something that appears in the settings to the PN, requires action in the code or interface, but the removal and cleaning of settings are affected by the Mona immediately and without any updates, for example:

Report. Support workers. Increases. Options. Elements. Operate ();

Before closing the report form, the system asks only if there were changes in the option. If there were changes in PN, they will continue automatically without any questions, and will also automatically try to apply in the next session of the report.

Notes:

Under a number of errors, the use of settings is first displayed a message about the problem, and then layout occurs, the event call and building a report. At the same time, the FN, if they were, are still ignored, and only the settings play the role.

When adding a selection on the form "Change option", it is done immediately with the "Turn on in Mon" flag, but I repeat, from the point of view of the built-in PN language remain unchanged.

Setting the variant value and setting the change of PN are not directly related, these are two different directions of change.

Mon, among other things, there are "Advanced Settings". I could not understand how and at what point they are filled. Although the report is the settings, "marked in the selection and conditional design" as a custom (according to the joint venture), but additional settings in all cases turned out to be empty. At ITS about this nothing.

Despite the approval in the joint venture, the PN is perfectly serialized in XML.

If you are included in the use and independent selection elements, and the selection itself, the report component is correct, but when you show the information about the installed selection in the final layout.

The default form of editing version of the report contains many interesting things, but nowhere does not work with FN and PN, and with the main settings it works more for reading (except that cleans the choice, order, sleep position).

Part 2

Working with settings and FN through their collection is almost always allowed, but it is important to remember that the essence of the "third level" changes. At the first level, there are always settings for the default CCD itself, they also appear implicitly in the source of available settings; At the second level, the settings of the option used. But here logic allows either "sweat" underlying instructions, or ignore them. But the work with Monobilities no longer provides, and subtle manipulations must be done with the help of special methods, and sometimes temporary auxiliary intermediary objects, for example:

Computer \u003d new folder-topled complex; // You can still for starters // Comp.Initialize (somecomposkrikstroika. Power Supplies to accessors ()); Comp.Rodajdavodstunctors (somecomposchchlorosser. Instruments); Somecommospherkashkinas. ZapjectsCompanicEnoxew (comp. UserSkitenkiy);

The layout of the settings has a method (), Which loads the values \u200b\u200bof the custom settings transmitted as the method parameter. Method Officers() Allows you to get a copy of current settings (taking into account custom settings). Method Download() Loads the adjusted settings to the settings layout (the user settings are also re-opened on the basis of the transmitted data, taking into account the presence of keys, see the example below).

Applying custom settings to the basic settings is performed in the method Officers() Linker settings. At the same time, the following actions are performed:

* For the types of elementbar, the contents of the elements are copied to the corresponding custom settings.

* For the types of selected printed items that are in the main settings and marked as inaccessible, remain unchanged. Elements from PN are transferred to the main. They are added to the end of the collection for selection.

* For the types of group television collectors, the use of the use property in the appropriate element of the main settings is set (based on the sign of the use of the PN element).

Part 3.

When forming the final setup, if you quote ITS, various settings are combined as follows:

* If any type of settings is entirely marked as a user, the resulting settings include Mon. At the same time, if any settings are marked as inaccessible, then these settings will be placed in the resulting settings from the properties of the folder settings. Involutions.

* If any kind of settings is noted as a user not entirely, but elements, then the elements marked as custom will fall into the resulting settings from the properties of the folder settings. Use the user-in-law, and the elements marked as inaccessible will be taken to the resulting settings from the properties of the folder settings. .

* Fixed settings are added to the resulting settings "As is". At the same time, the situation is unacceptable when the settings of the same name in the FN and PN are, for example, the selection with the same left value in the condition. I note that even the utter coincidence of all properties of these conditions is prohibited. Honestly, somewhat illogical.

I note that if any fragment of settings falls under the functional option and should be limited, the system operates "twich" - removes this fragment from everywhere, does not report anything, and with software manipulations relating to such a fragment, work out "Cool" - errors It does not give, but no effect from the code. However, perhaps different releases behave differently.

Part 4.

The expansion of the report form provides us with the parameters "FN" and "PN", but nowhere is it not recommended to fill them directly, transmitting to the form. As experiments have shown, without additional dances with a tambourine, the filling of these parameters is ignored - it is maintained when the linker is initialized during the opening process and upon receipt of previously preserved PN. It is recommended to work with the keys of the PN, according to which to receive them from the settings repository and then to open and use, and it is done automatically on the side of the report form, rather than the calling form.

The "Sourcing Supplement" parameter is automatically broadcast to the linker information already when creating a form on the server and cannot be override. Rather, it can, but the effect will only give it after full redefinition of the entire chain of related objects. Wherein Self-sufficient equipment() Until the end of the development of all the events, the form will return indefinitely.

I note that the parameters of the form are essentially not key, "stretch" their action into several events if the formation flag is set when opening. So, in the event Processing pervertercaused by opening and forming, the "Selection" parameter will be available, and with it, but by simply by pressing the user on the "Shape" button - no longer. This is due to the fact that all these events are worked out for one "visit" of the server if the formation is included in the opening, and only at their time, the control is transmitted to the client and is called Opening. At the same time, non-selection parameters, naturally, are lost.

The overall procedure for performing events when opening a form with the flag of the report formation when opening (somewhat larger than is described in "Prof. Development"):

Saviorserver

Frightened to the server

PrialozhvyadanianTanserver

Frightened user-to-keysserver

Prialo-propuser equipment

Private-binding user-based equipment

Processing perverter

Opening

At the same time, no option nor PN is modified if special efforts have not been made.

Part 5.

Now let's stop in more detail on the task of opening the form of a report with its construction and pre-specified selection. Brief information There is an ITS and in methodical recommendationsBut there is only the principle itself and not disclosed with subtleties. So, for the contextual call of the report, it is necessary to transfer it to the form "To form a receipt", equal to truth; and the "Selection" parameter containing the structure. The keys of the structure are the names of the fields of the CCD or parameters of the CCD, and the values \u200b\u200bare their values. Quoting the joint venture if there is sCD parameter With the name corresponding to the key name of the structure, the value will be set to it. If there is no parameter, but there is a field, the selection will be added to this field. At the same time, if there is a parameter and field of the same name, then the system is simply quietly ignored and does not install anything.

In "Prof. Development", an example of a change is given (i.e. interception and reconfiguration) Mon "On the fly" in the event Frightened user-to-keysserverwhere the argument containing the current Montego is transmitted. In fact, this is not always like this - for example, there are cases where the PN storage error in the previous session, or a contradiction between the settings, FN and PN will lead to the fact that the "Settings" argument will be empty. And what is the most interesting, fully reconfiguring it in this event will not be able, it can only be done "at the end" of the sequence of events, namely, in the event Processing perverter.

Let's see what we have before downloading Mon on the server.

For a simple case, when any elements are not included in the SCD, no items are included in the PN, the situation is as follows: settings are empty; FN - contain the right selection; PN contain empty selection. Formation works correctly, but from the user's point of view, the interface is contrary to the internships and discourages - the selection works, but not visible. Similarly, if in the settings of the embodiment settings, turn on the selection to the PN, the report is also built taking into account the selection, but the user also sees no selection.

Specify in the settings of the CCD in the prevention configurator (equal to empty values) and turn them on in mon. In theory, the FN must fill in the settings, and those - mon, but in fact we have: in the settings - the selection with the desired element, but the empty right value, FN contains the correct selection, and the mon - do not contain anything. In addition, in this case, the report will not be built, because The right selection value is empty, despite the value transmitted in the parameter.

Attempting to work with PN elements also does not result. For the PN element, it is possible to change the "use" flag and participation in the "fast". The selection value on the interface will be empty, the system will not display any errors. Similarly, an attempt to work with the selection of PN will also work, in the debugger, the right value will be visible as correctly filled, but you will not see anything on the interface. And the composition of PN, I can not remind you. Thus, additional tricks are required. For example:

& Nasserver Procedure InstallingFreasted Presentation Persons (Half Town) If not parameters. Speed \u200b\u200b("Selection") then refund following; If the parameters. Parameters. Number () \u003d 0 Then return to the end; RTIPEO \u003d type ("elementotor-free"); For each KIZ from the parameters. The collection of the Ripol cycle \u003d new half-blooded (KIZ. Welcome); // If (Tinch (KIZ. Type) \u003d Type ("array") or typny (KIZ. Type) \u003d type ("list of recognition")) and Kiz. Rights. Otherwise, RvidSravnias \u003d VictimsManComponovkydny. Ended; // Ranomotbor \u003d undefined; // We look if there is a selection in the benefits. Networks of RNUBOOEO \u003d undefined; // We look, whether there is a separate elementatubombound in use. In use. For each elnastra from the host. // It could be done outside the cycle, but it is necessary to sort out the uses. It is necessary for the sake of the elements ... Incited Tinch (Elnaist) \u003d RTPEO then // This is an element of the selection, there may be a lot of them, but we are not interested in not initialized or with the desired the field if the elnastr. Lowerness \u003d Ripol or Elnastr. Lowerness \u003d Undefined and revurdenEo \u003d undefined RunumberEo \u003d Elnaster; Ended; Ended; EndCycle; // If RanumberTebor.<>It is indefinitely then // it goes as a priority revumbreativeness \u003d undefined; For each ELLB of RanumberTebor.Elements Cycle If the ELLB.LOPE \u003d RPOLE is then revumbling / ECLB; Interrupt ended; EndCycle; If revumbling mellotabre \u003d is uncertain then revumbling meter \u003d revolutionar. Elements. Addly (RTPEO); RanumberEoisotor. Lowerness \u003d Ripol; Ended; revumbling euzotor .Vidservations \u003d RvidSravnaya; revumbling eeryzotor. Definition \u003d KIZ. revumbling. Use. USE \u003d Truth; // RNUKUEO. USE \u003d false; Invulsioned RanumberTolation \u003d Undefined and RanumberEo<>It is indefinitely then // put on the element of the RNUBEO. Lowerness \u003d RPOL; RunumberEo .Vidservations \u003d RVIDSRATION; RanumberEo. Maintaining \u003d KIZ. Appointment; RanumberEo. Using \u003d Truth; Ended; Round \u003d undefined; For each ELLB from the report. Support workers. Involcts. The collection. The elements of the cycle // is in a good way, there must be a recursive search! If typcoon (ELLB) \u003d RTPEO and ELLB.LOOS) \u003d RPOL then rant \u003d ELLB; Interrupt ended; EndCycle; If Rnumber \u003d uncertain then doubled \u003d report. Support workers. Inspectorate. Taking cliberer.Elements. Addly (RTPEO); RNUB. Lowerness \u003d Ripol; Ended; RNUB. Width \u003d RvidSravnias; RNUB. The definition \u003d kiz. Ranumber. Using \u003d truth; // EndCycle; Report. Support Spaces. Equipment. Potting. Electronts. Operate (); // otherwise it will say that the elements intersect / contradict the detailed

Call it most correctly like this:

& NASTER Procedure Procedure ProcessingProwed Server (Refusal, Checking Equipments) InstallingFreasted Substitutions (Report. Support Sacrics. Use the user-in-law); Extrudresses

Then, the contextual call, for example, from the form of a reference book will look like this:

& Complaint procedure Open report (command) If it is optimized (object. Link) Then OTB \u003d New Structure ("Link", Object. Link); // So the field is called in the CCD report of parameters \u003d a new structure ("selection, forming receptacle", OTB, truth); Open form ("Report. Report1.Form. Formount", parameters, formation); Ended; Extrudresses

Part 6.

If necessary, change the report settings in the process of working with it, incl. and at startup, and after opening, most right way It seems the change "from the beginning", i.e. from the settings of the CCD. The change in the CCC scheme is performed only with the object report (or foreign exchange), and not with the form data, and in itself does not change anything - the same thing remains in the PN, and the FN can remain empty. Therefore, depending on our tasks:

After execution

Report. Support Spaces. Clipputs (SKD.Nastpoumolech)

only the option varies, and nothing more;

After performing the reception given in paragraph 2 (using the "intermediary" and the method Loading userSetworks()

it triggers only if you reset the current interface interface. By themselves, they, when changing the option, will not change. In this case, the selection changes, but a new element collection is not added.

After execution

Formation. Create element formulator equipment (, modelsProductsCompon.

the platform is just quietly falling. Tested on several different releases. And the call to the display mode of the settings only for rapid it does not make sense - we did not affect their composition, so nothing will not change anyway.

And since we still need to fully change not only internal selections, but also the display on the form of a report and in the associated forms, it is necessary to change only the selection, or to act as follows:

& Nasserver procedure changed () Rail \u003d RequisitformAdrification ("Report"); OTB \u003d Railway.Shemacomponovkydny. Ravidnaestrokes. Pouring (0). Options. Option; EO \u003d OSB.Elements. Addly (type ("elementboratory")); EO. Lowerness \u003d New Poland-like ("Linksphanage.power1"); EO .Vidservations \u003d VictimsManComponovydny. EO. Maintaining \u003d truth; EO. USE \u003d truth; Recentlyrerevisitforms (Reli, "Report"); Report. Support workers. Customs supplies (Railway.Shemacomponkydatay. Report. Support workers. Restore (); // Preferably, although the FN does not affect it anyway. // Actually, it is precisely this can be called a change in the composition of the PN for each email from the report. Superman. If a mushroom (email deentifier-user ") then // can be used to use the email method to use the Estraentifier method, see a certificate in the joint venture, there everything is quite clearly email to SiD123; // Important - Identifier can be any, not UUID and not GUID! EL.Relastical user-tooling \u003d "sample"; Ended; EndCycle; computer \u003d new folder-topled complex; Comp. Training tools (rod.Shemomponovkydny. Report. Support Spaces. Suggested user-in-law (comp. User-in-section); For each email from the report. Support workers. Use the user-in-law. The elements of the cycle of EL.Rezhymographenization \u003d modulation of the electroenterkomykompon. // chopping the report of the report to the report; // Now it will give an effect: the form. Create element formulators (, modelsTracksProducts. Extrudresses

Actually, you can study this mechanics for a long time. This publication has grown out of studying methods for solving one specific problem, and therefore quite one-sided; But I will be confiring that the internal logic of settings, especially custom, in general, you can write a separate book that is not thinner than Krustalevskaya. I, unfortunately, there is no strength and time. Who will use specific developments - already well.

Something clarified experimentally and therefore controversy. Knowing more - invited to criticize and comment.

For one report, several options for its visual representation can be specified - that is, the village and the same information can be developed differently, grouped, etc. Predefined variants are specified in the CC Designer on the Settings tab (Fig.); Also, the option can be created in the enterprise mode.

An option located above all in order will be considered the default option.

For configuration predefined options, you can specify which settings will be available to the user. For example, you can prohibit making either grouping for an item. This is specified in the properties of the user settings item:

Specify the user access option to the setting:

It depends on that the user will see in the configuration of the report in the enterprise:

Question 11.32 Exam 1C: Professional on the platform. What version of the report in the data layout scheme will be considered default?

One that stands in the list of options first
The one that has a default property feature
One that was determined first in the process of creating options

The correct answer is the first, description in the text.
Question 11.35 Exam 1C: Professional on the platform. How to add settings to the list of custom settings?

in the form of the user element setting, you can specify a sign that the element is user
in the form of configuration of the user element, enable fast access in editing mode
adding is done by installing the checkbox in the "Use" property

The correct answer is the first.
Question 11.40 Exam 1C: Professional on the platform. In the settings of the data layout system must be specified

Structure of settings
Parameters
Selected fields
Groupized fields
Sorting
All of the above

The correct answer is the first. The structure is obligatory, all the remaining LCD can add automatically, or it is not necessary in principle.
Question 11.41 Exam 1C: Professional on the platform. How will the report form look like after applying the following settings?

In the form of a table of four columns: "Product", "Warehouse", "Number of residue", "Amount of residue"
In the form of a table of three columns: "Product", "Warehouse", "Number of residue"
In the form of a table, the number of columns of which will depend on the number of warehouses on which non-zero residues exist
The report will not be formed

The correct answer is the fourth - in the root element of the settings structure, it is not worth a check mark, therefore, the data for output is not defined.
Question 11.42 Exam 1C: Professional on the platform. What happens when generating a report, if there are no data layout settings in the user mode?

The default settings specified by the developer in the data layout scheme will be used.
From the list of options for settings will be used the option next for the current
Custom settings will be used.
The report will not be formed

The correct answer is the fourth - priority is that the user indicated. Custom settings are empty, therefore the report will not be formed.
Question 11.43 Exam 1C: Professional on the platform.

On the left border of the first second date specified in the "Period" parameter
Actual residues will be obtained if another value is not specified in the data layout system parameter created based on the name of the external parameter specified in the query text for the "period" parameter of the virtual table

The correct answer is the fourth. Tick \u200b\u200b"Period" is not worth it, that is, the useful selection is not specified. In general, this means actual residues, but perhaps the parameter of the period is defined in otherwise setting the CC.
Question 11.44 Exam 1C: Professional on the platform. What point on the time axis will be obtained remnants when forming a report?

On the left border of the first second date specified in the "Period" parameter
On the right border of the last second of the date specified in the "Period" parameter
Actual remnants will be received.
Actual residues will be obtained if another value is not specified in the data layout system parameter created based on the name of the external parameter specified in the query text for the "period" parameter of the virtual table

The correct answer is the first - here is clearly the selection.

Question 11.45 Exam 1C: Professional on the platform. The figure shows the report form created by the default system. An element of what type of settings is circled by the frame?

Custom settings
Fixed settings
Option settings
The element may relate to any type of settings, depending on the value of its property "path to data"

The correct answer is the first.
Question 11.46 Exam 1C: Professional on the platform. The selection report on the "Warehouse" field is specified simultaneously in all types of settings. What happens when you try to form a report?

The report will not be formed
The report will be formed using the selection from custom settings.
The report will be formed with the use of selection from fixed settings.
The report will be formed using the selection from the current settings option.

What kind of "all kinds of settings" is not clear, but the correct option is the correct option.
Question 11.47 Exam 1C: Professional on the platform. The selection report on the Warehouse field is set at the same time in the user settings and in the current version of the settings. What happens when you try to form a report?

The report will be formed using the selection from user settings if the "Use" flag is. If the "Usage" flag is not installed, then the selection will not
The report will be formed using the selection from user settings if the "Use" flag is. If the "Usage" flag is not installed, the selection setting from the settings option will be used.
The report will be formed using the selection from the settings option if the "Use" flag is. If the "Usage" flag is not installed, then the selection will not
The report will be formed using the selection from the settings option if the "Use" flag is. If the "Usage" flag is not installed, the selection setting from custom settings will be used.

The correct option is the first.
Question 11.49 1C exam: Professional on the platform. When working with settings, the user can set the grouping field

In a separate window "Grouping"
In a separate window "Editing field fields"
On the "Grinded Fields" tab
In a separate "Grouping" window and on the "Grinded Fields" tab
In a separate "Grouping" window, in a separate window "Editing field fields and on the" Grindable fields "tab

The correct answer is the fifth. Grouping window:

Options Editing field fields and grouped fields:

Question 11.50 Exam 1C: Professional on the platform. The user created "from scratch" option settings. What settings did he have to edit? Choose the most complete and correct answer.

Selected report fields, report selection, selection via warehouse, additional settings of the table, sorting nomenclature, parameters, conditional design Nomenclature
Selected report fields, report selection, additional table settings, conditional design of the nomenclature, selected warehouse fields, parameters, report sorting
Selected report fields, report selection, selection via warehouse, additional table settings, conditional design of nomenclature, parameters, report structure
Selected report fields, report selection, selection via warehouse, Advanced report settings, parameters, conditional design of the nomenclature, report structure

The correct answer is the third, you need to carefully look at the screenshot.

Attention! Before you, the introductory version of the lesson, the materials of which may be incomplete.

Data Layout System 1C 8.3 For Beginners: Making Data Sets

Write a report that displays customers and their favorite products. Each client has a favorite color, and each product has its own color on the basis of these colors and it is necessary to determine the "love" of the product. For example, if Andrei's favorite color is red, then one of his favorite products will be tomatoes (they are red).
Apply two dataset in the report. The first set is the data from the table "Customers" directory. The second is the data from the table "Food" directory.
Implement communication of these two setsSo that only your favorite products for each of the customers remain in the report.

Create a new report

Open the database "Deli" in the configurator and through the main menu create a new report:

Type of document - "External Report":

In the form of a new report, specify the name "Lesson" and click the "Open Data Layout Scheme" button:

Leave the default scheme name:

Add the first set of data

In the opened scheme, go to the "Data Sets" tab and choose "Add Data Set - Request" through the Green Plus:

Call a query designer:

Specify the table "Clients" and fields you want to get from the request:

Add a second set of data

Add a second data set:

We highlight it (set2) and again call the query constructor:

We specify the table "Food" directory and fields you want to get from the query:

It turned out such a query text:

Please note that we now have two data sets in the report: sets1 and sets2. Each has its own query text and its data.

We make names more visual

For clarity, let's rename sets1 to customers, and set2 in the food.

Make it double-click each of the sets:

We will be able to use each set of each sets in our report. To these data we will handle through the fields.

At the moment, the set "Clients" the following fields: "Name" and "Favorite Title", and the "Food" set: "Name" and "Color".

We see that the names intersect and we are easily confused. Therefore, let's change the field names to more speaking.

We highlight the set of "clients" and change the names of the fields like this:

Then we highlight the set of "food" and change the names of the fields like this:

Call the designer settings

Finally, go to the Settings tab and press the magic wand to call the settings constructor:

Report type - "List ...":

Select fields for report from both sets:

See why it was so important to change the names of the fields? At the stage of layout settings, we do not see which sets of these fields. We see only their names.

Check the report

Save the report and form in user mode:

Yeah. Well, but not quite. There was a so-called cross-connecting connection of two sets (it should be well acquainted by connections in the queries that we studied in past modules). Each record from the table "Clients" is mapped to the "Food" table.

But we need from all these records to leave only those whose "Favorite Blower Clear" field is equal to the field "Colored":

We communicate two sets of data

To do this, make the connection of two sets of data (clients and food) in the fields of favorite detectant and blooms.

Go to the tab "Communication Data Sets" tab and click on the Plus button to add a new link:

Customize the parameters as in the figure below:

I will make explanations.

Source and receiver communication. Well, everything is clear here. Indicate the first set (clients) and the second set (food) of the data. I want to pay special attention to that the connection will be carried out on the principle external left connection (We passed it in the topic of requests in past modules). Based on this and you need to choose which set will be the source, and what a receiver.

Expression source. Indicate here a expression or just a field from a source dataset (we indicated here a field of favorite declined from the client set).

Expression receiver. Indicate here a expression or simply field from the receiver data set (we indicated the Flames field from the food set).

In this way this communication Leaves from the past list only those lines that have a field of favorite declitient equal to the field of color.

Save the report and launch in user mode:

Excellent!

I will make an explanation about the field " Communication condition", On which beginner programmers are so often beaten.

Communication condition is an auxiliary field. There you can write expressions with the participation of fields only from the data set specified in the communication source.

In this case, for all lines from the communication source, this expression will be checked (communication condition). And if this expression is the truth, then an attempt will be made to establish the relationship of this line with rows from the communication receiver. If the expression is equal to false, then there will be no such attempts.