Latest Contributions by ZacharyHart

Thanks for this Elisabeth! I'm curious about the disparity between AGO in Pro in the implementation of Arcade regarding dictionaries now. ... View more

Ok new clues. I'm going to mark your other response as the solution since it got us to where we need to be, but the rest looks like we have found a potential bug.  A colleague tested for me and the expression works just fine in AGO. For the heck of it, I saved a copy of that layer in AGO with the working label expression and brought it into Pro. Labeling failed to work. Checked the expression and same error about field not found. I tried to add Expects($feature, "Type") and that returns a new error of invalid JSON. So everything works fine in AGO but there's a problem with this solution in Pro. Thanks for everything!  ... View more

I noticed that and i'm still getting the same error about field not found. Perhaps this is an issue with the label expression builder? I'm trying to fetch attributes with that interface. (ArcGIS Pro 3.1.3) ... View more

I should have mentioned I tried that as well but when doing this I'm given an error of field not found. I know the format for Arcade attribute labels is $feature.fieldname  var stuff = { "0": "SCC", "101": "SEP", "4": "CLT", "23": "CGS", "8": "CTR", "7": "CTH", "14": "DSW", "9": "ECT", "5": "FTH", "21": "GPS", "10": "GSL", "3": "ITH", "22": "ITS", "13": "ISH", "20": "OSR", "17": "PTC", "26": "PCT", "24": "SAL", "18": "STC", "15": "SWR", "19": "STR", "6": "TFA", "12": "3SS", "11": "2SS", "100": "GPE", "25": "WHI", "102": "RET", "103": "TSI", "104": "POL" }; var keyField = "Type"; // Look up the value based on the key from the field var lookupKey = $feature[keyField]; var lookupResult = Dictionary(stuff)[lookupKey]; return lookUpResult; ... View more

Supposedly the Arcade Distinct function will be working in the 3.2 release...(several years after it was first shown in the documentation). You can read comments from others here. ... View more

like i said, 3.1.3 fixed this for me...3.2 isn't far off so I wouldn't be hanging on to 3.0 for too long... ... View more

I am happy to say that upgrading to the latest patch of 3.1.3 has resolved this issue for me! I hope this works for the rest of you! ... View more

I am happy to say that upgrading to the latest patch of 3.1.3 has resolved this issue for me! ... View more

@TomKukitz Do you have any documentation related to this? ... View more

I don't see how this is the solution when the issue is with HFL's and AGO.  ... View more

did you ever find a solution for this? ... View more

the documentation suggests it is available but when i search power automate for the connector I don't see it! https://doc.arcgis.com/en/microsoft-365/latest/power-automate/set-up-the-arcgis-enterprise-connector.htm   ... View more

Does anyone have any suggestions regarding this?  Does anyone utilize Feature Services as an input to GP Tools?? Here's what Chat GPT 4 had to offer: It sounds like you're facing an issue while trying to publish a geoprocessing tool to ArcGIS Server that uses a feature service as input. The problem arises because ArcGIS Server doesn't support registering a feature service with ArcGIS Datastore, which leads to a failure during the validation process. Here are a few steps you can consider to resolve this issue: 1. **Use a Geoprocessing Service**: Instead of trying to publish the geoprocessing tool with the feature service as input directly, you could create a separate geoprocessing service that takes the feature service as input and then use that geoprocessing service as a tool within the main tool you're trying to publish. 2. **Data Extract**: Depending on the nature of your geoprocessing task, you could use the feature service as a reference but extract the necessary data to a file geodatabase or other supported data source that can be used in the geoprocessing tool. This extracted data could then be included with your geoprocessing tool when you publish it. 3. **Temporary Feature Class**: If possible, you could create a temporary feature class within a supported geodatabase (like a file geodatabase) and populate it with the features from the feature service. This temporary feature class could be used as input for your geoprocessing tool. 4. **Data Replication**: If your workflow requires frequent updates to the feature service, you could consider setting up a data replication process where the feature service's data is periodically copied to a registered data source that is compatible with ArcGIS Server. 5. **Contact Esri Support**: If you're still facing issues, it might be a good idea to reach out to Esri's technical support. They can provide you with more specific guidance and troubleshoot your scenario to find the best solution. Remember that the specifics of your workflow and environment can influence the best approach to take. Choose the option that aligns most closely with your requirements and available resources. ... View more