Latest Contributions by DougBrowning

See the green mark on the field Number.  That means its a reserved word and you cannot use it. Also you can just do ${Fire_Station} in the calc.  Pulldata is for grabbing from a service.  If the label and name are different you can use jr:choice-name(choice_name, 'question') to get that.   See here for more info https://doc.arcgis.com/en/survey123/desktop/create-surveys/xlsformformulas.htm  ... View more

Also looking for a way to get the field name vs the alias as we can no longer use the CSV since it has spaces in the column names. https://community.esri.com/t5/arcgis-experience-builder-ideas/table-widget-export-to-csv-is-using-the-field/idi-p/1619062  ... View more

select one and multiple are a special case as there is no way to program that in excel so they are fine.  I know that is a bit weird but they did the best they could with excel.  So yes you just have to know which are ok to be green. ... View more

First I would make sure its not a really large image.  We had some users trying to send screenshots that were huge. ... View more

One change to make is you have to check empty before using first.  The sample code they have out there is wrong.  I told them but it never got changed.  If you call first on an empty list it fails. For filter not sure why the @ symbol is in there?  I do it like this with a sql in a var and it works.  Also note wrap filter around the FeatureSet call is faster since its one call not 2.  Also set return geo to false is faster. var EvaluationID = Concatenate($feature.PlotID, "_", text(ToLocal($feature.FieldEvalDate), "Y-MM-DD")) var sql = "EvaluationID = '" + EvaluationID + "'"; var tbl = Filter(FeatureSetByName($map,"Site Evaluation", ['EvaluationID'], false), sql); hope that does it. ... View more

Trying to get on but early adopter site is down.  Getting Page Not Found ... View more

@Wei_Ying  We are now seeing some of our layers show up on the list so thanks for fixing that. It is still telling me some layers are hidden with the public message but not which ones so I cannot track it down.  Still not sure why this message is there since this is a internal geoprocessing service so the layers should not need to be public.  It should only block non public layers for AGOL geoprocessing tools correct?  That makes sense but not a instant block if its not a AGOL tool.  What logic is being used to block some layers and list others?   Also it is still not respecting selections in the map on the layer as input.  Is this going to be fixed?  Users are confused that this is not working since it does work in Pro with the exact same geoprocessing tool.  Selections into tools as always been part of Pro, ArcMap, and WAB in the past.  This same tools works great with selections in WAB so its been hard to have to retrain our users after all these years.  I could also see adding a action to link the map and analysis widget. In addition when using Set as Analysis input in WAB it was smart and would only show me tools that took a polygon as input when coming from a polygon for example.  ExB is listing all tools no matter what the layers types are.  That would be a nice fix as we have users trying to run a polygon into a point layer tool for example.  Then we get support calls.  Matching WAB would be a good first step. thanks a lot   ... View more

@Wei_Ying   Any update on this?  We still cannot get selections to work a year later.  thanks a lot! https://community.esri.com/t5/arcgis-experience-builder-questions/select-widget-cannot-connect-to-analysis-widget/m-p/1626374   ... View more

@Wei_Ying  We cannot get the Analysis widget to see selections at all either.   Many ways do not work.   https://community.esri.com/t5/arcgis-experience-builder-questions/select-widget-cannot-connect-to-analysis-widget/m-p/1626374    We have been stuck for months now.  thanks ... View more

If there is a way to fix the Analysis widget then to see selections?  We have been trying for months and the Analysis widget cannot seem to see selections from anything.  thanks ... View more

Have you found any way for the Analysis widget to see selections?  It just ignores them. ... View more

@JRhodes  Have you found any way to get the Analysis widget to see selection from the Select widget?  It totally ignores the selection when it is input to the geoprocessing tool.  Every other Arc product respects selection on tool inputs.  thanks ... View more

We have found this workaround Manually in some setting in ExB buried deep - you have to flip it from honor the layer properties, to custom (to get it to actually honor the layer properties). Then if there are more than 50 fields you have to scroll through and turn them back on, because it restricts to 50 by default when you do that for some reason. ... View more

I could share the app but not the layers.  But its an easy one to see and it happens in all ExB we have ever built.  So nothing to do with ours specifically.  It is AGOL ExB.  Basically the Analysis widget is blocking ALL non public layers from being used.  It does not seem to check which tool it is. The tools are our own custom geoprocessing services running on ArcServer 11.3.  They are not AGOL.  So that means the layers do not need to be public for the gp tool to work.  I can see why they would need to be public for AGOL geoprocessing tools.  But internal there is no reason to block this list.  I think this is simply a hardcoded in block where they forgot that geoprocessing services can be custom and thus the layer would not need to be public.  I think its just an oversight and easy fix. If you go through the Set as Analysis Input button off the popup these tools work just fine.  So again no need to block them from the list. But in some ways we have found all of this may not matter until honoring selections gets fixed.  I detailed that here  https://community.esri.com/t5/arcgis-experience-builder-questions/select-widget-cannot-connect-to-analysis-widget/m-p/1626374#M19453   But basically the Analysis widget ignores selections completely no matter how we make them.  See posts for all the ways that do not work.  Making a selection then having a toolbox honor that is a core Arc function that has been in every product ever so we were pretty surprised by this one.  It is simply how toolboxes work.   thanks a lot and hope that all makes sense. ... View more