Plant Engineering > Part Data Tools > Part data synchronisation 
PartDataAutosync.exe / DBPlantDataImport
In both PartDataAustoSync and DBPlantDataImport you can now get an overview of how the sub-types of an archive file (i.e. VAA or PAA) are displayed as linked articles in HELiOS.
For a concrete variant, there is usually a linkage structure that looks something like this:
So in the VAA file several sub-types are defined, which are identified by an article type, which in turn is mapped in HELiOS to the attribute HEL_TYPNAME.
When the VAA file is transferred to HELiOS, the following are created:
- a document master,
- an article master for the general type and
- one article master for each sub-type.
These articles together with the general type form the main section and are connected to each other by links. The articles are characterised by the fact that identifiers are stored for them, which can be found again in the VAA file. These are the Plant IDs.
In addition, further sub-sections may have been created with the HELiOS function Derive variant 
.. These are also linked to the document master, but have no unique identifiers. Instead, these items can be assigned to the sub-types via the item type.
To get an overview of the current state of this linkage structure before matching a variant, use the function Consistency check File <-> HELiOS. This function is available in the part data sync in the context menu of the file selection.
After executing the function, the file compare_file_to_HELiOS_protocol.txt. can be found in the HiCAD Temp directory. In addition, the Notepad opens automatic and displays the contents of the file. The content looks something like this:
|
09.01.2023 09:14:12: File: A2RF1_100.vaa
General type: HELIOS:\\B00A137W6LK2UT00008TXJ_0 Status: Sub-section derived via HELiOS Article types of sub-types for which no article exists: 300 Articles without article type: none Articles with article type that does not exist in the archive: HELIOS:\\B00A137W6LK2UT00008TXK_0 HELIOS:\\B00A137W6LK2UT00008TXN_0 Articles that could not be accessed: none
General type: HELIOS:\\B00A137W6LK2UT00008TXX_0 Status: Sub-section derived via HELiOS Article types of sub-types for which no article exists: 300 Articles without article type: HELIOS:\\B00A137W6LK2UT00003NR8_0 Articles with article type that does not exist in the archive: HELIOS:\\B00A137W6LK2UT00008TXY_0 HELIOS:\\B00A137W6LK2UT00008TY1_0 Articles that could not be accessed: none
General type: HELIOS:\\B00DH4XULBEB5J000004FY_0 Status: Error: Main section with additional articles Article types of sub-types for which no article exists: 300 Articles without article type: none Articles with article type that does not exist in the archive: HELIOS:\\B00DH4XULBEB5J000004G0_0 HELIOS:\\B00DH4XULBEB5J000004G3_0 Articles that could not be accessed: none |
At the top of the file, the date and time of the check is shown, followed by the VAA file that was checked. Then follows one paragraph for each derived section. So in the above example there are three derivation sections. For each section, the article of the general type is first output as a HELiOS link. This is followed by the status of the section, i.e. main or sub-section.
Next, it is listed whether there are deviations from the ideal state in this section, such as:
- Article types of sub-types for which no article exists.
This is OK and occurs if there are additional sub-types in the VAA that have not yet been transferred to HELiOS. - Articles without article type.
Articles that do not have an article type are linked to the general type. Either this has been deleted or an invalid link has been created. In either case, this is an error. - Articles with article type that does not exist in the archive.
Usually occurs when a sub-type has been deleted from the archive. This is not an error. However, it can also occur if a link has been created to an article that does not come from the VAA file but has an article type. This would be an error. - Articles that could not be accessed.
Errors when accessing the article, this first says nothing about the link structure.
During part data sync, it can happen that the main section is no longer available in the database, usually because articles were accidentally deleted. As of HiCAD 2023 SP2 (V 2802.0), the part data sync restores the main section if it was not found.
Please note:
The function Consistency check File <-> HELiOS also checks whether "orphaned" article masters exist for the IDs stored in a VAA and reports this::
|
23.02.2023 11:08:11: File: QS-Rohr.vaa Articles outside the link structure: HELIOS:\\B00XIKCF0R3DD00000416M_0 HELIOS:\\B00XIKCF0R3DD00000416N_0 HELIOS:\\B00XIKCF0R3DD00000416O_0 HELIOS:\\B00XIKCF0R3DD00000416P_0 No articles linked to the document found |
If you perform the part data sync in such a situation, the links for the main section are repaired, the consistency check reports afterwards:
|
23.02.2023 11:09:37: File: QS-Rohr.vaa Articles outside the link structure: none General type: HELIOS:\\B00XIKCF0R3DD0000042BB_0 Status: Main section Article types of sub-types for which no article exists: none Articles without article type: keine Articles with article type that does not exist in the archive: none Articles that could not be accessed: none |
Important: This kind of repair is only possible for the main section. The sub-sections are created purely on the HEL side and have no IDs that relate the items to the VAA.
