Design Review File-based Design Import

• Application node are replaced
• The structural aggregations, the names and the graphical properties of Markups are lost.

• A Scene and a Presentation contained in a markup are converted into a Slide whose name is made of the name of the Presentation.
• Only one Scene or only one Presentation in a markup is converted into a Slide whose name is made of the name of the Scene or the Presentation.
• If several scenes are pointed by a Presentation, the Slide corresponding to the Presentation is created for the last- pointed Scene and a default Slide is created for the other Scenes.

During scene migration into a slide, all scene attributes, particularly scene viewpoints, are preserved.

A scene created by selecting a subproduct is not correctly imported.

• Graphical properties of Presentations are preserved.
• If a Presentation references applicative data which cannot be imported, then the links to these applicative data are removed from the created Slide. A warning message will be added in the log file.

• An Annotated View is migrated to a Slide having the same name and same viewpoint as the Annotated View plus the 2D Markers that were associated to the Annotated View.
• If the Annotated View is in a Presentation, all Markers of the Annotated View are imported in the Slide created for the Presentation. One slide will be created for the Presentation name and one slide will be created for each pointed Annotated View.
• If an Annotated View is pointed by several Presentations, the Markers of the Annotated View are duplicated in the Slides created for each Presentation.
• If the Annotated View is in a Markup, the Markers of the Annotated View are created in a default Slide.
• Graphical properties of Markers contained in the Annotated View are preserved.
• The image and audio Markers in an Annotated View are lost.

  Important: To import the data partially, you must declare the audio and the image files' extensions at Me > Preferences > App Preferences > Social and Collaborative > Global Design Management > Coexistence and Migration > File Coexistence and Migration > FBDI General > Extensions to ignore.

• Link/Unlink attribute is lost.

• If the 3D Annotation is in a Presentation, a corresponding 3D Annotation is created in the Markup, visible in the Slide created for the Presentation.
• If an 3D Annotation is pointed by several Presentations, the corresponding 3D Annotation is duplicated in the Markup, visible in the Slides created for each Presentation.
• If the 3D Annotation is in a Markup, a corresponding 3D Annotation is created in the markup, visible in the default Slide.

• A Replay is converted into an Animation of the same name.
• Viewpoint animation in Replay is preserved.
• Product positioning information in Replay is preserved.
• Product color information in Replay is preserved.
• Product opacity information in Replay is preserved.
• Product visibility information in Replay is preserved.
• Manikin motion information in Replay is lost.

• Only Measure Between, point, edge, surface and volume measures can be imported using FBDI. Band analysis measurements cannot be imported using FBDI.
• Measures are migrated with the same name they have in V5. If a Product contains two Measures with the same name, the second migrated Measure will be named [measure_name](2).
• All Measures made in 3DEXPERIENCE use the Global Axis System. It is not possible to use any other. If a Measure originally made using another axis system is migrated from V5 by means of FBDI, it will be recreated in 3DEXPERIENCE according to the Global Axis System.
• Edge limits cannot be selected using Measure Between in 3DEXPERIENCE. If a Measure comprising an edge limit selection is migrated from V5 by means of FBDI, it will be recreated in 3DEXPERIENCE with the whole edge selected which might change the measure result.
• Volume measures are not updated after FBDI migration as visualization is not created during migration. Such an update can however be done in Design Review.
• Links on Measures are not migrated by means of FBDI. If a Measure with a link is migrated, the following warning is included in the migration report: The migration of links on Measures is not supported.
• Inertia measurement data specific only to measure volume for part can be imported using FBDI.
• The option Isolate links on missing document is operational for Measures. A warning appears in the FBDI report. Measures with broken links are seen in the tree as not linked i.e. with the or the symbol depending on the command you used (Measure Item or Measure Between). If you edit a unlinked Measure, the selection cannot be changed (the default behavior of an unlinked Measure). If the option Isolate links on missing document is cleared, migration is done if there are no other FBDI errors.

• Sections are migrated with the same name they have in V5. If a Product contains two Sections with the same name, the second migrated Section will be named [section_name](2).
• A non-updated Section will not be imported as non-updated. It will be considered to be up-to-date and therefore cannot be updated.
• The option Isolate links on missing document is operational for Sections. A warning appears in the FBDI report. Only migrated Parts are taken into account in the 3DEXPERIENCE Section. Sections are not seen as broken in the tree. If the option Isolate links on missing document is cleared, migration is done if there are no other FBDI errors.