ESRI Map

Hello, I believe I have found a few bugs with the mapMarkerField component:
1. Polylines appear to support name and description fields, since these can be added by selecting the line and clicking 'Update', but lines passed into the lineData parameter do not display the a name or description. The length of the line is displayed as the feature instead.

2. Updates made to the name and description fields of points are reflected in the pop-up when a feature is selected, but these values in the variable are not updated. The same goes for lines and polygons.

3. It's possible to update the name and description fields of point, lines, and polygons when the mapMarkerField is set to read-only.

Lastly, this is not necessarily a bug, but when updating the name and description fields, the "Update" button in the popup is disabled until the user unfocuses from the input field where edits were made. It would be better user experience if the button was disabled until a change in the field was detected on keypress.

I'm surprised no one has raised these issues before, hopefully they are easy to fix. Thanks!

Hi team,

We're actively using the ESRI Map Component Plugin (v1.5.2) in a law enforcement demo and have identified two bugs in esriMapMarkerField that we'd love to see addressed in a future release:

1. Pre-loaded pointData popup renders blank
When points are loaded via the pointData input parameter, the popup title and description are empty on click. This is because the popup template is constructed as a plain JavaScript object rather than using new PopupTemplate({...}) as is done for user-drawn sketch graphics. Changing the popupTemplate construction in addPointToMap() to use new PopupTemplate() resolves this.

2. onGraphicSelect depends on popup lifecycle
The onGraphicSelect save event only fires via the popup's selectedFeature watcher, meaning if the popup is slow to open or suppressed, the event never fires. Adding a direct activeView.on("click") hit-test handler inside addPopupTriggerEvents() would make the event fire immediately and independently of the popup, which is much more reliable in read-only map scenarios.

3. Feature request: disableInputPopup parameter
A boolean parameter to suppress the built-in popup for pre-loaded pointData graphics would be very useful. Many use cases (especially read-only intelligence maps) use a custom SAIL panel to display graphic details rather than the built-in popup, and there is currently no way to prevent the empty popup from appearing.

I have already implemented and tested all three changes locally. Happy to share the exact code changes if that would help speed up the fix.

Thanks for a great plugin, it's been a solid foundation for our use case!

• The following changes were made in the esriMapMarkerField -
• Removed a bug occurring when creating a Polygon on a basemap with WKID 27700
• Removed a bug caused when featureLayers is null

• The following changes were made in the esriMapMarkerField -
• Modified the baseMap and secondaryMap parameters in the component to support custom base maps from Ordnance Survey.
• Added a showLayerListSelection parameter in the component to control layer list selection visibility
• Applied minor revisions to the tableHeight and maxSelection parameters

Thanks for the new features. I want to report that after upgrading from v1.3.0 to v1.5.0, several instances of the esriMapMarker field I had been working on became entirely unresponsive and would not display data. After getting them to work again through process of elimination, I think the reason is that the instances had no value specified for the featureLayers parameter. Passing in an empty list {} appears to resolve the issue.

• Feature Table Search and Selection: A new feature table functionality has been added to enable users to search and select items directly on the map. The table performs queries based on the user’s search query input, and if no query is specified, it fetches all items.
• Search Field Specification in FeatureLayer: A new property has been introduced within the FeatureLayer input that allows users to specify the fields for search queries. This enhances the control over the search process, ensuring more relevant results based on the specified fields.
• Item Highlighting on Map: On loading the feature table, selected items are automatically highlighted on the map for easier identification. Subsequent selections in the table will update the highlight on the map.

• Feature Object Highlighting: A new parameter has been added to highlight feature objects within the feature layer, enhancing visibility.
• Circle Geometry Type: Introduced a new geometry type, Circle, allowing for more diverse mapping capabilities.
• Geometry Editing: Users can now edit the name and description of geometries for improved organization and context.
• Element Tracking: Added functionality to track feature layer elements under geometries, enhancing data management.
• Layer List : Introduced a layer list feature that enables users to rearrange and control the visibility of feature layers easily.
• Feature Layer Info Saving: Added the capability to save feature layer information, ensuring user configurations are preserved.

• Race Condition Resolution: Resolved a race condition issue within the feature layer on load.

• Fixed the issue in the Get Direction feature.

Is geofencing functionality currently available in the ESRI ArcGIS Map Component plugin, or are there any plans to include it in future updates? If it's already available, can someone kindly share how to utilize it?

• Included a parameter ‘onGraphicSelect’ to find the selected graphic in the marker component.