Latest Contributions by JimmyKnowles

‎06-28-2019

Great. Thanks for you help with this. I think this will meet my needs, but I'll do some testing first.

‎06-28-2019

Yes, I'm creating offline map from the join view. To add some detail, the offline map will be used for editing, but on other sync-enabled layers. Are you saying that edits on the sync-enabled layers will not be able to be synced?

‎06-28-2019

Hi Khaled, thanks for your response. Here's why I'd like to enable sync on the join views. It is strictly for display, no editing. I understand that the editing takes place on the source layers. I have symbology and filters that are based on attributes that are in the join view that aren't in the source layer. If it weren't for the symbology and filters, I'd just use the source layer.

‎06-27-2019

Kanchana, I have a need to this, so I was curious if you have experienced any negative effects from enabling sync on the dynamic join view? Does anyone know what negative repercussions could occur from doing this? Thanks.

‎06-27-2019

Here's another limitation that I've run into when trying to make web maps that will work in the current version of Collector for offline use. I have a join feature layer view that I would like to have different filters on in the same map to be used offline. I can't create a view of a view, so my only option is to have multiple copies of the layer in the map. I guess I could create multiple join views but that seems like overkill and resource intensive.

‎05-30-2019

For a specific feature class/feature layer, every time I close the Layer Properties->Definition Query dialog and then reopen it, I get a duplicate definition query. It's the same exact query, just another one. Every time I close and reopen, a new one appears. I'm on Pro 2.3.3. It appears that it has something to do with the query itself since this is only happening for a specific query, but happens on a fgdb feature class and a hosted feature layer (basically same FC but published to AGOL). The query is (polygon_id NOT LIKE 'FY19-Rapid-_____-____-_' AND polygon_id NOT LIKE 'FY19-Rapid-_____-____-__' AND polygon_id NOT LIKE 'FY19-Intensive-_____-____-_' AND polygon_id NOT LIKE 'FY19-Intensive-_____-____-__') OR polygon_id IS NULL Has anyone else seen this behavior? Anything wrong with this WHERE clause?

‎05-14-2019

Trying to use the WAB filter widget for strings that begin with a space or a tab. I tried several different ways of doing this and none worked. Things I tried space in single quotes ' ' space in double quotes " " %20 %20 in single quotes %20 in double quotes I know this is possible because I can use the REST API to query for strings that begin with a space, but could not find a way to do this in the filter widget. Any ideas? This sounds like something that could be implemented pretty easily. Using a URL, for finding records that begin with a space, I use the following where clause where=survey_key%20LIKE%20%27%20%25%27 When I use the query web form at the REST endpoint, I use the following for my where clause survey_key LIKE ' %' When I hit the Query (GET) button, the URL has the following where clause where=survey_key+LIKE+%27+%25%27

‎05-14-2019

WAB filter widget for strings contains most of the filters available in ArcGIS Pro, but there are a couple that are missing. On the left is what's available in WAB and on the right is what's available in Pro. I would like to see the same filters available in WAB. Big ones that are missing for me are 'does not begin with' and 'does not end with'.

‎04-22-2019

Just to follow-up, this has been filed as a bug. BUG-000121850

‎04-13-2019

Just in case anyone else comes across this. There are two relatively easy workarounds. Enter in a "null" GUID. I.e. 00000000-0000-0000-0000-000000000000 Set the default to the same 'null' GUID for those fields. I think this needs to be done prior to publishing or in the web map in your feature templates. I've got a ton of feature templates, so it was easier for me to go back to my gdb that I'm publishing from and set the default there. Esri technical support is looking into this to see if it's a bug.

‎04-13-2019

I solved this issue with some help from esri technical support. I used fiddler to monitor the queries that WAB was making to the feature service. It appears that for the line layer it was including a list of the fields in the outFields property of the query call. One of the fields it including didn't exist in the feature layer, so the query was failing. I think the reason why it included a field that didn't exist had to do with how I originally published the feature service from Pro. Somehow I think I copied the popup configuration from other layers in my map that I published from. I know I used the 'Apply Symbology' tool, but not sure if this copied the popup configuration too. Regardless, for my polyline and polygon layers, I had the popups configured to show the Shape_Area and Shape_Length fields. This popup configuration got published as-is to the AGOL hosted feature layer. In other words, the fieldInfos arrays in popupInfo and popupElements in the hosted feature layer included those fields with the single underscore, not the double underscore (Shape_Area, Shape_Length). Those fields don't exist once it's published (only in the gdb that it was published from), but publishing the feature service with those popup configurations doesn't cause an error. The issue occurs in WAB because it appears it uses those fieldInfos arrays to populate the outFields parameter in the queries that it makes to the REST API. I confirmed that this was the issue in two ways. I used ago-assistant.com to edit the JSON for the hosted feature layer contained in the the web map that the web app was using. I added the additional underscore for every instance of those Shape fields. The info summary widget now works fine. I went back to ArcGIS Pro and the map that I was using to publish the hosted feature layer to AGOL. I reset the popup configuration and republished. The fieldInfos arrays now contain the correct names for the Shape__Area and Shape__Length fields (with the double underscore).

‎04-05-2019

I've seen this pop-up in other posts, but no one seems to have found a good answer/solution. I'm trying to use the info summary widget and it works fine for most of my layers, but there is one layer that it just won't load the features for. It just continuously displays the loading feature animation and never loads them. I've tried a lot of different things to get this to work, but nothing seems to fix it. Here are the things I've tried: Deleting all existing line features and creating some new ones Different combinations of what is displayed in the panel Publishing a new feature service w/ no relationships Different themes (dashboard, foldable, box) Various combinations of widget options Anybody have anything else I can try?

‎04-05-2019

Summary: Smart editor widget requiring field when it's not a required field. Using WAB (online edition) with dashboard theme. 'Polygon Line Key' and 'Non-Territorial Line Key' are esriFieldTypeGUID, but they are not required (i.e. nullable: true). Smart editor widget requires these fields to be populated in order to save feature. These are the only two fields that show the message 'The value entered is not valid.' This message makes sense because I didn't enter a guid, but since it's a nullable field, these values should be allowed to be blank. Creating features via the editor widget works fine as does creating features in a web map.

‎01-07-2019

Hi Phil, Thanks for the info. Since it allowed me to publish the survey, I was just curious if maybe this was allowed/possible, but not recommended or advertised. We'll figure out a different way to implement this to avoid any issues in the future. Jimmy

‎01-04-2019

I'm developing an S123 form using an existing feature service that has a common key in three related feature classes. The field name is the same, but they are in different feature classes. The Survey123 documentation states: The name column determines the name of the ArcGIS feature service column in which the response to the question will be stored. No spaces or special characters are allowed in this column. No two rows can have the same content. The feature service also has relationship classes using globalid-guid and takes advantage of this. There are several reasons why we use this common key. One is in this thread related to parent-grandchild relationships. My latest reason is for wanted to use the batch attribute editor widget in WAB. This requires that fields have the same name if you want to batch edit the same field in different feature classes. I know this is possible because I did it...the xlsform give a warning by highlighting the cells red, but otherwise it publishes just fine and collects data without any issue. But I'm just curious if this is likely to be possible in the future. In other words, is it probable that future releases will make this no longer possible.

Online Status	Offline
Date Last Visited	‎06-30-2023 04:56 PM

My Ideas

Latest Contributions by JimmyKnowles

Re: Overwrite a Feature Service used in Join Features as Hosted Feature Layer Views

Re: Overwrite a Feature Service used in Join Features as Hosted Feature Layer Views

Re: Overwrite a Feature Service used in Join Features as Hosted Feature Layer Views

Re: Overwrite a Feature Service used in Join Features as Hosted Feature Layer Views

Re: UPDATE: Cannot create offline area if Webmap has a copy of a layer in new Collector for ArcGIS

Duplicate definition queries appearing for a specific query

WAB filter widget - strings w/ special characters

WAB to have same filter options as ArcGIS Pro

Re: Smart editor widget requiring field when it's not required.

Re: Smart editor widget requiring field when it's not required.

Re: Info summary widget not loading features for certain layers

Info summary widget not loading features for certain layers

Smart editor widget requiring field when it's not required.

Re: S123 and non-unique database field name (existing feature service)

S123 and non-unique database field name (existing feature service)

Re: How to return null in Arcade with Calculate Fi...

Re: Overwrite a Feature Service used in Join Featu...

Re: Send error: Polygon input not valid

Re: Overwrite a Feature Service used in Join Featu...

Re: Using the df.spatial.to_featureclass() causes ...