topic Re: Explorer Issue Drawing Layers in MMPK in ArcGIS Explorer Questions

Explorer Issue Drawing Layers in MMPK

RyanUthoff — Mon, 17 Sep 2018 13:14:31 GMT

I am creating a MMPK with numerous point, line, and polygon layers pulling from an EGDB for use in Explorer. Recently, one of the layers is having issues drawing in Explorer. If I open the MMPK in ArcGIS Pro, the layer is visible, but in Explorer, either the layer is not visible or when it is visible, I can't select select it and access pop-ups. This layer used to work fine, but now it no longer works.

The only thing that has changed is that I added a relationship class to this layer to associate with three related tables. I'm not concerned with having access to the related tables in Explorer, I just need the point feature class to be visible and accessible. Even after removing the relationship, the layer still does not draw.

Exporting the feature class with no relationships fixes the issue, but this is not a good long term solution.

Is this a known issue or does anyone have any solutions to this?

Re: Explorer Issue Drawing Layers in MMPK

HeatherMcCracken — Mon, 08 Oct 2018 13:24:57 GMT

Hi Ryan,

I'm not aware of any known issues in this area, so perhaps we're running into something specific with your data?

Are you able to share this mmpk with me? I can investigate to see what's happening, and hopefully suggest a workaround?

My email is hmccracken@esri.com

Mark Bockenhauer‌ Joel Whitney in case you are aware of anything?

Thanks,

Heather

Re: Explorer Issue Drawing Layers in MMPK

MarkBockenhauer — Fri, 02 Nov 2018 18:54:28 GMT

Specific to this issue, it was determined that there was a field named "rowid" in the data that was conflicting with some internal runtime code. For the time being do not use field names of 'rowid' This is a bug, and the code will be reworked to resolve the conflict in a future release.

Mark

Re: Explorer Issue Drawing Layers in MMPK

RyanUthoff — Mon, 05 Nov 2018 12:49:23 GMT

I confirm that changing the field name "rowid" to something different did correct the issue.

Thank you!