Select to view content in your preferred language

Tree management Solution- Issues configuring

135
7
Tuesday
AlisonAbercrombie
Emerging Contributor

I am trying to configure the tree management solution for use by my organisation. I have updated some of the fields on the Trees layer including fields in the Inspection and Maintenance tables. These changes are not reflected in the hosted feature layer views 'Recent inspections' and 'inspections history'. Do I need to recreate these layers? If so how do I do this as I have tried to do this in ArcGIS online and there is no option to create your own filter expression? I can only select specific dates not the most recent date?

Also I have tried to update the species roster to UK species. The instructions on the configuration page simply state 'follow the update wizard'. However the wizard asks you to select the unique identifier fields and the options given in the drop down menus do not work? I have tried adding the data rather than updating but now cannot add any tree data as the forms do not work?

0 Kudos
7 Replies
JonM32
by
Frequent Contributor

@AlisonAbercrombie  Alison, to update the view layers you'll need to go the each view layer's item page, go to settings, then down the page you'll see 'Update View' for the layer. Go through that walkthrough and you can then pick the newly added fields you created in the source layer, and make them visible for the view layers.

I haven't used the tree solution but a different solution with view layers. I did the same thing with adding custom fields and needed to do the above workflow.

Hope this helps!2025-06-10 10_31_05.png

Jon
0 Kudos
AlisonAbercrombie
Emerging Contributor

This would be a much easier solution but I cannot find Update View as an option in settings for the layers?

0 Kudos
JonM32
by
Frequent Contributor

@AlisonAbercrombie There should be a source feature layer where all the views were made from. In the screenshot, the source would be the Feature layer (hosted) and then below are 2 view layers created from it. I'm assuming the tree layer is the same and if you searched for it in the Contents of AGOL, it'll likely have a Feature layer (hosted) version which is the layer you can go to settings for and find that update view button.

2025.png

Jon
0 Kudos
AlisonAbercrombie
Emerging Contributor

I think that this might not work for a couple of reasons. Where you have shown the update view button I have the following text: 

* Setting must be configured on the hosted feature layer that this feature layer view was created from.
 
Also in some other advice I found on this is states:
  • "feature layers that participate in view layers with joins cannot have their schema altered and are always read-only and cannot be used offline."

     

    I think that because source layer has multiple table joins I can update the view layer?

     

0 Kudos
JonM32
by
Frequent Contributor

That might be why then - the joins. 

Jon
0 Kudos
MikeDagle
Esri Contributor

Hi @AlisonAbercrombie,

Because Trees_currentinspection and Trees_inspections are hosted joined views, they do need to be recreated to expose additional fields. 

To do that, you can follow these steps:

  1. From the item details page of the Trees_currentinspection view, copy the service URL into a text editor. This will ensure you have the unique name of the view. It may simply be Trees_currentinspection, but if the Solution has been deployed multiple times in the same organization, it may have a guide suffix like: Trees_currentinspection_ae0f74dea4a44bf992bf0b00b97887ef. Repeat for Trees_inspections.MikeDagle_0-1749582281696.png
  2. From the Settings tab of their item details pages, delete Trees_currentinpection and Trees_inspections.
  3. If using the Recycle bin, permanently delete each view from the Recycle bin.
  4. Navigate to the Trees feature layer's item details page.
  5. Click the Create View Layer button, then select Joined view layer.
    1. To create Trees_currentinspection, select Trees for the Target layer, then click Next.
    2. Select the Inspections table, then click Next.
    3. The attribute join section should already correctly populate Global ID and Tree Global ID for the Target and Join fields. The Join operation is One to one, keeping the first matching record.
    4. In the Sort by, select the Inspection date field, then Descending for the Sort order.
    5. The Join type is Left join.
    6. Click Next.
    7. In the Title, past the unique name copied earlier (ex, Trees_currentinspection_ae0f74dea4a44bf992bf0b00b97887ef or Trees_currentinspection).
    8. Click Create. 

       

    9. To recreate the Trees_inspections layer, repeat steps 1 & 2.
    10. The Inspections Table is the Target layer.
    11. Trees is the "layer or table with the attributes that will be added to the target layer."
    12. The attribute join section should already correctly populate Tree Global ID and Global ID for the Target and Join fields. The Join operation is One to one, keeping the first matching record.
    13. Leave the default Sort by settings.
    14. The Join type is Inner join.
    15. Click Next.
    16. In the Title, past the unique name copied earlier (ex, Trees_inspections_ae0f74dea4a44bf992bf0b00b97887ef or Trees_inspections).
    17. Click Create.

Note that while the join views are deleted, apps like the Trees page on the Tree Management Center will have broken data sources.

I hope that helps!

Mike

 

MikeDagle
Esri Contributor

@AlisonAbercrombie Regarding the species roster documentation, sorry that hasn't been helpful. After updating the species roster csv and clicking Update Data from the Trees feature layer's item details page, click Add features. Select the Species Roster table, then click Next. Drag your csv into the window. The window should update with the field mapped correctly. Click Add and complete. 

Once you've done that, you're ready to move onto the next section on the configure documentation: Update domain and contingent values, which uses a Notebook to update domain and contingent values with those you've uploaded into the Species Roster table from your updated csv. 

We'll make a note to improve that section of the documentation at our next release. 

 

Cheers,

Mike