Skip to main content
I
IanW10-Marble
10-Marble
March 25, 2025
Question

Class java.lang.string cannot be cast to class java.lang.integer when using a Reference Doc Template

  • March 25, 2025
  • 2 replies
  • 872 views

Version: Windchill 12.1

 

Use Case: I have created a Reference Document Template using an Excel Document.


Description:

When trying to create the first Reference Document using the new Template I get the attached error.  Not sure which field is creating this issue?

Catalina_0-1742917824103.jpeg

 

2 replies

Catalina
CatalinaCommunity Manager
Community Moderator
March 25, 2025

Hi @IanW 

 

Thank you for your question! 

 

Iā€™d like to recommend to bring more details and context to your initial inquiry. For example:

  • How did you configure the Reference Document Template using the Excel document? Are there any specific fields or settings you customized?
  • Have you checked the field mappings between the Excel document and the Reference Document Template? Are there any fields that might be causing the issue?

Please refer to this guideline to make your questions more likely to receive a quick and useful answer. 

This will increase your chances to receive meaningful help from other Community members. 

 

Thank you for your participation and please let me know if you need further assistance! 

 

Best regards,

Catalina | PTC Community Moderator
HelesicPetr
22-Sapphire II
HelesicPetr22-Sapphire II
22-Sapphire II
March 26, 2025

Hi @IanW 

The method server logs could help you to identify the root case.

The error just say. that you put string value in the integer type so it is not compatible

 

If your excel file contains some columns that are linked to the Windchill attribute, then be sure to use correct excel type column. 

 

PetrH

D
18-Opal
d_graham18-Opal
18-Opal
March 27, 2025

@HelesicPetr 

Petr,

 

I help Ian with this post.

You would not believe what I found.

 

The TemplatesUtilitly.changeFilename() method was failing while trying to get the filename truncation length from the preferences.

The line that failed is below.

Integer var14 = (Integer) PreferenceHelper.service.getValue("/com/ptc/windchill/enterprise/templates/doc/filenameTrunctionLength", "WINDCHILL", var13, var12);

 

The PreferenceHelper.service.getValue() method return an Object which happens to be a String in this case.  I did confirm this. And it is deprecated.

So, I hacked the class and changed it to a non-deprecated method to get the object and then create the Integer object.

 

Object obj = PreferenceHelper.service.getValue(var13.getContainerReference(), "/com/ptc/windchill/enterprise/templates/doc/filenameTrunctionLength", "WINDCHILL", var12);
Integer var14 = Integer.valueOf(obj.toString());

 

The hack works great.

I have passed this on to TS.

Curious to see what they come back with.

 

FYI, the PreferenceHelper.service.getValue() method is deprecated.  Not surprised by this.  I see this all the time with OOTB code.

 

This was good one.  Keep 'em coming šŸ˜Š

David

    avillanueva
    23-Emerald I
    avillanueva23-Emerald I
    23-Emerald I
    March 27, 2025

    So it seems @IanW stumbled on a bug? Any way it can be worked around for now? Is this avoidable?

    Terms & ConditionsCookie settingsAccessibility statement