The predefined element is absent in the data 8.3 processing. Installation of predefined elements

The very idea of \u200b\u200bprogram work with predefined elements, in my opinion, is very correct. Just there are nuances that need to be considered when working.

First you need to clearly realize for yourself that there are predefined elements in the configuration and there are predefined elements in the information base (IB). Technically predefined IB elements These are the most common elements of reference books, in which the "Name of the Distribution name" specifies, which predetermined configuration item they correspond. They do not differ from ordinary elements anymore. Accordingly, any conventional IB element can be made predefined, any predetermined. To do this, it is enough to enter the desired value in the props "NamePredeshestiny".

Periodically, this property turns out not the value that the developer has provided. As a result, errors occur in 1C. From the critical, in which the work in principle is impossible, to non-critical, in which the logic of the operation of the algorithms is disturbed.

Conditionally you can highlight Three types of errors:
1. "The predefined element is absent in the data";

3. Invalid instructions predefined element;

1. "The predefined element is missing in the data" - abouttouch the predefined element described in the configuration in the IB data.

This is the easiest in debugging and correcting the type of error. Its simplicity is that the platform correctly reports to this situation "the predefined element is missing in the data" and is quite understandable how to fix it.

When referring to the missing element in the code "Reference books. VidaContact the information. MailContact the one is issued a message.

When contacting the item in the query "Meaning (Handbook .VidkoneTactionalInformation.EmailContact)" a message is issued:

This error occurs if the element in the configuration is described, but in the database it is not compared.

To begin with, we specify that this situation is not always erroneous. It is quite possible to use predefined data in some kind of software logic, which may not be used for most users. In this case, so as not to choke a reference book from all configuration users, it is logical to define predefined elements in the configuration, but not to create them in all IB, but only for those IB in which the desired configuration logic is used. In this case, the programmer may specify the "Do not update predefined data" property for the reference book and create the program elements when accessing the module functionality. Either give the opportunity to the user to independently bind predefined elements of the module to the usual elements available.

It is also not used to automatically create predefined elements when working in RIB mode. Since new elements should be transmitted from the central base, and not to be created in nodes with different widths.

Those. Sometimes an error is to appeal to an unavoidable element, and not the very presence of such an element.

It is necessary to analyze why the element is not created. It may be possible to be created when performing any program mode. For example, after making a exchange in Rib. And perhaps, it was just accidentally deleted.

If the logic is provided to fill the predefined items not automatically, but a separate mode, then before using the call name " Reference books. LifactsContact information. MailContactNometrics"To prevent an exceptional situation, it is advisable to verify that the element is already in the database. If the item is missing, I will tell the user about this and explain what mode it needs to be performed to fill the item. For such a check, you can make a request to the data.

Request \u003d new request; Request. Text \u003d "Choose | SpeciesContacts. Link | From | Handbook .VidkoneContinct information as SpeedKontacultiformation | Where | SpeedContacts. EmailContact Togolitsa"" "; Elementatonsvutvytnyy \u003d query. Fill (). Empty ();

If it is still an error in the database data, then you need to be binding to the predefined element of the IB element. Those. You must explain the system to which IB element should contact the software code for this name. Technically binding is just specifying the name of the predefined item in the property "Name reported"IB element. To install it, it is enough to execute the code:

2. "The predefined element is not unique" -advanced predefined elements:

This situation lies in the fact that several elements of IB are tied to one predefined element. In this case, when accessing a predefined name, the element will be chosen randomly. This situation is always erroneous. Its complexity is that the platform does not report anything about it. Just algorithms begin to work incorrectly.

The platform will report an error "The predefined element is not unique" only when you try to edit a convertible element.

Until anyone needs to edit an element, no one knows about the error.

Such duplicates can be created, for example, if the reference book is used and in properties for predefined data, the "Update automatically" mode is specified. In this case, when performing a exchange, one instance of predefined data will be created when updating the configuration. The second instance of predefined elements with the same name is transmitted from the central base when exchanging.

Also, these duplicates will occur when using the exchange processings between configurations in case of different bases predetermined elements, different IB elements correspond to the predetermined elements. In this case, one instance of predefined data in the database is already there, the second will come when loading data with another UID. If you perform data transfer, it is necessary to decide whether the elements of which database are considered to be the main and use them in the subordinate base. In the subordinate database, it is necessary to replace the use of old elements on the elements of the main base.

Such errors in the database can be revealed by the view of the form:

Choose SpeciesTenectin Information. IMAIPED DEFINITIONED, Number (Various SpeciesTextant Information. Link) As a Mount Aid-Distributed Directory .VidkoneCont Information How to Sonekontin Information Groupled for Species Tank Inteformation

This request will return a list of predefined elements with which more than one element of the IB is associated with.

In the presence of such elements, it is necessary to remove the connection with the predefined connection for one of them. Those. It is necessary to definitely determine for the system, to which IB element should contact the program code when using this name.To do this, just execute the code.

3. Incorrect indication of the predefined element.

The error is that the predefined element corresponds to the wrong element that is provided for by the program logic. Such errors are most complex in diagnosis. Unlike the first two types, it is impossible to automatically check these errors to automatically check the configuration. They can be identified only by analyzing the logic of the work. If you doubt, you can check whether the item needs is used.

To do this, just execute one of the commands.

// Definition of an IB element that is tied to the desired predetermined to inform (reference books. Lidkontact information.EmAlightContact) // Determine the predetermined element to which the selected report is attached to (reflecting element.

When identifying such errors, it is necessary to remove incorrect communication with the old element and add communication with the new item. Operation code is similar to the correction code of the first two types of errors.

Well, briefly about errors in software or in configurator mode:

"The predefined element does not belong<Имя справочника>" - Error occurs when you try to record a predefined element with a name that does not match the name in the Konofurator.

"Not predefined objects cannot have predefined subconto species records" - Error arises when trying to make an element a predefined account plan for unexpected. To eliminate errors, it is necessary for each line of the subcontal element to remove the sign "predetermined".

"Not predefined objects cannot have predefined records of leading species of calculations"- The error occurs when you try to make a predetermined element of the plan for calculating the calculation of unexpected. To eliminate errors, it is necessary for each line of the leading type of calculation of the element to remove the "predetermined" sign.

"Predefined elements are not unique" - Error is issued in the configurator when updating information base On the release of configuration without compatibility mode from 8.3.4. It is necessary before the update check duplicas and eliminate them.

"The name of the predefined element is not unique" - Error occurs if there are several of the same predefined elements in the configuration when updating to the platform8.3.6.2332 and above. It is necessary to eliminate duplicate in the configuration.

To work with predefined data, recommins. It knows how to perform any actions with predefined data, and can also check the configuration with a member for availability in all IB objects (directory, account plans, PVC, PVR) errors of the first two types (hidden and missing elements).

Good day.

Today we will talk about the innovation in the Platform 8.3 concerning predefined elements.

Introduction

Let me remind you that earlier in practice, very often I wanted to learn its predefined name in the element of the reference book. For example, you created two predefined counterparties and called its Ipsidors and a commotor. And some logic seduced on them.

When everyone was debugged and worked out, it turned out that the task was put on the contrary and logic for the IP need for LLC, and the logic of LLC for IP. "There are no problems," we say and in the enterprise mode, we rename items. After all, it is much more difficult to climb into the code. A year is held and a new task is set: for Sidorov's IP, set some other logic. You climb the configurator, write the logic, start checking and does not work, because In the configurator of the Ipsidors, and in the enterprise - a commoteeor. The brain is broken and this rake want to destroy. The simplest and visual is to display the name of the predefined element in the list form. Here is an ambush, it is possible to obtain the name of the predefined in 8.2 only by the method. And the method is your inconvenience, it cannot be obtained in the query. Those. The first inconvenience is to get the name of the predefined link to the reference book.

The second inconvenience, when we already have an element of the reference book and we need to make it predetermined. We create a predefined element and get two items in the directory. One predefined, the other worker to which all our documents refer. Replacing links of course cuts out, but if the base is large, then it is hard.

Now in the case

The first thing is that the reference book has a "Updating Predefined Data" property.

What does this field give us? If it is installed in "not updating automatically", then adding a predefined element, we will not see it in the directory immediately. Those. Metadata is in no way related to the data. And if it does not create it in the directory, then the appeal to it by his name through the directory manager will cause a syntactic error.

Very interesting, why? How do we create an item in the directory? And as you wish, you can create, or you can associate it with already existing. Now the directory has the props "name of the Distribution". We create an element of the reference book programmatically as usual through "Reference books. Contractors. Create element ()" and fill it by the props "name of the name-constrained" equal name of the predetermined element. Or, if the element is already there, we get it the object and in it again fill in the "name of the Distribution". Everything.

And lastly a little syrup

This new props, just that it is read and write, so it is also available in queries. In this way, you can impose conditions on it in queries, to determine the predefined it or not.

Thanks for attention.

Simple processing to work with predefined values.

Allows you to match IB elements with predefined in the configuration elements.

Allows you to check the configuration encouragement (several IB elements tied to one predetermined element - error) and missed elements (predefined items that are not associated with IB elements). Such elements could occur during exchanges or failures and cause errors in the configuration.

You can simply view the current values, you can make any necessary changes.

Operating procedure:

1. Run processing.

2. We choose the type (directory, account plan, PVC, PVR).

3. Select the directory of the selected type itself.

4. In the tabular part of the processing, all predefined elements available in the IB appear and described in the configuration.

If there are several elements tied to one predefined property or some of the elements described in the configuration items are not assigned to elements, the system will report this when choosing a reference. The grooved and missing elements will appear at the top of the list and will be highlighted with orange.

5. We establish new values \u200b\u200bfor the necessary predefined items.

At the same time, strings are marked red, for which the predefined element disappears from the configuration. Single lines for which a predefined element is changing, green strings, which appears a predefined element.
For large quantities The doubles are convenient to highlight all the extra lines and specify for all selected communication with the "Cancel compliance" button (from version 1.3.1)

6. Perform a reassignment by pressing the button "Perform elements" button.

Checking the oak (error "The predefined element is not unique"):

When you click on the "Check Droke", the processing will check all directories, billing plans, PVC and PVR and will display a list of tables with hurry elements with an indication of the returned elements.

After that, it is necessary to check individual objects for which errors are found.

Verification of missed(error "Predefined element is missing in data"):

When you click the "Check Missed" button, the processing will check all directories, billing plans, PVC and PVR and will output a list of predefined elements that are not compared to IB data.

To use requires a platform 8.3.3 or higher.

Universal, can be used with any configurations.

Detect language Afrikaans Albanian Arabic Armenian Azerbaijani Basque Bengali Belarusian Bulgarian Catalan Chinese (Simp) Chinese (Trad) Croatian Czech Danish Dutch English Esperanto Estonian Filipino Finnish French Galician Georgian German Greek Gujarati Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Kannada Korean Lao Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Tamil Telugu Thai Turkish UKRAINIAN URDU Vietnamese Welsh Yiddish

Afrikaans Albanian Arabic Armenian Azerbaijani Basque Bengali Belarusian Bulgarian Catalan Chinese (Simp) Chinese (Trad) Croatian Czech Danish Dutch English Esperanto Estonian Filipino Finnish French Galician Georgian German Greek Gujarati Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Kannada Korean Lao Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Tamil Telugu Thai Turkish UKRAINIAN UrDU Vietnamese Welsh Yiddish