Latest Contributions by AllenDailey1

I am currently having this same problem.  My feature layers with this problem cover a large county but don't have a particularly large amount of features. I found that switching the map service to a feature service (or turning on "feature access" in the service's capabilities in ArcGIS Server Manager) solved the problem. However, you should not have to make everything a feature service in order for it to simply show up in the map!! I am using a state plane projection, so the posted solution makes me wonder if changing the projection would help... but that would be an extremely onerous undertaking, since I have a number of layers and again, this is not something one should have to do in order for the layers to simply show up!! ... View more

Thank you so much for your reply.  That all makes sense and is helpful. ... View more

Thank you.  No, there haven't been any schema changes.   I did use those tools to create and rebuild my locator. ... View more

Thanks for your reply.  Well, since we have to stay on Server 11.3 for the foreseeable future, we don't want to use Pro 3.4 yet, since 3.3. is the one that's officially compatible with Server 11.3.  But I can keep that idea in mind in case we want to at least test it out, like you said, just in case it provides any interesting information. ... View more

I kept digging into this and discovered that the warning was accurate - there really were unique ID fields mapped to all of the "join" role fields, for all of our address locators.  Yet no one had done it.  We do not even use alternate name tables for our address locators, which is what those fields are for.  My guess is that this happened automatically in the software somewhere between Pro 2.7/2.8 and 3.0, when Pro gained the capability to have locators with alternate name tables joined to them (we have had the same address locators since around Pro 2.8 or so).  And then the fields caused this warning to occur in 3.3.   Anyway, it looks like we will have to re-create all of our locators anew with Pro 3.3, because it is not possible to edit out the fields mapped to those join ID role fields, even though the documentation says the configurations are editable. If anyone else is experiencing this situation, I'd be very interested to hear about it.  I'm curious if we are the only ones or not. ... View more

Hello @urquidid , Thanks for your comment.  No, I haven't found a solution, although I haven't dug into it in a while.  Thank you for the link - I will read up on it and see if it's something we'd want to use. Thanks! Allen ... View more

Dear Esri, Has this been changed in the November 2024 ArcGIS Online update? I'm seeing behavior that makes me think you can now zoom to a feature even when using a map image layer, rather than a feature layer.  Can I trust my eyes?  ha I read all the documentation (at least all that I could find) about the update but didn't see anything about this. ... View more

I ran into this, with the same tutorial, also.  I hope Esri adds a way to resize the chart's legend, like a way to specify the legend height as well as the width, or a drag bar to resize the legend.  I'd be sad if I ran into this issue while creating a real app. ... View more

I have been having this problem, and I found this bug documentation from Esri: https://support.esri.com/en-us/bug/create-locator-returns-the-error-message-error-002777-t-bug-000153036 My path does have periods in it, in the server name, which includes "name.dmz".  So I guess that's the problem.  The bug was found in Pro 3.0.2 and fixed in 3.1.  I am using 3.0.3.  Time to upgrade! ... View more

Hi there, I'm sorry you're having this problem, and sorry to say I have no idea why this would be happening!  Perhaps Esri Support could help troubleshoot it with you?  Good luck! Allen ... View more

Hi there, It would help to see your code in the code-style font/format.  You can do that by clicking the button to expand the toolbar (when you are writing a reply here), then click the </> icon to insert code. I see that you are using the variable "thisFD" for arcpy.ListFeatureClasses().  For me, this variable name could cause a little confusion and obscure a possible reason for your error.  I would expect "thisFD" to represent the feature dataset name or object, so I would not expect it to end up as None, because how would you have a feature dataset name for a nonexistent feature dataset?  But since the variable is representing the list of feature classes within the dataset, you could have a feature dataset with nothing in it.  So the variable could represent None (no feature classes).  That's where I find it could cause confusion.  Personally, I find it helpful to use variable names that very literally indicate what they represent.  I think if the variable name was something like "fc_list", it would very clearly indicate what it represents, and it would indicate that it could be empty/None, because a list can be empty.  I agree with what the previous person said, to add handling to deal with an empty list. ... View more

Hi, Have you made sure that your connection file is pointing to the version?   ... View more