Preview: View the conflicts - Intergraph Smart Reference Data - Help - Hexagon

Intergraph Smart Reference Data Help (10.1)

Language
English
Product
Intergraph Smart Reference Data
Search by Category
Help
Smart Materials/Smart Reference Data Version
10.1

A conflict arises when the data from the source specification is already available in the target specification and the list of conflicts are displayed in the Preview tab.

Preview

Conflicts are displayed only when you copy a specification from Project to Product Group.

The application checks if the dependent data details are available in the target. If available, the matching dependent data is displayed as conflicts in the Preview tab. The internal details corresponding to the dependent data that are shown in the following table are not checked.

Dependent Data

Corresponding Internal Data

Commodity Group

Commodity Rule, Object Parameter , Standard, Attributes, and Commodity Group Nls

Commodity Part

Commodity Rule, Part Object Parameter, Standard, Attributes, Documents, PDB info, and Commodity Part Nls

Commodity Rule

Commodity Rule details, Commodity Keys, and Interface/Company Commodity Keys

Commodity Code

Commodity Rule, Object Parameter, Tables used, Attributes, Commodity Code Nls, Commodity Code layout, and PDB info

Object Parameter

Object Parameter Details

Table Name

Table Links, Table Attributes, Interface/Company data and underlying Table Groups, and Table Details

Table Group

Table Group Links and underlying Table Details

Table Details

Table Detail Attributes, Parent Table Details, and Table Detail Nls

Spec Header Geometric Table Name

Table Attributes and Table Values

Geometrics

Table Attributes and Table Values

Though the corresponding internal data is not checked, the Interface/Company data corresponding to the dependent data is checked and created in the target specification if it does not exist.

Following are some special scenarios for dependant data

Question 1: What happens to the Geometric data?

While copying, if the Geometrics and Tables are not available in the target, then the system does the following:

  • Creates Tables in the Table Management page,

  • A Geometric is created in the Geometric Management page and it is associated to the Table.

    While creating the dependent data for Tables, all the associated details such as Table Attributes, Table Details etc are created too.

Question 2: What happens to the Interface or Company Commodity Rules when the Commodity Rule is at conflict?

  • No conflict at Interface/Company Commodity Rule: It means that the Interface or Company names are not available in the target specification. Therefore, the Interface, Company, and the dependent Interface Commodity keys and Company Commodity Keys are copied to the target specification for the corresponding SRD Commodity Rule.

    The newly copied Interface or Company Commodity keys are then added to the Commodity Rule under the Commodity Attributes grid if not available and the checkbox Required will not be selected. If required, you can manually select the checkbox.

  • Conflict at Interface/Company Commodity Rule: It means that the same Interface or Company names already exist in the target specification, the application will not check for the Interface Commodity keys or Company Commodity Keys. A conflict is displayed.

Question 3: What happens to the Interface or Company Table Details when the Table Details is at conflict?

  • No Conflict at Interface/Company Table Detail: It means that the Interface/Company Table Details are not available in the target specification and they are copied. 

    After copying, if the table attribute is not available in the target Table Attributes grid, it is added to the grid only if the table attribute is used in the Table Details for Interface/Company.

  • Conflict at Interface/Company Table Detail: It means that the same Interface or Company Table Details already exists in the target. Therefore, no data will be copied.

Question 4: What happens to the Interface or Company Spec Header Notes when the Spec Header Notes is at conflict?

  • No Conflict at Interface/Company Spec Header Notes: It means that the Interface/Company Spec Header Notes are not available in the target specification and they are copied. 

  • Conflict at Interface/Company Spec Header Notes: It means that the same Interface or Company Spec Header Notes already exists in the target. Therefore, no data will be copied.

Question 5: What happens to the Interface or Company Item Notes when the Item Notes is at conflict?

  • No Conflict at Interface/Company Item Notes: It means that the Interface/Company Item Notes are not available in the target specification and they are copied. 

  • Conflict at Interface/Company Item Notes: It means that the same Interface or Company Item Notes already exists in the target. Therefore, no data will be copied.

  • Procedure for Preview tab

  1. Preview the list of conflicts (if any).

  2. Click Copy to copy the source data that you have selected in the Copy Scope tab into target specification.

  3. At the prompt, click Yes. The copied specification is displayed in the Copied Specifications window.

  4. (Optional) Change the specification name in Target Spec Code column and click Save.

  5. Click Close.

No duplicates are generated in the target specification while copying. That is, if the data already exists in target specification, that data is not copied to the target specification to avoid duplicates.