A fix is available
APAR status
Closed as program error.
Error description
Importing a previously exported ARXML file causes duplication of model elements 1) Create AUTOSAR 4.x project 2) Export project to ARXML 3) Import the ARXML file over existing project using "Update existing model elements..." setting 4) Export project to ARXML for a second time 5) Compare the two ARXML file in text diff merge
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * Rhapsody 8.1.5 iFix001 * **************************************************************** * PROBLEM DESCRIPTION: * * The import operation is trying to match and merge existing * * model elements with elements imported from ARXMLs. * * Re-importing of ARXMLs might cause duplication of model * * elements instead of merging with existing model elements due * * to the following: * * * * 1) Some meta-data is added to imported unnamed elements, * * based on their content, in order for them to match in * * successive import operations. * * Unnamed elements might not match properly if the * * corresponding meta-data is different (e.g., imported using * * Rhapsody version older than 8.1.5) * * * * 2) In ARXMLs a single SwcToEcuMapping element may contain * * many references to components and only a single reference to * * an ECU. * * In Rhapsody such SwcToEcuMapping is imported as many * * swMapping elements (or SwcToEcuMapping elements in * * Type-Based profile), each with one reference to a component * * and one reference to an ECU. * * Starting with 8.1.5, The name of the additional swMapping * * elements which are imported is determined according to their * * content, and might not match properly with exiting swMapping * * elements in models prior to 8.1.5. * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
Fixed in Rhapsody 8.2 - 1) Add the Property Boolean Model::Importer::IgnoreUnnamedIdData with "True" value to the Active Configuration, the Project or in some Properties file, such as site.prp, in order to allow to match unnamed elements under the same owner according to their order ignoring the corresponding meta-data. 2) Add the Property Boolean Model::Importer::EnableContextTagAsName with "True" value to the Active Configuration, the Project or in some Properties file, such as site.prp, in order to allow to match additional swMapping elements with the corresponding elements imported from ARXMLs (according to their referenced component) Once the elements are properly merged - the Properties mentioned above are no longer needed to be enabled.
Temporary fix
Comments
APAR Information
APAR number
PI64895
Reported component name
TLOGIC RHAPSODY
Reported component ID
5724V74RP
Reported release
814
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-06-27
Closed date
2016-12-05
Last modified date
2016-12-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
TLOGIC RHAPSODY
Fixed component ID
5724V74RP
Applicable component levels
R815 PSN
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7P9W","label":"Rational Rhapsody"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1.4","Line of Business":{"code":"LOB02","label":"AI Applications"}}]
Document Information
Modified date:
16 October 2021