-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] - Segments will not display due to "New Line" labeling #251
Comments
Reported to Esri, you have successfully submitted your support request. Your new case number is: 03585008. |
Just finished an Esri Support call. We confirmed that we can replicate the issue if we clone the SARCOP feature layer, but she is not able to replicate from a fresh layer itself. We were able to get some error codes and am sending her a HAR file for now. We will go ahead and fix our web map labels for now and Esri will use this cloned feature layer for testing. https://napsg.maps.arcgis.com/home/item.html?id=b61eff6326204d20b69aeee6f89687cf#overview |
Web Map used in WAB: https://napsg.maps.arcgis.com/home/item.html?id=904575e13cf04ebfb9bdfc4ee0f48cbb Compare for location Owensboro, KY JS SDK 4.28: https://codepen.io/avezina/pen/MWRmogd JS SDK 4.29: https://codepen.io/avezina/pen/GRLmEKO Confirms that it looks like may be regression for JS SDK between 4.28 and 4.29 |
Workaround for now.
Format should look like this. |
Here is the result. https://napsg.maps.arcgis.com/home/item.html?id=b491ee06d5d94183956ced157b35d004 At this point in time, I see that the fourth feature with neither Field 1 or 2 filled out, is entirely blank on screen but does show up in the data table. And after returning the map, I know see only partial drawing. In the below "1" is with both fields filled out. "4" is with no fields filled out. It seems really inconsistent, but I can definitely observe the issue. Here is the error I am picking up in the console |
This now logged as a defect, will monitor until fixed and then close this issue. We will have to go back and fix our maps with the new script. Field Maps and QuickCapture can't read the "two label" workaround implemented above. |
Addressed by ESRI - closing. |
Which app?
Dashboards
Describe the Device, Operating System, and Browser
Laptop, Windows, Edge
Describe the bug
Search segments (polygon feature layer) will not display unless Segment Name field is filled out. This fields is used as a label on the map so it is potentially a labeling issue bug.
Expected Behavior
The search segment features should display even when these fields are not filled out.
Reproduction Steps & Sample
Other Relevant Info
This appears to have started AFTER the ArcGIS Online release. Here is the version of Edge I am using
Also on Chrome, I will try the update next
Confirmed that this is not caused by Dashboard embedded in Experience Builder, tested on stand alone Dashboard
https://napsg.maps.arcgis.com/apps/dashboards/a6637762c84a47a7958a4e3601cd071f
Confirmed that this is not caused by Dashboard applications, tested in the web map
https://napsg.maps.arcgis.com/apps/mapviewer/index.html?webmap=ae14c820e00d492d90428aefaa01422a
Confirmed that this is not caused by web map viewer, happens even in the Visualization tab, so I think this is a Javascript API issue https://napsg.maps.arcgis.com/home/item.html?id=5f67f852d0f043799d7509efdaa16ad2&sublayer=5#visualize
The arcade expression being used is $feature["segment_designation"] + TextFormatting.NewLine + $feature["team_name"]. Perhaps it is an issue with "new line" expression? When I turn lables off - the issue disappears. Also if I keep the expression simple without NewLine, it goes away.
Priority impact
p1 - time sensitive
Impact
This will be confusing for end users who are quickly drawing search segments and intend to go back later to name them.
The text was updated successfully, but these errors were encountered: