1C 8.3 How to make the field inaccessible.

// Along the way, fill the field of the object's name, if it is necessary to be filled (object. FIO) Then structurephio \u003d physicalityaclitservoer. Family disease The name ofFizlitsa \u003d CROLP (STRUCTURE. Familia + "" "" + Structurality + "" "" + Structurality. Object. FIO \u003d namePhizlitsa; Object. To recruit (); ended; // Just in case we check, there are records in the register for the current elementandanyFl \u003d registriors. Fiophysical tester () \u003d 0 then // Filling the register of individuals for the accounting department of the enterprise 3.0 structurally \u003d physicalityclitservoer. Family disease (TEG (object. FIO)); Period \u003d? (Value is filled (object. Advantage), object. Advantage, date (1900, 1, 1)); Structural structure ("" period ", period); Structural structure ("" physical, reference); Set \u003d registers. Fiophysical land. Create registration (); Set. Title.physicity. Set (link); Recording \u003d set. Add (); Filling out (recording, structural); Set. recruit (); Ended; The register will be updated normally, if the names of the directory elements or the FULL field are filled in orderly, that is, in the format the name of the name patronymic. With you a hundred rubles on the phone in the profile as a gratitude. // Exported procedures and functions and functionar clogging (available products, selected) Form exports \u003d This. Molding (). Forms; For each form of a form of cycle, if form. If \u003d "" "Pre-drawing" or form. "" "" "" Formasters "" or form. If \u003d "" Specked "" then continue; Ended; Foundation \u003d Available products. Stalls. Init (form. The "" name "); If not found) \u003d undefined then if not found. Processing \u003d form. Sinone then I found. Process \u003d form. Sinonym; Ended; If it is not this object. Forecorm (form. I mean). The use of the settings then the found. Stroke .Tube (); Ended; Proceed; Ended; New Treatment \u003d Available Production. Straight. Add (); New Treatment. Processing \u003d Form. Sinimi; New Treatment. Emplooms \u003d Form. EndCycle; Maceselands \u003d new array; For each available processing of available products. Straight cycles. If forms. Invite (accessible processing. Employ) \u003d It is indefinitely an argent adaptation. Addly (accessibility); Ended; EndCycle; For index \u003d 0 by argerting. Quantity () - 1 cycle of available products. Strengthening. Delete (massually adaptations [index]); EndCycle; Maceselanting. Operate (); For each selected processing from the selected processing cycle, if the selected processing. Strand-accommodating processing \u003d is indefinitely an array of argerting. Addly (selected); Otherwise, if the selected process is. Strand-accompanied. Drawer \u003d Undefined if available products. Structures. Interty (selected. Extra stake. Ended; Otherwise, if available products. Structures. Interty (selected. Strand-accommodating processing. Diversity. Items, "" Name ") \u003d Undefined then massaging. Addly (selected processing); Ended; Ended; Ended; EndCycle; For index \u003d 0 by argerting. Racing () - 1 cycle of selected trees. Delete (array / index]); EndClocheclone; End Controlments // Broadcasting () 1C: Enterprise 8.2 (8.2.18.61) Fat client KONF is not standard.

Here's another: I decided to try to replace the values \u200b\u200bin the directory in the tabular part, you need to select and simply delete the value (replace to empty) and then after selecting: "" (form. Drobaging. Form (991)): Error calling the context method (output ): Output error: Error Output When the result is deriveding a data acquisition error: Error creating a "set databrus" dataset ": Error in the data set query: ((223, 31)): Invalid parameters in the comparison operation. It is impossible to compare the fields of unlimited length and the fields of incompatible types. Table linked. Rassers\u003e \u003d & P "".

Related Topics Subject Author Replies forum Ambassador. Message Important: Processing (managed and normal application, data exchange of ut 10.3 / 10.2 - BP 3.0) Designed to transfer documents and directories from the UT 10.3 / UT 10.2 base to the BP 3.0 base without using exchange plans .: arrow: Supported Releases (for platforms 1C Enterprise 8.1, 8.2, 8.3): Trade Management: 79 Sat 09 Sep, 2017 00:22 Processing (Managed Appendix) Allows you to simplify the process of debugging and testing external filling treatments, including tabular parts, or creating related objects (input based on ) for configurations 1C: enterprises 8.2 / 8.3, developed by 39 W 18 Apr, 2017 19:43 Processing (managed and normal application) is designed to view / change roles (access rights) of users of the information base both in the managed and normal application without Bindings to a specific configuration. For group change Rocks 8 Thurs 02 Feb, 2017 19:45 Processing (managed and regular application), Data exchange Purpose: Universal processing for registration, cancellation of changes (register management) in exchange plans, monitoring the status of data exchange as in managed mode, So and the usual application without 28 Fri 18 Aug, 2017 01:06 Universal mechanism for monitoring the details of objects in the enterprise mode (the usual application of the universal mechanism for controlling the filling of details (control of empty details) of the headers and table parts of the configuration objects (reference books, documents, business processes , tasks, exchange plans, plans of species 15 Thursday 09 Jul, 2015 15:29.

Place the button in the form of a list of reference book, wrote the code: Proceeds Procedure (button) Sampling \u003d References. Scripts. Symbol (); While the sample. Next () cycle, if the sample .Rodel. Name \u003d "" Then if the sample. Gruppies. 14 Oct 10, 17:20 Reply | Quote Report to moderator. Re: The object field is not available for recording. 1C8.2 Handbook Employees Element form module. Operating procedure () if not eton () then.

When working with 1C, it may often be possible to appear error message "The object field is not available for recording". Consider what actions can lead to it, and how it can be eliminated. Causes of the error occurring to the appearance of a system window with this error can result in 6 factors: an attempt to change the values \u200b\u200bin the fields, the change of which is meaningless; Error in code; Attempt to change system fields; Not enough rights to change; Outdated 1C configuration; The managed form uses an element and props with one name.

Attempting to change the values \u200b\u200bin the fields, the change of which is meaningless for example, an attempt is attempting to replace references, not an object. But it is impossible to do this. If you change the link, first, it will refer to a non-existent object (to nowhere), secondly, you will no longer find it anymore. An example of an incorrect code fragment: Ivanov \u003d reference books. Physician .Nightyponiament (Ivanov Peter); Ivanov. Romeryport \u003d "2175353"; And when entering the last line, an error "object field is not available for recording" appears. The reason is that an attempt to edit properties or details of the reference occurs. In the specified example, the "Careport" parameter you are trying to set a definite value. But this data can be changed only at the object.

In this example, "Ivanov" is a link that is designed to read. For it, a person is identified in the database. In the second line indicated "Point" - "Ivanov. Increased". But it is also not an object, because when accessing the "point", the same request is performed to the database. This is done for the convenience of using 1C. How to fix the error?

So that the message "Field of the object is not available for recording" no longer appeared, you need to register the following: Ivanovlinka \u003d reference books. Ivanovitsy.Ter); Ivanovobject \u003d Ivanovlinka. Focusing (); IvanovObject. Increased \u003d "2175353"; Ivanovobject. To recruit (); Now the link is accessed by reference, and then it is already edited. After that, the object is written, that is, its new state is recorded. The error in the code is possible the reason for the programmer that worked with the current 1c configuration made an error when finalizing. Then only a specialist can also fix it. It is desirable that it was exactly the person who initially set up 1C.

An attempt to change the system fields The user is trying to edit those data to replace which it is not right. For example, the line number in the table, the installation of the "current" instead of "flowing", etc., sometimes the error occurs due to simple inattention. If you turn to the right fields - the error will not appear. Not enough rights to change Sometimes the field that tries to change the user is read only. This is related to the rights to the objects of a particular user. To eliminate the resulting error, it is necessary to analyze the rights to a specific object and or allow the user to access the corresponding field (on the entry), or to exclude the field (or an object) in general from consideration.

Outdated 1C Configuration Sometimes the "object field is not available for recording" error appears when updating 1C. To remove it, you need to upgrade to the latest version of the platform. Eliminate the error is usually not difficult and to make it can the user itself. If the configuration 1c is seriously violated, only a specialist can correct the position. The managed form uses an element and props with one name quite rarely error "The object field is not available for recording" appears when the names of the props and the element of the controlled form are coincided.

To eliminate the error, it is necessary to explicitly register access to the details or form element. For example, in the form 1C there is props with the name "amount".

With the same name on the form there is an element "Amount".

For novice developers 1C 8.3 it is difficult to understand why they are so often getting a mistake - The object field is not available to record 1C (operating time, code, table, number, date, etc.). We'll figure it out why this error may appear and how to deal with it.

If you have no idea what programming is, it is better to touch anything. Most likely, programmers who modified your configuration simply allowed an annoying error. Just call a specialist who worked with you. This error is solved fast enough (if it does not pull over other, more complex problems). If contacts with personal programmers are lost, you can contact our highly qualified professionals, details on the page -.

If the error occurred after configuration updates 1C 8.2 or 8.3, most likely, You need to last relevant version.

Get 267 video tutorials for 1C for free:

If you are a beginner programmer 1c

If we talk in general, then you are trying to change data in the program code that you do not have the right to change. Consider specific cases:

Change the object and not a link

Hit parade The reasons for the appearance of this error heads an attempt to assign an element of new attributes. Do it usually approximately like this:

Petrov \u003d directories. Physilestick. Foundation (Petrov Ivan); Petrov. A number of number \u003d "2156363";

And at this moment, the newcomer receives an error - the object field is not available for recording 1C.

It should be understood: change properties and details are possible only object. In this case, the variable "Petrov" contains in itself the so-called. "Reference" is a unique identifier in the database, with which the system supports uniqueness. And the fact that it is available to us "on the point" (Petrov. Incidental) is just the convenience of 1C enterprise, and in fact any "point" is another query for the database.

Proper problem of problem:

Petrovsky \u003d References. Physilestick. Foundation (Petrov Ivan); Petrovabject \u003d Petrovsky. Reference (); Petrovobject. A number of number \u003d "2156363"; Petrovobject. Write down ();

Attempt to change system fields

The second most popular cause is the cause of this error is an attempt to change details that cannot be changed.

• row number of tabular part;
• using the current, instead of fluid;
• etc.

Beginners Programmers 1C Quite often see an error message in the unavailability of an object field when recording. There are only three ways to appear this error, but in practice it is often found quite often, so the developer need to know how to correct the situation. Understanding once the reason for the appearance of the message of the system field is not available for recording, you will stop receiving it once and for all.

Why does this error appear?

If you are a simple user and see such a mistake, you can hardly handle it with it yourself. The problem is not in your actions, but in error in the program code. To correct it, it is necessary to analyze algorithms. Therefore, when you see the "field is not available for recording" error, inform the developer and wait for its instructions. If there are no third-party specialists in your company in your company, then third-party specialists will come to your aid.

Developers highlight 3 common causes of an error window appearance:

Attempting to change the reference, not the object. In the 1C system, there are certain rules, and one of them reads: "Only objects can be changed." The problem is that the link is simply an object address in the database created for uniqueness. It is important to understand the difference between reference and object, because in some operations with them the result will be the same.

If you randomly or by ignorance tried to change the props of links and got a mistake, you need to add a couple of lines of code. In the Platform 8.3, the function of obtaining an object on the link is laid, and to change the values \u200b\u200bof the details will have to use it. That is, before changing, you need to get an object by reference, change the props and write the object.

The second source of this error in frequency is The code in which the developer is trying to change the requisites prohibited to change. This sins inexperienced programmers 1C, trying to change the line number in tabular part, identifiers and so on.

Another reason for the appearance of such an error is Updates. 1C releases them quite often for configurations, and for platforms. The problem is that not all changes are subject to thorough testing, and users involuntarily perform this work. That is why it is recommended to use the test base for the update on which to check the performance of the new release of 1C, compare the value and parameters on it.

What if you still can't work after the update, watching the error of the inaccessibility field of the object for the entry?

Specialists advise either to establish the latest issue of configuration and platform 1C, or, on the contrary, return to the previous workable and wait for corrections. Of course, you can climb a typical configuration code and correct the error, but for this you need to be a highly qualified 1C developer and remember that after the change you will not be able to be updated automatically.

If you decide to ask help, keep in mind that there can be several software products from 1C in your company, therefore, to facilitate the work of programmers, inform them with detailed data. The correct parameters refers to the name of the program, its version and actions that led to the appearance of an error. With these introductory developer, the developer will be easier to figure out the problem.