Solution

During Save to PLM, the Ballooning information for a particular [model + configuration] is retrieved from various views across various sheets of a drawing. The ballooning information is read-only from the views that are linked to BOM tables of type Top-Level.

Following points must be considered for this solution:
  • The parent item [model + configuration] must either be captured in PLM or it is the default configuration of that file. The views must be for this [model + configuration].
  • If multiple views are linked to same BOM table, then the BOM information from all the views is retrieved.
  • However, if there exist multiple BOM tables in the drawing for the same [model + configuration],then integration will collect information only from those views that are linked to the same BOM table. That is, integration will not mix the information of views linked to different BOM tables.

    Example for a particular model “A1.sldasm” and Configuration “Default”, if there are 2 BOM tables (Bom_1 and Bom_2) and 4 views (View_1, View_2, View_3 and View_4). View_1 andView_2 are linked to Bom_1 and View_3 and View_4 are linked to Bom_2, and both the BOM tables are of type “Top-Level”. In this case, the ballooning information from all views linked to BOM table “Bom_1” is retrieved. If no ballooning information is found, then the ballooning information from all views linked to BOM table “Bom_2” is retrieved. In any case, integration will not combine the ballooning information of views from two different BOM tables.

  • When multiple drawings exist for the same [model + configuration], ballooning information of the first drawing is retrieved. If ballooning information is not found or if the ballooning information of the drawing is incorrect, then ballooning information is retrieved from the next drawing. When the integration finds the ballooning information in a particular drawing, it uses that for mapping the ballooning information.
  • When capture design variant is not performed, the balloon-ids are retrieved in the following order:
    • If the default configuration is also used within the assembly (as Top-Level component),then the Balloon-id of default configuration is retrieved.
    • If the default configuration is not used within the assembly as a Top-Level component, then the Balloon-id of the non-default DV (that is, un-captured DV) that is in use is retrieved. For more information, see Scenarios in Balloon Mapping.
  • When multiple documents are linked to same item, the Balloon-id of the “BOM Defining”document is given a priority. If both the documents are either “BOM Defining = True” or both are “BOM Defining

    = False”, the Balloon-id of the document with the unresolved design configuration is retrieved. However, when both the documents are using unresolved configurations or when both the documents are using the resolved configurations, then integration will pick the Balloon-id of the first one in the collection (it can be random, depending on how it is used in the assembly). See example scenarios for more details.

  • When the target field in PLM is FIND_NO, then integration checks if the same balloon-id is specified for two different child items. If the balloon-id is specified for two different child items, then the FIND_NO field for the parent item is not updated (by using the ballooning data). Old values are retained for all the child items of that parent item, because the field is unique in PLM.