How many times did you wanted to change the name of something, WITHOUT changing the data type?

Please make this happen, or have a setting to disable the Data Type prediction auto-change.

Do you mean no DataType hinting on LowCode platform?

No i don't mean hinting, because it will automatically change the data type while chaning the variable name.

Hi Hugo,

I agree with you, this is mighty annoying, especially because the auto-guessing could be a lot smarter (e.g. first search for Entity names, and only if not found check for things like "Number"). Note however, that the guessing stops as soon as you use the variable (or parameter, attribute etc.) somewhere.

Hi Kilianm,

While creating records or some variables with not typical/simple data types (like List Records with X number of data types) while changing the name, if at some point the name or part of the name will Auto-guess something, will undo the work defining the variable and set it to some random entity.

The feature is very good, could be better but still very good. I just want the ability to temporarily/permanently disable it. 

Yes indeed, the basic functionality is a-ok, but there can be some improvements making it better.

I don't know if i made it clear on the title or i was doing something wrong, but i had this one situation where i had a variable with many data types and it frustated me that every time i changed the name of the variable it kept changing to other data types, making me to set all the data types again.

ServiceStudio is usually very helpful in 'guessing' the intended data type of a new variable or attribute. 

However, sometimes, when I change the name of a variable or attribute afterwards, Service Studio again 'helps' me by changing the data type, which I don't always want. 

It would be helpful to have a little undo button somewhere in the data type property field, so I can undo the automatically data type change, in cases where I know the original data type is what I wanted instead of the new data type that ServiceStudio thinks it should be.

Either that or a checkbox or something to "lock" the type of a variable and prevent it from being automatically changed.

Note: Once the variable/attribute is in use, the auto-typing stops happening. Problem is, it will be more clicks/interaction to lock it, than to set the type again. :(

J.Ja

Well Justin, in most cases you are correct, but I've had this issue with a variable which was a list of type record with 6 different structures and it just changed this to a simple record of one structure after fixing a typo in the name.

I don't that that a checkbox is the right solution, because you have to know beforehand that the type is going to change or you have to do the change, see that the type changed, undo the change (CTRL+Z), set the checkbox and redo the change, which is indeed a lot of extra work to prevent the change from happening.

I would like to see a similar functionality as in Word when you paste a piece of text. A small popup that auto-hides after a couple of seconds and in which you can decide if you want to change the type of keep the type and only want to change the name.

Remco Dekkinga

Like the idea! This data type guessing behavior when we rename variable/attribute is really annoying! Because of this I sometimes include in the description of the variable/attribute the data type, to be able to detect when the data type has automatically changed and I (or other developer) did not notice.

I am not sure about what the best implementation would be (undo feature, lock mechanism, other?).

Justin James,

what do you mean by "auto-typing" in:

"Note: Once the variable/attribute is in use, the auto-typing stops happening." ?

Is it "automatically data type changing"?

But I think in Service Studio even if that variable/attribute is in use sometimes the data type gets changed if you rename that variable/attribute.

Tiago -

Yes, that's exactly what I mean.

In almost 9 years of using Service Studio, I have NEVER seen a data type automatically change *after the variable is being used*.

J.Ja

Justin,

You are totally correct about "I have NEVER seen a data type automatically change *after the variable is being used*.". Myself did not realize that.

BUT, since Service Studio only validates the usage of the variable/attribute within the same eSpace, this situation still occurs, for instance, when renaming attributes in public structures that are not used in the eSpace where they are defined and are only used in the consumer eSpaces.

Tiago Bernardo

Tiago -

Got it! Yes, that makes sense. That sounds like a "bug" to me, I suggest you file it.

J.Ja

This is a love hate relationship.  The following use fits my needs:

The smart Data Type auto feature should be initially turned on for a given parameter after the parameter is created.  The auto smart Data Type auto feature will turn off when either of the following conditions occur:

•   The Data Type is manually changed from within the Parameter property window.

or

• Upon the exiting of the Parameter property window session (to some other object) where the Name property was manually edited in the Parameter property window session.

Erik -

#1 is *already* the case.

J.Ja