Capital™
Capital forces to change design name when copying or importing design to another database
2023-09-13T06:58:09.000-0400
CapitalCapital Harness DesignerCapital Connectors
Summary
Capital forces to change design name when copying or importing design to another database: “Design with same name but with different base id already exists. Hence it cannot be copied as a revision” (see the screenshot in next section)
Details
We can observe the issue if we try to import design into a new, empty database. Let’s first create there a harness design with the same Name, Revision and Short Description as some test design in our current DB:
In Capital Harness Designer, make an import into new database having only this single harness design: observe that design name is in red and we have to change it:
Change Short Description and Revision, it’s not enough, all the values are still in red. Click “Advanced…” button and try in Wizard: observe the message when hovering the mouse over the “Name” field: “Design with same name but with different base id already exists. Hence it cannot be copied as a revision”:
If we are copying or importing design from a source project to the target, and the design with the same name already exists, then the mandatory rule is that both of them should have the same base id. Base id is unique identifier tag which connects multiple revisions together. Capital is comparing these unique identifier tags which are created as the designs are being created. If the base ids don’t match, designs cannot be treated as a revision of each other.
Designs with the same names but different UIDs can appear also in the same DB causing the same message:
When “As Copy” is used during the project export, all the UIDs for the project’s objects get reset
When designs are copied from one project to another one and the 'Copy as Revision' box is not checked. This copies the designs with new UIDs