cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Did you get called away in the middle of writing a post? Don't worry you can find your unfinished post later in the Drafts section of your profile page. X

Save as should follow attribute constraints for Name and Number

Save as should follow attribute constraints for Name and Number

According to Article CS153516 Save As does not follow the same constraints set for new part creation.  This will cause issues in downstream systems like SAP where there are limits to the number of characters.  This causes failures in the transactions to these systems ultimately slowing down your release process.

9 Comments
HugoHermans
9-Granite

It's a pity I only can vote once!

Hugo.

OliverDroop
12-Amethyst

I don't think that the title is well choosen here. If you take this idea it would prevent to copy any legacy object which has not fullfilled the constraints.

This is not practical since certain constraints get introduced later on. Since you can not change the attributes during save as this would be a blocker.

You should change the title to "Save as should follow attribute constraints for Name and Number". This is much more clear and makes sense.

See here where I have some related request for the numbering format Reg Expressions should be evaluated for number attribute

gscorpil-2
6-Contributor

I have changed the title.  I also saw a request on here to be able to change attributes during a save as which should help with the case that you describe.

PTCModerator
Emeritus
Status changed to: Under Consideration
 
jsabu-2
3-Visitor

We have a scenario with Different child types having different length Constraints for Number Attribute. When performing Save As, the current behavior bypasses the length Constraints and causes failure at downstream systems.

RABOU_Francois
8-Gravel

Issue also encountered in PDM with our interfaced ERP. Constraint on the name length is 40 characters but after Save As the user can bypass this constraint and the interface is failling.

epeterson
3-Visitor

We have just started planning our integration with SAP and this is going to be a big problem for us.  SAP has many restrictions for both Name & Number.  How can we control these in Windchill without disabling "Save-As"?.  Business rules are much too late in the process and will slow things down significantly.  

JenniferPierron
14-Alexandrite

Hello All.

 

Sorry for the late reply and I hope you have already noticed from our Release notes; but Constraints on Number and Name have been supported since Windchill 11.1 M020.

 

I am using a 12.0.2 server set up with a length restriction and Regular expression validation (to prevent illegal characters like _).  You can see in the images below that the Save As UI is giving the user a warning and won't allow continuing Save As.

JenniferPierron_0-1667298360757.png

JenniferPierron_1-1667298369434.png

 

I believe these two constraints allow you to handle any issues publishing to SAP.

 

In the latest documentation, this is noted:

https://support.ptc.com/help/wnc/r12.1.1.0/en/index.html#page/Windchill_Help_Center/cadx/CADxInfoPageActionsObjSaveAs1.html

 

Thanks

Jennifer

 

SteveShaw
15-Moonstone
Status changed to: Current Functionality

Available since Windchill 11.1 M020.  See post from @JenniferPierron  above.