Skip to main content
Jun 3, 2025 9:34 PM UTC
Acknowledged

Paste Special with many features failed (Suggestion for improvement)

Related products:Creo Parametric

When trying to transfer many features from one component to another component with paste special, an error occurs because wrong references was selected. But I don't want to cancel the "paste special" now, because I know the rest fits.
In addition, the error is not in the failed feature "chamfer" but often one featuer before it. In this case, the error is in the points feature, but I can't get to it to fix it without losing everything else. very unfortunate.

Creo Parametric 7.0.11.0

9 replies

Jun 3, 2025 10:24 PM UTC

You are referring to components which implies assembly mode, but I suspect that you are in part mode copying features from one part model (source) to a target part model. Please confirm this. It is not clear how many, or which features you are attempting to copy from the screenshot. Copy/paste will automatically map references if they exist in the target part. Are you certain you must use paste special to achieve your goal?

 

Almost certainly there is a problem with a reference in the source model that you can probably resolve but it is difficult to determine without access to your models. If you can, post the models and identify what features need to be copied from the source to the target model.

 

If you are certain that the issue is with the datum point feature and this is a single point of failure in this context then add the datum point to the target part manually and then use copy/paste special and map the references.

Jul 11, 2025 11:59 AM UTC

Yes, I mean the part mode. The features to be copied have no references to an assembly. Thanks for the feedback, but I'm not looking for a solution (I'm aware of all the suggestions), I'm asking for consideration in the further development of the user experience.

My dear readers, give me a Kodus if you also think that this would be a significant improvement in handling.
The model tree can already handle non-regenerated features, why can't the special insert store the features in non-regenerated form and keep the already assigned new references during the special insert process. It is frustrating to have to cancel a complex insert and also lose assigned references (>30), even though the error was triggered by another feature.

Jul 11, 2025 12:06 PM UTC

@WoodBeeJoe 

The appropriate board for improvement suggestions "IDEAS" is here https://community.ptc.com/t5/Creo-Parametric-Ideas/idb-p/creoparametric

You can ask a community moderator to move this post if you prefer or you can make a new post. There are certain requirements for access to the Ideas board.

Jun 9, 2025 5:26 PM UTC

The best way to do this is with a UDF. Create a UDF of the features that you want to copy and define the names of the items that build each feature. That makes it easier to create them in the new part. See the below article for help with creating a UDF.

 

https://www.ptc.com/en/support/article/CS37426?source=search

Jun 9, 2025 5:36 PM UTC

I would not agree with the assertion that UDFs are the best way to deal with copying features between models. There are many instances where I use copy/paste and copy/paste special without creating a UDF. Creating UDFs is not something easily done on the fly whereas copy paste can yield near real-time results when modeling. With the introduction of multi body support for top-down design functions, I am even less likely to use a UDF in some cases.

Jun 9, 2025 7:58 PM UTC

I should have said that my experience with copying many features, the best results have been with a UDF. I also just copy/paste if it is just a few features.

I haven't had any experience with using the multi-body function.

Community Manager
Jul 17, 2025 2:02 PM UTC
Status changed to: Clarification Needed

Thank you @WoodBeeJoe for publishing your idea. However, we ask you to please organize the information as per the questions in the submission form, also posted below.

Please let us know within the next two weeks.

1. What version of the software are you running?.
2. What is the problem?
3. Are you using a workaround? If yes, please describe it.
4. What is the use case for your organization? Describe how your idea would work in context or how it would apply to a practical situation.
5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.

Jul 17, 2025 8:17 PM UTC

@Catalina 
1. What version of the software are you running?

Creo Parametric 7.0.11.0

2. What is the problem?
When using "Paste Special" to transfer multiple features from one component to another in part mode, an error occurs due to incorrect references. However, I don’t want to cancel the operation because most of the features are correctly referenced. The issue is that the error message points to a later feature (e.g., a chamfer), but the actual problem lies in an earlier feature (e.g., a point feature). Unfortunately, I cannot access or fix the earlier feature without canceling the entire paste operation, which would result in losing all progress.
Note: This issue is specific to part mode. In our organization, "Paste Special" is not used in assembly mode.

3. Are you using a workaround? If yes, please describe it.
Currently, there is no effective workaround. Canceling the paste and redoing the entire operation is the only option, which is time-consuming and inefficient.

4. What is the use case for your organization?
In mold design, we often reuse complex feature sets across components. Efficiently transferring these features is essential for maintaining consistency and reducing design time. The inability to selectively fix references during a paste operation disrupts this workflow significantly.

5. What impact does this problem currently have on your organization?
This issue affects multiple users and leads to repeated manual work, resulting in lost productivity. Each failed paste operation can cost 30 minutes or more, especially when dealing with large feature sets.

Community Manager
Jul 18, 2025 6:50 AM UTC
Status changed to: Acknowledged

Thank you @WoodBeeJoe for your idea. Based on the information you provided, we are acknowledging it as the Community management team. This is not a commitment from the Product team. Other users may comment and vote your idea up.