When a numeric field has an alphabetic alias in the domain, AGOL will utilize the alphabetic aliases as opposed to the numbers in all of its operations, even though it knows and reports that the field is numeric.
Because of this oversight and hinderance you cannot use relational/comparison operators on the numeric fields (<, >, etc) even though AGOL knows that it is a number.
As a result of this shortcoming and aggravated annoyance you are then forced to alter your data before publishing, where you must first create a 'staging area' and remove the domain in order to publish it to AGOL, what should be an unnecessary step and is an extremely unfortunate headache inducer (this is actually esri's recommendation, believe it or not!).
I say, treat a number as a number!!!!!!!
