APAR status
Closed as unreproducible in next release.
Error description
SMARTEAM INVENTOR INTEGRATION: Properties Not Mapped Correctly Scenario: 1. MappingTest.gdb, create BDE alias, set as default DB connection using DB connection manager. 2. Open Inventor 6, log in to SmarTeam as 'Joe' and navigate to SmartInventor->Tools->Property Management. 'Drawing Properties' and 'Revision' are the only default mapping groups that are created. However, on page A-6 of the Inventor integration documents their property structure, are automatically written to the SMARTEAM database. The System Administrator can now use the Integration Tools Setup utility to map these properties direct to attributes in the Profile Card." I'm not sure why there are not created but I will create them manually for this example. 3. Create and save an Inventor part to test the default functionality. Create a new part and save locally. Save the part to SmarTeam. An individual profile card appears and I can modify the information. Click "OK" and the part is saved. There is no problem with this. 4. Now create mapping attribute for the Inventor Part Description field. Open Integration Tools Setup and navigate to the Inventor section. Under "Mapping Group Types" create a "File Properties" type. Open the groups tree and create groups for "Custom," "Project," "Status," and "Summary." Add a new mapping property under the "Project" category and call it "Description." This corresponds to the iProperties "Project" tab and the field labeled "Description." Add a mapping attribute to the Description and map it to Inventor Part and the field Description. We now have the Description of the Inventor part mapped to the SmarTeam Inventor part class and the description attribute. 5. Create a new Inventor part, add a description to the Project tab, and save locally. Then save to SmarTeam. The part should save correctly and the field should be mapped. 6a. Now create a new assembly and then create a new part in that assembly. Be sure to fill in a description for the part as you did in step 5. Save the assembly to SmarTeam. This is where the odd behavior occurs. when I save the assembly a profile card for the Inventor part comes up, however the description is not mapped. There are two options now. I can hit cancel or hit OK. If I hit OK the part is saved to SmarTeam and the description is filled in with the part number (which is the file name). SmarTeam then asks me where to save my assembly so I pick a project. The assembly profile card appears and I hit OK. Now the assembly and part are saved into SmarTeam but the mapping was ignored. 6b. I add a new part to the assembly and save to SmarTeam again. This time when the first profile card appears without the mapping I hit Cancel. Another profile card for the new part appears and also does not have the mapping. I hit cancel again. Now a profile card appears for the part but the description is filled in with the file name again. BUT it is the file name of the part that was already saved (so now the file name and description do not match). If I hit cancel then the part is saved but again with the wrong description. 6c. Now I will create a new assembly and create a new part in that assembly. Again, add a description to the part so we can see if the mapping is working correctly. Now do a SmarTeam save. A profile card appears but there is no description mapping. I hit cancel. SmarTeam asks me where I want to save the assembly. I pick a project and hit Save. The assy profile card appears and I hit OK. Another Inv Part profile card appears again without the description mapped. I hit cancel again. And now a third Inventor Part profile card appears and the mapping is correct. I will hit OK this time. The assembly and part are now save correctly. 7. I have also tried mapping other properties and have experienced similar results. I mapped the Inventor title property to the Inventor Drawing class description and noticed that the assembly title was mapped to the assembly description when I did a SmarTeam save. Also, if you go through a couple of examples you will see that there are problems with the mapping. 8. Since the mapping appeard to work when I save the parts individually I also tried this approach. The parts are saved fine but when I try to save the assembly SmarTeam wants to recognize the parts as new objects. So this approach is not an option.
Local fix
Problem summary
INVENTOR PROPERTIES NOT MAPPING CORRECTLY *DS PEZ on 02 Jun. =============== He Here's a problem for SMARTEAM. They agreed that it was a def So please transfer it to t
Problem conclusion
Temporary fix
Comments
THE PROBLEM WAS SUBMITTED ON : SMARTEAM VERSION 5 RELEASE 10. THIS PROBLEM IS NOT REPRODUCIBLE ON : SMARTEAM VERSION 5 RELEASE 13 GA level AND ON V5R12SP04 AND V5R11SP07 AND V5R10SP10 Comment: note that this problem is unreproducible since V5R11SP 4, V5R12SP1 and V5R10SP7. .
APAR Information
APAR number
HD07294
Reported component name
SMARTEAM NT 200
Reported component ID
569199970
Reported release
510
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2003-06-02
Closed date
2003-11-20
Last modified date
2009-06-24
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
SMARTEAM NT 200
Fixed component ID
569199970
Applicable component levels
R510 PSN
UP
R511 PSN SP51107
UP03/12/08 N 1000
R512 PSN SP51204
UP03/12/18 I 1000
R513 PSN
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS2S3T","label":"ENOVIA SmarTeam V5"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"510","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
24 June 2009