PRISM Forum - Message Replies

Topic: PRISM Questions and Answers
Topic Posted by: SRC ( )
Organization: SRC
Date Posted: Wed Jan 12 8:33:33 US/Eastern 2000
Topic Description: Welcome to the PRISM forum! Please feel free to post your questions and comments about the PRISM assessment software here.

Back to message list About this forum

Original Message:

Posted by: Thomas Urbanczyk
Organization:SystemA Engineering
Date posted: Thu Aug 11 2:21:58 US/Eastern 2005
Subject: Assembly Copy&Paste Bug?
I came across the following critical bug: If I copy an assembly containing of sub-assemblys and components and paste it into another system (another PRISM project-file) OR even paste it into another assembly of the same system, ALL components of the copied assembly will get lost after I save the file, close it and open it again. It seems, that the program-internal component IDs get corrupted. Is there any known workaround for this serious bug and if not, could you state, when the next PRISM update is supposed to be available? Best regards, Thomas Urbanczyk


Subject: Copying and Pasting Sub Assemblies
Reply Posted by: Tammy Sehn
Date Posted: Thu Aug 11 12:52:19 US/Eastern 2005

Yes, there is a work around. As you noted, the sub-assemblies appear but the components do not. By tiling the two systems (old and new) you can drag and drop the components from one system to the other. For example: We have System Alpha with two levels of sub-assembly and new system called System Beta. We want to look at one of the sub-assemblies (we'll call this sub-assembly Assembly Q) as an independent system. Select and copy Assembly Q in System Alpha and Paste it into System Beta. Save and close the two systems. Reopen both Systems Alpha and Beta. Tile the windows so that you can both systems in the PRISM desktop. Drag and drop the components from System Alpha, Assembly Q to System Beta, Assembly Q. When this is complete, save System Beta. You can now close and reopen System Beta and the data will still be present.

At this time, we do not have a time line for the next update/release of PRISM. Without a doubt, I do expect to have this issue resolved in the next release.

Back to message list About this forum

Reply to this message