Skip to main content
O
OnurNalbantoglu14-Alexandrite
14-Alexandrite
July 14, 2022
Question

Reel Number Attribute Mapping

  • July 14, 2022
  • 1 reply
  • 1586 views

I defined an attribute that I created as Real Number as a variable in the activity and I want this value to appear on the primary attribute screen. Unfortunately, the code I use when I define it as an intager does not work in real number, what should I do?

 

pictures will be more descriptive;

 

Attribute type;

onur_0-1657811158962.png

 

Creating variable;

onur_1-1657811224517.png

 

the code I use;

onur_2-1657811297613.png

 

 

 

1 reply

D
18-Opal
d_graham18-Opal
18-Opal
July 14, 2022

@OnurNalbantoglu 

Why not make the workflow variable the same object type as a Real  Number.

 

That seems the simplest solution.

 

If you have to keep it String for some reason you need to convert the String value to class FloatingPoint (which is what a Windchill Real Number is).

 

If you go the way of making a new variable you should find FloatingPoint under Windchill classes. Or just copy/paste from Type and Attribute Manager. You can see it in the upper left  where you can edit display name. It’s under Data Type (I think).

 

David

    O
    OnurNalbantoglu14-AlexandriteAuthor
    14-Alexandrite
    July 23, 2022

    I stopped using the attribute I created in the task as a real number. I will have users edit the form.

    I tried the attribute as a string to the variable, it didn't work, I tried it as a floating point, it didn't work, I tried it as java.lang.long and it didn't work. Unfortunately I couldn't find a solution. Thank you very much for your work.

    D
    18-Opal
    d_graham18-Opal
    18-Opal
    July 26, 2022

    @OnurNalbantoglu 

     

    I looked at your code and I bet you are getting a Class cast exception as you are trying to cast a String to a Double.

    That's going to work.

     

    Creating the workflow variable as FloatingPoint and Type attribute as Real Number (FloatingPoint) should work and there would be no need to cast the object returned from PersisableAdapter to a FloatingPoint as it is already a FloatingPoint.

     

    Note there is also FloatingPoint with Units.  Do not use that one as it is different from FloatingPoint.

    If this does not work and you are following this methodology something else must be wrong.

     

      Terms & ConditionsCookie settingsAccessibility statement