Briefcase consistency after a get
In case the External Designer removes components from an assembly structure, or he returns back only the modified files without the full structure, a check has been added at the end of the briefcase-read process in order to advise the importer that the structures may be inconsistent.
To better understand this case, please consider the following example: we call MAIN the main company site/database and EXT1 the external designer site/database.
Suppose MAIN owns the assembly A1, with parts P1/P2/P3.
MAIN
A1
+ P1
+ P2
+ P3
MAIN creates a briefcase and enables modification on A1/P1/P2/P3: the documents are temporarily assigned the OWNER_COMPANY_ID to EXT1.
MAIN
A1(EXT1)
+ P1(EXT1)
+ P2(EXT1)
+ P3(EXT1)
EXT1 imports the briefcase: his database contains:
EXT1
A1
+ P1
+ P2
+ P3
EXT1 removes the part P2 from the assembly A1:
EXT1
A1
+ P1
+ P3
and creates a briefcase to send it back: since the documents were sent for modification, after sending them back their state becomes foreign with the COMPANY_ID of the main company:
EXT1
A1(MAIN)
+ P1(MAIN)
+ P3(MAIN)
MAIN receives the briefcase and loads it, creating the following structure in the MAIN database:
MAIN
A1
+ P1
+ P2(EXT1)
+ P3
since the component P2 is not belonging anymore to assembly A1, after the changes made by EXT1.
Under these circumstances, a new dialog is displayed by the read-briefcase process, showing the following informations:
Documents with inconsistent parent-child structure
The selectable documents have been removed or not imported from the briefcase.
Select them to remove the parent-child relations in the master database.
Checking the P2 component removes the PARENT_CHILD relation between A1 and P2, fixing the A1 structure.
The need for the control explained above comes from the ability to send back partial structures only for the modified documents, excluding the documents that have not been edited.