Latest Contributions by DaveFullerton

Working with the developer edition can be much the same as the AGOL version once it is installed. An added benefit is that sometimes an update to the AGOL version could create a new bug that breaks something that worked in the past. With the developer edition you decide when to move to the next version. The developer edition must be installed locally and the project files will be stored locally too. I have been making occasional backups of the project files because I don't know of any way for them to be stored directly on a network share.

While using the sample widget named feature-layer (https://developers.arcgis.com/experience-builder/sample-code/widgets/feature-layer-class/) I notice that FeatureLayerQueryParams has a geometry property. I have been importing JSAPI modules to do spatial queries and I thought I would switch to DataSourceComponent instead. I tried setting the property to an envelope, but it didn't work. The geometry parameter in the URL to the REST endpoint looked, like this: geometry=%7B%7D instead of this: geometry=%7Bxmin%3A+2254552%2C+ymin%3A+250692%2C+xmax%3A+2254562%2C+ymax%3A+250702%7D Is it possible to use DataSourceComponent for spatial queries? Is there some other component I should be using? See: FeatureLayerQueryParams Documentation

I tried something with the developer edition that seemed to work. I am still using version 1.1 for reasons I won't explain. The ExB projects are named with integer values starting with 0 and going up. Using project number 1 as an example, in arcgis-experience-builder-1.1\server\src\public\apps\ 1 \resources\config\config.json find the code for the widget by searching for it's label (e.g., Bookmark-1). Within the json you can cut and paste the objects to reorder them. You should probably backup the file first. Here is an example of a bookmark json object: { "id" : 2 , "name" : "Bookmark-A" , "title" : "Bookmark-A" , "type" : "2d" , "imgParam" : {}, "snapParam" : { "fileName" : "widget_2-snap2.jpg" , "originalName" : "widget_2-snap2" , "url" : "${appResourceUrl}/images/widget_2/widget_2-snap2.jpg" , "type" : "IMAGE" , "size" : 235789 , "created" : 1610661908021 , "resourcesPrefix" : "images/widget_2" , "fileFormat" : "image/jpeg" }, "imagePosition" : "FILL" , "imgSourceType" : "SNAPSHOT" , "extent" : { "spatialReference" : { "wkid" : 102677 }, "xmin" : 2241999.3155568424 , "ymin" : 208827.52623204477 , "xmax" : 2268665.9822235093 , "ymax" : 235494.19289871145 }, "viewpoint" : { "rotation" : 0 , "scale" : 40000 , "targetGeometry" : { "spatialReference" : { "wkid" : 102677 }, "x" : 2255332.648890176 , "y" : 222160.8595653781 } }, "graphics" : [], "showFlag" : true , "mapViewId" : "widget_2editor-null" , "mapDataSourceId" : null , "layersConfig" : {} }

‎12-14-2020

Thanks, Grant. I have seen no errors from webpack. There was an error in Chrome's developer tools, and I was looking for the _sourceMenuButtonNode but couldn't find it. It turns out that when there is only one source, there is no dropdown button for selecting which source you want to use. I added a second source and it now works without errors. Could you confirm that your local-search widget only works when it is on (or actually in) a map widget?

‎12-09-2020

Thanks, Grant. I had tried the folder structure both ways before with the same result. This version is better, but I still get one error in ExB v1.2 (two errors in v.1.1). Everything is green in the console, so all is good there. I just can't find anything on _sourceMenuButtonNode. Are you using VS Code? Which version of ExB?

‎12-09-2020

Thanks, Grant. I tried unzipping the folder in my "your-extensions" folder. In VS Code I am seeing a few error warnings. I encountered 1 less in ExB 1.2, but manifest.json says exbVersion 1.1. Am I missing something? Line 477 Line 519 Line 536

‎12-08-2020

If you are willing to use the developer edition you might take a look at this post: https://community.esri.com/t5/arcgis-experience-builder/jsapi-search-widget-in-custom-exbuilder-widget/td-p/1005580 Esri hasn't responded to the downsides of my custom widget, so your Kudos are welcome in case that influences their decision to respond. The code would have to be updated (very easy) to reference your own geocoding service, featureclass, or just the geocoding services in your portal if you would like (the way it is in Esri's Map widget). It is also likely that you could figure out how to update more styles on the JSAPI Search widget inside the custom ExB widget similar to what I have done by overriding the CSS width property for the input element.

‎11-30-2020

I used the Esri sample widgets 'editor' and 'js-api-widget' as starting points to create a simple custom Search widget. It simply embeds the JSAPI Search widget in the ExB widget (the code is attached for v 1.1). I got a reasonable result except for one thing. The dropdown list of search candidates does not overflow the parent div (class="widget-content"). This is demonstrated in the picture below where the ExBuilder widget has a red outline - the 3rd address candidate in the dropdown list is cut off. This is a problem when this custom widget is placed above a map. Either it has to be placed way above the map to leave room for the dropdown, or it has to be placed partly in front of the map. The problem with having part of the widget in front of the map is that it prevents that part of the map from being clicked on. The code is attached. Can anyone tell me if there is a solution for this? Another thing I ran into was a problem migrating it to ExB 1.2. The arrow keys work to navigate the dropdown list of search candidates in 1.1 but not in 1.2. With 1.2 I get an error on InputKeyup: And here is a link to the ArcGIS Idea for a Search widget in ExBuilder in case you want to vote it up: https://community.esri.com/t5/arcgis-experience-builder-ideas/search-widget-for-experience-builder/idi-p/931318

‎10-19-2020

That might work, but it would still not be very good. Let's assume you could do a point on point spatial query in the same featureclass, and you combine the information from, for example, 4 points in the pop-up. There would still be the problem of the number of pop-ups displayed. If you had 4 stacked points, you would sometimes have 1 pop-up, but more of the time you would have 4 pop-ups that would repeat the same information. It seems to me it would just lead to a different problem. However, if we were able to restrict the number of pop-ups displayed to just 1 per click, then I think your suggestion might work.

‎10-19-2020

I contacted esri support in an effort to find a workaround. They did not suggest any workaround.

Online Status	Online
Date Last Visited	9m ago

My Ideas

Latest Contributions by DaveFullerton

Re: Changing bookmark order

DataSourceComponent Spatial Query

Re: Changing bookmark order

Re: JSAPI Search Widget in Custom ExBuilder Widget

Re: JSAPI Search Widget in Custom ExBuilder Widget

Re: JSAPI Search Widget in Custom ExBuilder Widget

Re: Search Widget for Experience Builder

JSAPI Search Widget in Custom ExBuilder Widget

Re: An Option To Show All Pop-ups For Overlapping Points

Re: An Option To Show All Pop-ups For Overlapping Points