When various design variants (configurations) are used
Example consider the following model files in structure:
| Model File | Configuration | Originating Item | Item-ID | Comments |
|---|---|---|---|---|
| 5020.sldasm | Default | Yes | 5020 | |
| 5011.sldprt | Default | Yes | 5011 | |
| -do- | V1 | - | - | Not captured |
| 5012.sldprt | Default | Yes | 5012 | |
| -do- | V1 | - | - | Not captured |
| 5013.sldprt | Default | Yes | 5013.DEF | |
| -do- | V1 | No | 5013.V1 | |
| 5014.sldprt | Default | Yes | 5014 | |
| -do- | V1 | - | - | Not captured |
The assembly has the following structure(first-level child):
| Parent Model / Configuration |
Child Model |
Child Configuration |
Quantity | Balloon-ID | Comments |
|---|---|---|---|---|---|
| 5020.sldasm (Default) | 5011.sldprt | V1 (not captured) | 1 | 1 | Because V1 is not captured, and Default is not used as a first-level child within the parent, so Balloon-id of V1 will be used. |
| -do- | 5012.sldprt | Default | 1 | 2 | Because the configuration has its own item and is used within the structure as first-level child item, so its Balloon-id will be used. |
| -do- | 5012.sldprt | V1 (not captured) | 1 | 3 | Because V1 is not captured, and Default is used as a first-level child within the parent, so Balloon-id of this will not be considered |
| -do- | 5013.sldprt | Default | 1 | 4 | Because this configuration has its own item and is used within the structure as first-level child item, so its Balloon-id will be used. |
| -do- | 5013.sldprt | V1 | 1 | 5 | Because this configuration has its own item and is used within the structure as first-level child item, so its Balloon-id will be used. |
| -do- | 5014.sldprt | Default | 1 | - | Balloon-Id is missing (or bal-loon deleted). |
| -do- | 5014.sldprt | V1 (not captured) | 1 | 7 | Because V1 is not captured, and even when Default is used. However, the Balloon-id of Default is missing, so the Balloon-id of V1 will be used. |
- Create a drawing for the assembly as shown below:
- Perform the Save to PLM operation on this drawing. The item structure in PLM can be as
follows:
Note:
If a configuration has its own item, and the Balloon-id for the configuration is missing,
then:
- If the target field is FIND_NO, its value will be generated automatically by the integration.
- If the target field is other than FIND_NO, its value will not be modified in PLM. Its old value, if any is retained. If this is newly getting created, then its value will be set as empty.
If the target field is FIND_NO, then its value will be generated automatically by the integration. If the target field is other than FIND_NO, then its value will not be modified in PLM. Its old value (if any will retain). If this is newly getting created, then its value will be set as empty.