Latest Contributions by jcarlson

‎08-31-2022

Because the right-click Move pane is different from the Modify Features pane, it can be configured separately. You can click the pin icon to set that pane to auto-hide. At the very least, this treats the move panel as an overlay the next time you activate it, which will not alter your map extent. I don't believe you can prevent it from appearing, however. Also, if you're interested in avoiding wasted time, consider assigning Move to a keyboard shortcut like Alt + M.

‎08-31-2022

I would love to know the answer to this one! @JamalNUMAN you might even submit an idea requesting that users be able to define that order somehow. I'd vote for it!

‎08-31-2022

I believe that "max lines" setting is how many times the stack settings will insert line breaks. Do you happen to have a manual line break in your string anywhere? If you need to split the label at a multi-character string, I'd insert the break into the label string itself on the Label Expression, not in the stacking sections. var l = $feature.label_field return replace(l, 'to', 'to\n') // or just '\n' to make "to" disappear

‎08-31-2022

Exporting the workspace XML should give you everything you need. There are lots of third-party tools that can ingest such an XML to work with it in a more friendly setting if you don't have a handy way of parsing it yourself. Is a spreadsheet a good place to document your data model? I like a nice ERD myself.

‎08-31-2022

@ThijsBriggeman_TensingHold down the T key to get a "snapping schematic" view that will symbolize all snappable elements.

‎08-31-2022

The Split tool in the Modify Features pane does exactly this if you click directly on the vertex. It helps to have vertex snapping turned on, but you can split the line with a single click that is as precise as the vertex location.

‎08-31-2022

Using the zip file method is great for end users, as it enables you to deploy your app to a simple URL that updates when you want it to. We have a number of Experiences in our Portal, but our users prefer to have something like maps.co.kendall.il.us/mapviewer rather than a long itemID string. I would also like to add that the zip deployment is how you would share something built in the Developer Edition. If you haven't looked into, you really ought to, as the Developer Edition has access to the latest and greatest widgets you might see in AGOL's EB, and you don't have to wait for a Portal upgrade to use the newest tools.

‎08-31-2022

Building on @MikeMillerGIS 's excellent Schema method to subset your fields for those with "D_" in the name, include something like this in the main for loop: // other stuff above... var x = field_dict['name'] if (Left(x, 2) == 'D_'){ Push(fields,x) Push(values, $feature[x]) } } return min(values)

‎08-25-2022

The version of EB that shipped with Enterprise 10.8.1 will be whatever was available at that time, whereas AGOL has the latest version of it. There's no way to manually upgrade EB without also upgrading your portal, but if you need all the latest and greatest tools, I would recommend getting started with the Developer Edition. It still lags behind AGOL, but usually only by a month or two.

‎08-24-2022

I forgot to ask: is this on Portal, or AGOL? On Portal, you can use the Server Admin tool. Otherwise, you'll have to use something like the Python API. # connect to portal from arcgis import GIS gis = GIS('your portal url', 'user') # get featurelayer fl = gis.content.get('itemid of your service').layers[0] # pull out layer's json for your fields json = fl.properties['fields'] # you'll need your field's index here. # if you don't know it, you can get a list of field names and their respective indices first # print({x['name']:json.index(x) for (x) in json} # let's just pretend yours is at index 5 # append new code / value to domain json[5]['domain']['codedValues'].append({'code':'newcode', 'name':'newname'}) # apply updated json to service fs.manager.update_definition({'fields':json})

‎08-24-2022

Maybe try appending "/portal" to the URL?

‎08-24-2022

Editing domains can be tricky. Are you trying to apply this to the main layer, or a view that was created? For some of my hosted layers, I've only been able to edit the domain by editing the JSON directly, which can be a bit more advanced.

‎08-24-2022

Locks are locks, indeed! Time for some late night db admin!

‎08-24-2022

If your data "lives" somewhere that can't take advantage of attribute rules, it is also possible to write a really simple python script to handle this calculation and have it run at regular intervals.

‎08-24-2022

Where are your "label" values coming from? Do you have an actual domain on the field, or are these just manually configured aliases? Domains are a good idea for coded values for lots of other reasons, but easy labeling is the relevant thing here. When labeling a field with a domain, Pro automatically inserts the description, rather than the code. I'm sure ArcMap did the same, but I haven't used ArcMap in many years, and I don't recall. Suppose you have manually configured aliases instead of a domain, it would be nice to be able to translate your symbology directly over to labels without much fuss. There is a method of converting symbology classes to label classes, of course: Which is nice for certain situations, but then each label class has to be manually configured, which might be more work than just writing a decent label expression in Arcade. If you used a Where or a Decode, you could actually have the same expression being used for both symbology and labelling, and you could just copy and paste the expression in each. var adhoc_domain = { 'inst': 'Institutional', 'hdr': 'High Density Residential', 'mdr': 'Medium Density Residential' // and so on } return adhoc_domain[$feature['FLU_1']] In general though, if there's a value or alias that's going to be useful in more than one spot, it ought to be in the data either as a field or a domain. Relying on ad-hoc definitions and typing your labels in seems like it would take up more of your time. Re: your side note. User experience and feedback is critical to actually making the software better. In my experience, the development teams have been incredibly responsive to my feedback, even implementing some of my suggestions within a version or two. But in order for your feedback to mean anything, you've got to put it in the right place. Check out the Ideas boards on here, and make your feedback count! As I'm sure you're aware, you're far from the only user who is not finding the ArcMap -> ArcGIS Pro transition a bit rough. While development tends to focus on the leading edge of shiny new things, making sure that a big chunk of their user base doesn't get "eft behind is important, too, so the particular feedback you can provide as a longtime ArcMap user is really valuable!

Online Status	Offline
Date Last Visited	Tuesday

My Ideas

Latest Contributions by jcarlson

Re: ArcGIS Pro 'Move Tool' pane - stop pane from opening after right click to Move

Re: ArcGIS Pro 3.0.1: Based on what the sequence of layers are ordered in the content pane with “list by data source” mode?

Re: Label stacking separators - can we use a word?

Re: Copy and Paste to Excel

Re: Split on single vertex of polyline

Re: Split on single vertex of polyline

Re: Deploying a webapp

Re: Arcade to return field names that contain a string

Re: EB on Enterprise Versus EB on Agol

Re: Cannot add/delete field or edit domains

Re: Arcade Dashboard (data expression) - Entreprise 11.0

Re: Cannot add/delete field or edit domains

Re: How to Label based on "Label" value in Symbology Window

Re: Vary the feature symbology of a layer by the number of records linked to it

Re: How to Label based on "Label" value in Symbology Window

Re: Flow that triggers email when hosted feature l...

Re: Formatting "No Data" In Dashboard Indicator us...

Re: Interactive Chart From Data Expression

Re: Arcade in Dashboards, from 0 to 'null'

Re: Interactive Chart From Data Expression

GIS Jobs

Experience Builder Custom Widgets