Latest Contributions by ChelseaRozek

Having this issue in 3.5.3. Trying to use an address locator published to our ArcGIS Server (locators copied to it). Tried to use the file of the locator instead, and it's still spinning the "loading" blue dots and Next is greyed out. I'm only geocoding 3k rows and even cutting it down to 50 doesn't work. It's from a file geodatabase table so it's not a compatibility issue. I see no warnings in Diagnostic Monitor nor ArcGIS Server. My geocoding service works fine in other applications. Also doesn't work with ESRI's World Geocoding Service. Another user I was helping had the same issue, but when we docked her laptop she was finally able to geocode. Not sure if it's coincidence or not... My work computer is a desktop so it's not on wifi. It works fine on my work laptop and my personal desktop, both also on 3.5.3. Update: still an issue in 3.5.4. Put in a ticket, but no solution for Geocode Table. Only workaround is to use the Geocode Addresses gp tool. ... View more

Hi @ChrisWesson, you can view it just south of this parcel in our public app. I can open a support case to send a vtpk over, but is there a way we can escalate it to your team from the get-go? Which product should we call it as it's across Pro/Enterprise/AGO? ... View more

In case this helps anyone else, I was able to achieve it using the CIM. Please note: accessing the CIM may have unintended effects and mess up your project, so be cautious and save backups. My project was very simple and this code worked for me. I had Unique Values symbology on my municipal boundaries layer. This code automatically changed the fill transparency to 50% (leaving the outline at 0%) for each of the 28 features without having to go into each one. aprx = arcpy.mp.ArcGISProject('current') mp = aprx.listMaps()[0] #I only had one map in my project, adjust as needed lyr = mp.listLayers()[0] #mine was the first layer, adjust as needed lyr_cim = lyr.getDefinition('V3') #use V2 if Pro 2.x for x in lyr_cim.renderer.groups[0].classes: munisym = x.symbol.symbol.symbolLayers[1].color.values munisym[-1] = 50 x.symbol.symbol.symbolLayers[1].color.values = munisym lyr.setDefinition(lyr_cim)   ... View more

I believe with the recent changes to Hub this is no longer relevant. I'm able to add users to groups without specifying emails that go out to them. ... View more

Really looking forward to seeing this implemented ... View more

Thanks for confirming that it works in this version. I scoured the documentation again and I'm doing everything right. I accidently closed the map in my project and when I reopened it (and thus a new Sharing as a Web Layer panel), it allows me to publish now. It's like it didn't recognize it when I added those error layers from the Analyze errors. Oh well, it's published now! Thanks ... View more

@RobertKrisher I've gotten to that step and it's handy that it can pop those error layers into the map for you, but when I Analyze again, those errors are still there and I can't publish. Any ideas? I only have a point layer and its 4 error layers in my map, coming from a connection as the data owner to the default version of the layers on our enterprise geodatabase. Pro 3.5.2. ... View more

@BenRomlein do you remember if and how you solved this? I'm getting the same error Update: It worked for me today after the sharing panel was closed and reopened ... View more

Would love to see filter by Source Layer and Error Number so I can buzz through fixing a bunch of similar issues at once ... View more

in case anyone is like me and working through a remote desktop, using the built-in onscreen keyboard utility allowed me to use Alt + Spacebar to move the off-screen dialog box instead of it just working on my physical computer ... View more

Thanks for sharing your code! Using that originalfeature vs. feature geometry is the only workaround I've found too, but it's unfortunate that the rule still seems to fire all the time. My bulk attribute updates take forever and it's a hassle to wait until after hours, turn off the service, disable all the rules, and then do it... I've put in a ticket with ESRI, I'll post back here if anything productive comes from it. ... View more

Were you able to figure this out? I think I'm having a similar issue. I only have SHAPE as the triggering field, but making an attribute change still triggers it so I can't manually edit an attribute. ... View more

With a multirole locator with parcelname mapped to PIN: yes the intersection zoomed to 1:24.8. So does an address that’s one off from mine (that doesn’t exist), which I hadn’t tried before in my testing. My exact address zoomed fine, but when I recreated the locator without the address points locator as that result seemed to be coming from that locator (so only parcels and road lines left), everything is zooming to 1:24.8. My goal for the parcel locators is to be able to search by the parcel PIN or by the PROP_STREET in the parcel layer in addition to geocoding against the roads. Thanks for the document link. I was under the wrong impression that I would need an address range to map to the house number(s) with the Parcel role. I’ve modified a copy of the parcel polygons and created a locator with a role for Parcels against it (Name mapped to PIN, House Number mapped to STREET_NUM, Street Name to STREETNAME, city, state, zip) + the normal roads role. This locator is zooming me to 1:12.31 which is bad. I then recreated the locator minus the roads (so only the better mapped parcels), zoomed to 1:554 which is a little better. Obviously couldn’t test intersection or “off by one” address since it's only against the parcel polygons. I swapped the test and left only the roads locator in. All 3 test addresses came up at 1:1,231 which is great. Yeah, I’ve played with the Result Order before. I’m still wondering what controls which zoom level a result appears at, especially since these last two tests with only one role showed results at different zoom levels. I would think other users would want to be able to control this too. ... View more

Polygon parcels. Apologies, to be clearer, the Parcel Name maps to PROP_STREET which has 123 Main St. We do not have separate fields for street number and street name. I have a separate locator that matches based on the Parcel PIN. Correct Local Extra High and Global Extra High: same issue  I noticed in these two, when I search for my address, there are 2 results, one at 1:1,276 (decent) and the other at 1:28 (bad). In the original, GLOBAL_HIGH, the two results are both decent at 1:2,834 and 1:1,276. Combining A (Street and Point Address roles) with B (only Parcels) into a composite locator: intersection is fine at 1:1,890, my address is okay at 1:850 I am using ArcGIS Pro 3.5.2 So my workaround for now is to separate the locator for the parcels' street address into its own. I really appreciate your help with troubleshooting this! ... View more