topic Fields that symbology is based on are missing in mobile app in ArcGIS for Windows Mobile Questions

Fields that symbology is based on are missing in mobile app

AndrewBrown — Wed, 17 Jul 2013 13:40:05 GMT

Has anyone had problems where Fields disappear in the Edit Attributes window if they were used for basing symbology off of them in the original map document?
This is version 10.1.1 MPC with an ArcMap 10.1 map document.

Re: Fields that symbology is based on are missing in mobile app

ChristopherOlsen — Thu, 18 Jul 2013 12:46:55 GMT

I think there is already a bug logged for this:
#NIM089434 When updating existing features in ArcGIS for Windows Mobile, a field used for a unique value render is not available to be edited in ArcGIS Mobile.

Re: Fields that symbology is based on are missing in mobile app

AndrewBrown — Wed, 21 Aug 2013 15:20:24 GMT

Thank you Chris.

Re: Fields that symbology is based on are missing in mobile app

JoshuaCimera — Tue, 03 Sep 2013 05:20:02 GMT

I think there is already a bug logged for this:
#NIM089434 When updating existing features in ArcGIS for Windows Mobile, a field used for a unique value render is not available to be edited in ArcGIS Mobile.

Any update on this bug? We are having the same issue using 10.1.1

Re: Fields that symbology is based on are missing in mobile app

AndrewBrown — Tue, 03 Sep 2013 10:03:37 GMT

Unfortunately no, we've tried a few ways to work around it. Since our situation only requires two different symbols, we've tried two layers, with definition queries instead of a single layer with category based symbols but it doesn't work very well. The bug states it is fixed in the current build. Although I don't understand what that means. I re-downloaded mobile 10.1.1 thinking they might have fixed it, without incrementing the build numbers but it still doesn't work. I should mention that we have been able to get this working with line features stored in a 10.0 geodatabase. Andrew

Re: Fields that symbology is based on are missing in mobile app

BartPouteau — Thu, 05 Sep 2013 19:31:08 GMT

I just had a conversation with ESRI Tech Support regarding this bug fix. Apperently the issue has been resloved in Mobile 10.2. No set release date but figured it should be soon.