![1c The Identifier In The Directory Identifiers Of Metadata Objects 1c The Identifier In The Directory Identifiers Of Metadata Objects](https://patentimages.storage.googleapis.com/US6587856B1/US06587856-20030701-D00008.png)
ERP 2.4.2.123, platform - 8.3.11.2867, BSP - 2.4.4.130. The following problem occurred: A new directory was added to the configuration extension, then the following error occurs when you try to start with the '/ C Start Update Database 'error:' An error occurred while performing the General Purpose function. Identifier of the Metadata object () The metadata object 'Directory.Station' did not find the identifier in directory 'Identifiers of metadata objects' and the information register 'Identifiers of extensions version objects'. 'It is recommended that Dalle update the auxiliary data, which, in fact, could not be started. Perhaps someone has encountered a similar problem?
![1c The Identifier In The Directory Identifiers Of Metadata Objects 1c The Identifier In The Directory Identifiers Of Metadata Objects](https://patentimages.storage.googleapis.com/US6587856B1/US06587856-20030701-D00010.png)
I will be happy if someone tells me which direction to dig.
In 1C Enterprise 8.3 many have already encountered an error: An error occurred while executing the General Purpose function. Identifiers of the Metadata object () The identifier in the Metadata Object Identifier Directory was not found for the Metadata Object XXX. For the developer: it is possible to update the auxiliary data that affect the operation of the program.
A designation used to uniquely identify the object within the preservation repository system in which it is stored. Each data object held in the preservation repository must have a unique identifier to relate it to descriptive, technical, and other metadata.
To perform the update, you can: - use the external processing of the 'Developer Tools: Update ancillary data' - or run the program with the command line option 1C: Enterprise 8 '/ C Start Upgrading the Information Bases' - or increase the version number of the configuration so that when the next startup, base. For solutions to this error, I suggest you that is ideal for any configuration of 1C Enterprise 8.3.
Contents [] • • Unique identifier (GUID) If you met in the record database ', then it's time to get acquainted with the Unique identifier. A unique identifier is a unique set of characters that characterizes an instance of object-type metadata in 1C (example, element or document). In fact, the link is a unique identifier, and even for different types of objects it can not be similar.
It looks like this: de80b7c8-aa22-11dc-a0f4-0011d85708ff Ie. This is a set of 32 hexadecimal digits separated by dashes. The caption appears in the database when there is a link (unique identifier) to the object, and there is no object in the database. This can occur either when deleting objects without using the referential integrity or when exchanging between databases. For an example, write: (36: 9c4e0022642fda9811e10393c0d776fd) To get started, find out what type of object was deleted, we use the GetStructure method to store the DatabaseBase (), it returns a table of values (by default in SDBL format) where the correspondence of internal identifiers and metadata objects is indicated. For example, you can write this code: TZ = Get the Database Structure Storage Database (); Select. (); In it, we find an identifier that in the end contains 36 (digits before the colon), but not in the number (Document2836), but the exact match.
In our case this is the following line: Reference36 Reference.Nomenclature Means the deleted item was an element of the directory 'Nomenclature'. As you noticed inside the brackets there is an object type and a unique identifier with a string. Now we can find the deleted element on one of the archival copies by adding hyphens to the ID string we have: GUID = New Unique Identifier ('9c4e0022-642f-da98-11e1-0393c0d776fd'); Reference RemoteUnit = Directories.Nomenclature.Get the Reference (GUID); Knowing all the values of the fields, we can manually recreate the remote element with the help of treatments, but they will have one main difference - different Unique identifiers. And if we want to restore the element, then the identifier needs to be restored the same. To do this, you need to use the 'Set NewList' method, for example: Restore Item = Directories.Nomenclature.CreateElement (); GUID = New Unique Identifier ('9c4e0022-642f-da98-11e1-0393c0d776fd'); Reference RemoteUnit = Directories.Nomenclature.Get the Reference (GUID); Restore Element.