Latest Contributions by StephanieBlazey

I deleted the web app and started from scratch.  I am able to configure the search widget without getting the "Label exists" error now.  Weird... but there you go. ... View more

Laura, were you able to resolve this issue?  I am getting the exact same "Label exists" error when I try to configure the Search widget in Web App Builder.  Thanks, Stephanie ... View more

Ok so we finally got this sorted out.  You can add an ObjectID field when you create the spatial view definition! add something along the lines of: cast(ROW_NUMBER() OVER (ORDER BY {FieldOfChoice}) AS int) AS OBJECTID ... View more

NEVER MIND!  You can't publish an MXD with a "complex" query layer, e.g. it can't have a join or a where clause. So this doesn't help at all. Onwards with spatial views with no unique ID! ... View more

I'll start off saying I'm not sure how big of an issue it is to create a spatial view and not have a unique identifier, but it seems like something that might cause issues down the road so I want to avoid it. Ok I figured this out!  (EDIT -- NEVER MIND!!  The query layer (as illustrated below) works in ArcMap, however, you can't publish a "complex" query layer (e.g. one that has joins or a where clause).  You CAN publish a "simple" query layer (no joins, no where clause).  But in my case I needed those joins and where clauses and I need to publish it so this doesn't help.  Back to spatial views with no unique identifier!) Instead I created a Query Layer in ArcMap. I'm using 10.3.1, and followed these steps: 1. In ArcMap, Click File > Add Data > Add Query Layer. 2. It will ask you to provide the database connection. (see image below) 3. Type in a name for your new layer. 4. Create a query.  I used the same SQL that I would have used to create the spatial view (which I copied from SQL server management studio). This gives you a new layer in your MXD that does exactly what your spatial view would have done, plus it adds an "ESRI_OID" field that has a true unique identifier. You can save and publish the MXD as usual.  You can even save the layer as a .lyr file to easily use in other documents. So the downside is that you don't have a spatial view in your geodatabase to easily use, but since you can save .lyr files you don't have to rewrite the SQL every time you use the same data -- or even similar data, as you can edit the query in ArcMap whenever you need! ... View more

I think I understand the problem here -- I'm creating a spatial view with a 1-M relationship, so my ObjectID field won't be unique anymore.  I need to figure out a way to create a new unique ID field in the spatial view. ... View more

I am getting the same error as Naomi's screenshot too.  Same as Anish says, the geometry looks fine in ArcCatalog and I get the error when previewing the table.  When I add data to ArcMap it asks me to choose a unique identifier field (and OBJECTID is definitely there).  Are we missing a step where we can set which field is the unique identifier when we create the view? ... View more

I think I may have narrowed down my printing issues to versioned data. The printing works fine when my feature layer uses non-versioned data (thanks to the helpful tips here), but printing fails if the data is versioned. Is this a bug? Thanks, Stephanie ... View more

Restarting ArcGIS server worked for me too!  Thank you!! ... View more