Domains\Invalid Value

[JeffAzevedo]

Anyone using Domains having mobile respond with 'Invalid Value' even though it's set properly? For example a street name of "Broadway" already populated in the field, when identify or manage edit is used, mobile responds with a 'Invalid Value' on the field. Pulling down the domain list and re-selecting the exact same name "Broadway" from the domain satisfies the error? How could a Domain act up like this, could it have something to do with 'Null' values? Is this another Mobile Bug/Feature.

[AkhilParujanwala]

Spaces, if you don't properly Trim all the spaces you will get this problem. I think I had this problem once and quickly realized this problem.

If you don't mind explaining a little further how the Broadway problem was created.

Did you auto populate that field with the word Broadway, but the domain doesn't like it, so when you manually click on the field and select Broadway it works?

This is just an idea based on what you have written. I have no experienced any bug/issues with domains, yet. (been using them since 9.3)

[JeffAzevedo]

I field calculated the street names against the domain in Catalog or ArcMap. (can't remember which now) In the desktop environment. There are no problems with the domains that I can see, but once I get the data on one of our Trimble/Juno's the 'invalid value' pops up when the user identifies or tries to use manage edits. The domains include street names and street signs. If a new Post feature is added the sign domain also shows 'invalid value' and I figured this may have to do with 'Null'. It's also odd to me that the domain doesn't show 'Null' in the drop down, just "none" along with the list of actual signs. (edit: I did not add "none" to the domain, it just shows up?)

[AkhilParujanwala]

that's correct you need to add "none" to all domains and make it the default value. You will need to re-deploy the application. Updating domains don't happen automatically (I think).

[JeffAzevedo]

I assumed that it would default to 'Null' like it does on the desktop, but I guess it behaves differently on mobile. I didn't add 'none' to the domain, yet it appears as an option on the domain in mobile already. I will try and add 'none' to the default value and see if that helps. I'm still wondering where 'none' comes from, and will I be able to add it to default when it really doesn't exist in the domain. If that's the case, I will try and add it to the domain.

Thanks very much for the help AkhilP

[JeffAzevedo]

I don't think they (ESRI) are at the point of confirming this as a bug yet, but it is a known problem that has popped up occasionally. It does appear to be related to 'Null' values with Mobile. At least the Domains still work, it's just a work flow annoyance. I bet it gets fixed in the next patch.

[AkhilParujanwala]

I had this problem is 9.3. The reason why this problem exists as far as I know, is that if you try to create a feature, ArcGIS Mobile tries to create the attributes immediately. If the domains (coded) don't have a default value, it won't make a new record in the table. Thus you will get an error.

I have 2 coded domains and one range domain, the coded ones I had to make a default, and so I made it "none" which is an option in the selection. For the range domain you can leave that empty with no default.