The object field does not contain any filling rules. What's wrong, because "the object field is not detected." Cleansing nalashtuvan koristuvach
Perhaps one of the errors that often occurs when using programs and configurations issued by 1C can be called the “Object field not detected” notification. The reasons for the guilt of this act, the methods of its removal and the situation in which it manifests itself and is dedicated to this article.
What does “object field not detected” mean?
Any 1C configuration includes a set of metadata objects, to which the program is periodically updated. The skin object is characterized by a set of fields. The program itself informs you about the incorrect result of scaling to the object field when it appears.
You can blame this situation if:
- About the time to start the program;
- When the information fields of the form are filled in;
- When the information is sent to another person.
Cause mercy to appear
The 1C object field is not detected, most often it appears after making a change to the configuration (self-addition or updating to the current version). The main reason for guilt is the lack of importance of programmers:
- The details before which the code is generated are available at the database (it was previously created);
- Code to take revenge (;
- Grinding when generating fields (relevant for painters who work with ceramic molds);
- All the details of the form element have not been filled in (except that the entry field does not have the details “Way to date”, the error “Object field not detected” appears when the skin is entered to this field);
- In cerated forms, if you forgot to enter the command for the button in the sampler, you can get stuck with this price.
Ways to learn
Please note that for 1C “Object field not detected” is not a critical error. The operation of the system is frustrating, it interrupts every time the module is installed, or the system has a problem.
Whatever the reasons for the cancellation, without the delivery of programs, it can only be determined in one way: as soon as the cancellation is completed due to the updated configuration.
In this version, you can update the backup copy of the database or perform an update, after which, in the new release of the configuration, which means everything, the amend will be removed. Most other types of problems require changes to be made before the program code is terminated.
The butt of the paring is the same technique
In program versions following release 8.2.15, to simplify the identification of clients, the ability to log in using an additional OpenID has been introduced. At the time of this release, a lot of people clicked with the message “Object field not detected (OpenID authentication).
As explained earlier, the reason for the appearance of this window was that before the configuration was broken down, the possibility of such authentication was not guaranteed. And the program code did not specify the mechanism for causing such a problem.
The main directions of the decision were:
- Updating the platform to the current version;
- Vidmova updating the configuration;
- Change of exchange rules;
- You can simply ignore the reversal;
Whatever the situation, no matter how guilty the situation is, there is no need to panic. Try to read what the program tells you about, which fields are missing, analyze what actions led to the notification appearing and contact a specialist for technical support. Most often, this problem arises over the course of a year from the moment of development.
The problem with this problem is that the 1C system crashes - Pomilka: The object field is not detected, most often it disappears at startup. This problem brings insecurity and disrupts the work process. Many koristuvachs, as they show their experience, do not know how to solve this problem on their own. Let's take a more effective look.
In 1C settings, the skin object is assigned a voltage field. Having analyzed such a change from the programmer’s point of view, one can come to an uneasy conclusion: the problem arises when the program expands to a field that is not specified in the object. Assessing the problem from the position of the correspondents, the 1C problem lies in the fact that the program cannot find tasks that correspond to the attribute.
Pomilka 1C, as a rule, appears in three situations:
- when entering the program;
- at the hour of filling out the form;
- before completing the template.
This list can be taken into account, but methods for eliminating the error can be found in the details of incorrect display of pages.
Trouble: The object field is not detected 1C (Authentication)
With new updated 1C, you can login via OpenID. This new option allows you to bypass the login after the connection has been interrupted.
You can solve the problem in a number of ways:
- update the platform to the latest release (you will find the update on the official 1C website);
- Upgrade to the latest version (be sure to create backup copies).
How to troubleshoot the problem without using a wiki update:
- skipping mid-program verification;
- independent change of exchange rules.
Pardon: Field not shown (Warehouse)
Reason: the data in the document is indicated, for example, in the middle of the table, and the details appear at the header:
- polish the tooth to the point of grinding;
- In the configurator, be sure to check whether the entered data is correct.
Pardon: The object field is not detected (Prefix of the Product)
Options for solving the problem:
- insert a code for all your products;
- for codes, customize the template (section “Customization of possession”).
Pomilka: Object field not shown (Row Poshuku)
- Carefully review the code, as the problem may have been re-interpreted, such as an incorrectly specified visibility or something else;
- Introduce other conversion processing.
Pardon: The object field is not shown (Counterparty)
You can include this information by checking the “Independent conduct of partners and contractors” section. To get to this setup menu, go to “Administration”, and then to “CRM and sales”.
The problem we have looked at often occurs in new software releases due to the introduction of new software mechanisms. In most cases, the problem resolves itself around the time of a new release. To avoid waiting for a new release, do not forget to save backup copies. Let me turn you back to the previous version. This option can be used in any situation if the 1C program fails.
- It is necessary to clear the configuration of old and unnecessary information. In the "Check configuration" menu, set the order "Check the logical integrity of the configuration." The program independently displays incorrect information.
- For those whose configuration is in a state of flux, providers recommend carefully checking the configuration of the supplier. To check, transfer the configuration of the installer to the new database and repeat the first step.
There is an algorithm for canceling amends, which is based entirely on technical points:
- It is necessary to turn off all background data of active databases.
- Restart the server.
- Create backup using SQL methods.
- Take the base from support and vivantage cf.
Sometimes the 1C system responds with the following warning: “The object field was not detected.”
Cause mercy
This problem can arise in various situations:
- When entering the program;
- When filling out forms or before entering data into templates;
- when registering a compiler - “Before Recording” through the “ZagalniyModule Koristuvachi (OpenID Authentication).
Options may vary. It turns out that in the setup mode of the 1C configurator, all functions work correctly, but when you launch the program, such a problem occurs.
The reason for this is that the previously developed software mechanisms do not comply with these configurations, and the data entered into the program code does not undergo processing. Tobto. Let's go to the beast until there is no attribute.
This situation can arise during the installation of a new release or in a robot with the 1C program on an old platform.
Method of correcting the settlement
To correct the “Object field not detected” error, you need to reinstall or update the program to a new version. The current version of the platform can be found on the company’s official website or other related resources.
Otherwise, you can roll back to the previous version, but it is recommended to regularly make backup copies.
Sometimes it happens that after updating 1C, write “Object field not detected” from assignments to the same object. This may happen when entering the program, filling in any form, etc.
If you think about the essence of the information, it is obvious that the program is impossible to find out the tasks of the target object. This situation is typical for installing a new release that runs on an old platform. In this case, the outdated mechanisms of the platform do not support changes in the release and are converted to an attribute that no longer exists.
Fig.1
The module, before it is completed, stops working, otherwise the program may not be interrupted. If the program is located in the program or processing module, then the program may not start when launched.
In this case, it is important to look at the description of the progress that emerges during the hour of installation of the update. There, it is obligatory to specify recommendations for the current version of the platform.
Fig.2
Thus, the first and main option for the current problem is the price of updating the 1C:Enterprise platform.
To see what platform we have installed, you need to go to the menu item “Service” - “About the program”, where in the top row we see the version of our platform that is equal to the one recommended when installing the updated configuration.
Fig.3
Cleansing nalashtuvan koristuvach
The error may be canceled when updating the platform with programs, for example, after updating the configuration, when pressing the “Select” button on the implementation document, the message “Object field not detected (Currency)” appears. " What could be the reason for this, is the platform updated? Some parameters of the program can be fixed in the settings of the user and to remove the grinder, it is enough to clear the settings. In “1C: Accounting 3.0” this item is located in “Administration” - “Program Parameters” - “Koristuvach and Rights Parameters”.
Fig.4
In the section “Personal settings for personal accounts”, go to the “Clean settings” section, where we can select - clear settings for all members or just the selected one. We can also choose to clear all settings or any other settings.
Fig.5
Fig.6
Before us we see the training of the koristuvach, in which it is possible to vikoristovat old objects, which is where programs are trying to be amended. We can choose a specific setting (with a hint) or clear all settings.
Fig.7
In this case, since the guilty agreement is not connected with the platform and the training of the correspondent, then, perhaps, it simply became an error in the information base, which is a corruption of the object’s indications. In this case, it is recommended to carry out “Testing and correction of the information base”, in the Configurator mode, in the “Administration” menu item.
Fig.8
When tested and corrected, it is necessary to verify the logical and feasible integrity of the base. If an unidentified object is detected, we can set the parameters of the verification program to work with such objects - close the objects, clear the message, or do not change them.
Fig.9
When you select the “Create objects” option, the program, when an unexpectedly sent object is detected, forms an element, a kind of stub. When you select the option “Clear messages” or “Delete object”, incorrect messages will simply be deleted. If you deprive the switch from the default - “Do not change”, the program simply tells us on this subject, do not worry about daily actions. This option will not help us.
In this way, if there was a pardon in the 1C program, there would be a more logical explanation.