Order Field Value

blaize
Kilo Contributor

Hi,

I would like to ask if there is a certain max value in the Order field because we have tried using values around 1000 - 2000 but it seem to not be working with that values.

In this case, i would like to ask what is the maximum input value for Order field?

Moreover, what is the best practice in using this field?

Thanks for the help.

13 REPLIES 13

yetesh_ch
ServiceNow Employee
ServiceNow Employee

Hi,


I checked that Order field in Task table is of type INT of max length 11. Screen Shot 2015-09-07 at 7.51.10 PM.png


Moreover, it is given that max. value of 2147483647 is allowed. Check this link


http://stackoverflow.com/questions/7171312/what-is-the-max-number-if-i-store-int255-in-mysql


blaize
Kilo Contributor

Hi Yetesh,



thanks for the response, but in our dev, we have tried using values for 21 variables ranging from 100- 2000 for value in order. When we go to the requested catalog item, some of the fields are not being displayed. not until we change the value of the order same as seen in the screenshot below:


order.PNG


Using the updated order value as seen above, all the fields are now visible. what could have been the problem with the order value?



Thanks for the help.


You may have a Catalog Client Script or UI Policy that is hiding a container and some of your variables are numerically within that container.



As for numbering, I like to use large numbers because that gives you flexibility to add in variables without having to renumber a bunch of them.   I'll usually number variables within a section/container within 1,000 or 10,000 intervals, so the first section would start at 1,000, the next 2,000 and so on (or 10,000 and 20,000).   For the variables within the sections, depending on how many I already know I need, will be numbered in increments of 50 or 100.


srinivasthelu
Tera Guru

Hi Blaize,



Normally Integer fields maps to MYSQL Integers(11 digits)



so it should not impact the functionality with the values you have chosen.       It might be that other conflicting Rules overriding the functionality.



As the Best Practice goes, Normally i never saw any implementations that require pretty huge values. 1-1000 should be fine enough.



Thanks


Srinivas