Anyone have any experience/advice for creating WTParts for documents that are 40-70 characters in length?
We are currently set up so the WTPart created in 10.1 is copying the name from the cad file. These cad files are being loaded from network drives and some have been in use for almost a decade now, and are in many assemblies.
If I try to check in these models,
ex. 3880 FITTING,PIPE,BUSHING,HEX,0.25IN FNPTX1.25MNPT.SLDPRT <- 57 Characters
then this error comes up.
The value exceeds the upper limit of "40" for "Number".
I have a few ideas how I could approach this, but it would be a very manual approach (manually create and name the Part for the cad doc) or I could simply ignore the WTPart for these files for now... I should note that I have almost 2000 of these files with freakishly long file names. And for the record, no I did not name any of these files...
Thanks in advance.
Solved! Go to Solution.
You can do it by following the steps mentioned in http://www.ptc.com/cs/help/windchill_hc/wc101_hc/index.jspx?id=WCCG_Serv_CustModeledElements_CustColumnLengths&action=show
WTPartMaster.number.UpperLimit=350
2. Run the command ant -f bin\tools.xml custom_column -Dgen.input=wt.part
3. Run the upgrademanager -cs command for comparing the schema
4.. As per the Upgrademanager output present in ptc\Windchill\Upgrade\UpgradeManagerOutputs\UpgradeReports\CompareSchema\CompareSchema-, run the sqls to modify the table.
Hope this helps...
I should mention I did just set the preference to strip the extensions of the number field so that will save me 7 characters... but this will not solve my issue.
You can do it by following the steps mentioned in http://www.ptc.com/cs/help/windchill_hc/wc101_hc/index.jspx?id=WCCG_Serv_CustModeledElements_CustColumnLengths&action=show
WTPartMaster.number.UpperLimit=350
2. Run the command ant -f bin\tools.xml custom_column -Dgen.input=wt.part
3. Run the upgrademanager -cs command for comparing the schema
4.. As per the Upgrademanager output present in ptc\Windchill\Upgrade\UpgradeManagerOutputs\UpgradeReports\CompareSchema\CompareSchema-, run the sqls to modify the table.
Hope this helps...
Hello Binesh Kumar, is it procedure for oracle db? How i can upgrade schema with MSSQL?
SQL file that generate script can not be executed by MS SQL. Here is the log:
Msg 102, Level 15, State 1, Line 1
Incorrect syntax near 'Foundation'.
Msg 111, Level 15, State 1, Line 36
'CREATE/ALTER PROCEDURE' must be the first statement in a query batch.
Msg 156, Level 15, State 1, Line 45
Incorrect syntax near the keyword 'PROCEDURE'.
Msg 156, Level 15, State 1, Line 57
Incorrect syntax near the keyword 'PROCEDURE'.
Msg 156, Level 15, State 1, Line 69
Incorrect syntax near the keyword 'PROCEDURE'.
Msg 156, Level 15, State 1, Line 81
Incorrect syntax near the keyword 'PROCEDURE'.
Msg 156, Level 15, State 1, Line 93
Incorrect syntax near the keyword 'PROCEDURE'.
Msg 156, Level 15, State 1, Line 105
Incorrect syntax near the keyword 'PROCEDURE'.
Msg 156, Level 15, State 1, Line 117
Incorrect syntax near the keyword 'PROCEDURE'.
Msg 156, Level 15, State 1, Line 129
Incorrect syntax near the keyword 'PROCEDURE'.
Msg 156, Level 15, State 1, Line 141
Incorrect syntax near the keyword 'PROCEDURE'.
Msg 156, Level 15, State 1, Line 153
Incorrect syntax near the keyword 'PROCEDURE'.
Msg 156, Level 15, State 1, Line 165
Incorrect syntax near the keyword 'PROCEDURE'.
Msg 156, Level 15, State 1, Line 177