Latest Contributions by DanielWickens

Matt,  That error appears when the hosted feature layer has been added to the map in ArcGIS Pro. Can you remove it from the map, and try adding the feature layer from the Catalog > Portal when setting it as the target?  ... View more

Hi @DerekBernard, I'm happy to take a look and help out. Would it be possible to send me either a subset or full dataset? I'll see if I can reproduce the issue on my end.  DWickens@esri.com ... View more

@Allie - sorry for the delay, i was out of the office for a few weeks and just catching up on this. If you're still experiencing this issue with Field Maps on the Samsung devices, would you be able to try and reproduce the issue and check the logs for any errors?  https://support.esri.com/en-us/knowledge-base/how-to-export-logs-from-the-arcgis-field-maps-mobile-ap-000026882   ... View more

@Allie - can you provide more details about the date fields? How are they formatted, designed, etc.? ... View more

@Allie - You need to configure the attributes in your Outstanding Issues web map. Open the web map in Map Viewer Classic, then select the feature layer and click "Configure Pop-up". Then click "Configure Attributes". Check the fields you want to display and edit. Select a field to change its alias, order it, and format it. The fields you set to Display are shown as columns in the Manager app. The fields you set to Edit are editable when you select a record in the Manager app. Here's a screenshot from the Burials web map for reference: ... View more

Hi @Henry  I am not aware of this behavior in the Cemetery Data Management pro project. When running the data loading tasks, make sure the Target Dataset is set to the boundary layer that corresponds to the input boundary data you're loading (screenshot below). That should clear up any issues with data being loaded into the wrong layers.  ... View more

@Dakota - sorry to hear the tasks were hard to follow. I am aware that sometimes the tasks automatically make a selection of no records (see screenshot below), and that can cause issues with running the join/calculate. Opening the attribute table and either switching the selection or choosing a manual selection should fix the issue.  If there are any other issues you're experiencing with the Pro tasks or overall solution, please let me know and I can log them as issues to fix in an update. Thank you! ... View more

Thank you @Laura, I will keep an eye on the progress of the bug. I have not come across that error in ArcGIS Pro before, and the help documentation about it is sparse. https://pro.arcgis.com/en/pro-app/latest/tool-reference/tool-errors-and-warnings/160001-170000/tool-errors-and-warnings-160226-160250-160233.htm I am curious to see what Esri Support uncovers. ... View more

@VeronicaSarver - Both ArcGIS Online and ArcGIS Enterprise have the same limitation of 200 unique values. One workaround is to apply the symbology in ArcGIS Pro (where there is no limitation) and publish as a web feature layer, as described in this Esri Support KB article. I would advise you to publish the new service as a test first before swapping out any services in the solution. I'm not sure of the implications of swapping the service without testing it.  For Roads and Highways, signs are treated as event features. You can add fields to the Signs feature layer that comes with the solution that would be recognized by R+H (RouteID, Measure, Event ID, FromDate, ToDate, LocError, and Offset), and feed the data into R+H using the Append Events geoprocessing tool.  Alternatively, you can use GP tools or Arcade to calc the fields that are recognized by R+H. ... View more

@Laura - Do you have screenshots of the errors you're experiencing? ... View more

@Laura - Have you loaded data into both the gravesite feature layer and owner/burial tables? The next step would be to join the gravesites with each table via Gravesite ID and calc the Global ID to establish a relationship.  ... View more

@Laura - you should be able to click on the highlighted burial/owner record in the table of the dashboard to unselect it.  ... View more

Hi @dean1001 - The Sign ID field is a manually entered field on the Signs feature layer. Most clients use this field to represent a unique alphanumeric ID for the Sign for search/filtering purposes. Sometimes they use the ID of the barcode for the sign in this field. Additionally, the Sign ID field is not to be confused with the Sign's globalid field, which is a system field that is automatically populated upon collection.  ... View more

@Laura - The only bug that's been submitted for Cemetery Management that I'm aware of is BUG-000158051: Getting a 999999 error when trying to use the Calculate Field geoprocessing tool in the Cemetery Data Management Project. I closed this BUG as a known-limit because I was not able to reproduce the issue. I was able to successfully run the tool using the data provided. The ArcGIS Pro help documentation has a topic for troubleshooting the 999999 error, if that's what you're running into.  Also happy to talk offline and I can take a look.  ... View more