|
POST
|
Thanks for the reply and encouragement! I'm pretty sure version 11.3 doesn't allow for setting symbology of geoprocessing outputs through the Analysis widget like what you see in 11.5. See here.
... View more
|
0
|
0
|
11
|
|
POST
|
I am struggling with this as well (Enterprise 11.3). My geoprocessing output is visible but there doesn't seem to be anywhere in experience builder to configure the symbology of the outputs like what exists in WAB. Setting the symbology in the model works when run in ArcGIS Pro but has no effect in the published tool. Maybe I'm missing something in the publishing process?
... View more
Thursday
|
0
|
0
|
30
|
|
POST
|
Yes! Using the Search widget in experience builder, you can set a Zoom scale in the Action settings for zoom to.
... View more
2 weeks ago
|
1
|
1
|
45
|
|
DOC
|
@SubaKrishnan I second the comment above by @dheerabhat . Making this valuable tool easier to implement would be much appreciated!
... View more
06-25-2025
01:29 PM
|
0
|
0
|
8200
|
|
POST
|
@BrettMartin1 Thank you! Good to know! We are still on 11.1. Planning our update for January.
... View more
04-21-2025
07:30 AM
|
0
|
0
|
516
|
|
POST
|
@BrettMartin1 wrote: Can have an option to make "Output Feature Service Name" not visible. This was an option in WAB. This is very confusing for public users to tell the not to populate the text box. YES! I need this. Having to explain to my users to NOT enter a value is not good.
... View more
04-18-2025
04:00 PM
|
0
|
2
|
559
|
|
POST
|
the CORRECT SOLUTION: 1.) Create an attribute expression for latitude: var lat; var originShift = 2.0 * PI * 6378137.0 / 2.0; lat = number(Geometry($feature).y / originShift) * 180.0; lat = 180.0 / PI * (2.0 * Atan( Exp( lat * PI / 180.0)) - PI / 2.0); return lat; 2.) Create an attribute expression for longitude: var lon; var originShift = 2.0 * PI * 6378137.0 / 2.0; lon = number(Geometry($feature).x / originShift) * 180.0; return lon; I got this working in FieldMaps. THANK YOU!
... View more
03-18-2025
07:43 AM
|
0
|
0
|
427
|
|
IDEA
|
I would very much appreciate this functionality in Fieldmaps. Thank you.
... View more
03-13-2025
12:32 PM
|
0
|
0
|
467
|
|
POST
|
We have a need for this as well. I would use Survey123 but apparently, Survey123 doesn't like versioned data giving me an error regarding the service needs supportapplyeditswithglobalids to be true when I try to publish the form.
... View more
03-13-2025
12:12 PM
|
0
|
0
|
642
|
|
IDEA
|
I agree with this Idea. I'm researching this functionality now and came across this idea. We are using Enterprise 11.3 and having the sidebar automatically show when getting a hit on the near me widget would be very welcome. This is especially true for smaller screens like tablet and mobile.
... View more
12-16-2024
10:23 AM
|
0
|
0
|
825
|
|
POST
|
I solved this by adding a link button that links to the same Experience application. Basically a webpage refresh button.
... View more
12-12-2024
10:33 AM
|
1
|
0
|
438
|
|
POST
|
UPDATE: I've actually had decent luck with this tool using ArcGIS PRO 3.3.1 with Enterprise 11.3.0 so long as I had the field mapping configured properly and the destination layer selected in the table of contents.
... View more
12-12-2024
09:15 AM
|
0
|
0
|
604
|
|
POST
|
I realize this is a pretty old post (2014!) but I found my way here for this issue and others probably will as well. In ArcGIS Pro 3.3.1 there is a setting in the Symbol tab of Symbology Properties where you can set the Angle alignment to be 'display' or 'map'. Set it to display on rotated map layouts.
... View more
09-23-2024
07:27 AM
|
0
|
0
|
520
|
|
POST
|
Thanks! Super helpful. Agreed. Going forward, we will be upgrading our PRO and Enterprise together. I'll be forwarding that link to my IT people.
... View more
08-29-2024
09:18 AM
|
1
|
0
|
2388
|
|
POST
|
If I read this correctly (and from some personal experience), it is possible to upgrade, but DO NOT implement any new GDB functionality until your SQL Server is upgraded to at least version 17 when using PRO 3.3. We just recently upgraded to 11.1 and then 11.3 but our SQL Server is at 16. I did notice that if I added a date field (while using PRO 3.3) using the new 'date only' field type it threw an incompatible version error when I tried publishing a service. I had to delete the field. This happened at 11.1/PRO3.3. Had I known about this we probably would have held off on our upgrade until after the SQL server upgrade but here we are. We are now planning the SQL upgrade sooner rather than later but that will impact several other systems here. Which brings me to a complaint. We probably should have held off on upgrading ArcGIS PRO but you get that upgrade nag every time you launch and there's no link there for information as to what will break once you upgrade PRO. I'm learning now how integrated Enterprise and PRO are. They really go hand in hand. We will be much more careful going forward in the future with upgrading ArcGIS PRO in conjunction with Enterprise.
... View more
08-29-2024
08:36 AM
|
4
|
3
|
2395
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 2 weeks ago | |
| 1 | 12-12-2024 10:33 AM | |
| 4 | 08-29-2024 08:36 AM | |
| 1 | 08-29-2024 09:18 AM | |
| 6 | 05-20-2024 11:55 AM |
| Online Status |
Offline
|
| Date Last Visited |
Friday
|