topic Tree Management attribute table, Workforce, and public sharing questions in ArcGIS Solutions Questions

Tree Management attribute table, Workforce, and public sharing questions

JayHodny — Tue, 03 Sep 2024 15:49:43 GMT

Hello, we are considering deploying the Tree Management Solution to manage our tree inventory in 2025. The inventory will likely be generated by an external consultant. I would like to provide the attribute table for the primary feature class/service used in the solution to the consultant. Is there a way to download the attribute table schema without having to download the solution?

How will the solution evolve with Workforce being rolled into Field Maps? And is there an ETA on when Workforce will be replaced in the solution?

With the Enterprise version, will the public need credentials to access the public-facing solution components?

Many thanks, Jay

Re: Tree Management attribute table, Workforce, and public sharing questions

DanielWickens — Wed, 04 Sep 2024 01:08:49 GMT

Here is a link to a view of the Trees feature service with the details you're looking for:
Trees_public

Change the drop down to select the layer, click the fields button to view the details:

Field Details

Field Maps Tasks are tentatively planned to be released in February 2025. We will look to gradually update all Workforce Projects with Field Maps Tasks in ArcGIS Solutions (including Tree Management) in later releases in 2025. This schedule is subject to change.

The public will not need credentials to access the public-facing apps, as long as they are correctly shared through your ArcGIS Enterprise Portal (e.g., Everyone).

Hope this helps.

Re: Tree Management attribute table, Workforce, and public sharing questions

JayHodny — Wed, 04 Sep 2024 13:08:49 GMT

Perfect Daniel, thanks!

Re: Tree Management attribute table, Workforce, and public sharing questions

JayHodny — Wed, 04 Sep 2024 15:55:56 GMT

I was comparing the 'Trees' feature service with 'Trees_public' service after I deployed the solution. If I am not mistaken, the _public service does not have a field called "adoptedby." Just curious as to why.

Re: Tree Management attribute table, Workforce, and public sharing questions

DanielWickens — Wed, 04 Sep 2024 17:11:46 GMT

The 'adoptedby' field is used to store the username of the person adopting a tree in the Adopt-a-Tree solution. It's visible in the main 'Trees' feature service to view internally who has adopted which trees, but it's hidden in the 'Trees_public' view so as not to expose the username in public apps. If you wanted to make use of that field in the 'Trees_public' service, you would just need to update the feature layer view from the Settings tab. Keep in mind, this field is only relevant when using the Adopt-a-Tree solution. It's not leveraged in any components of the Tree Management solution.

Re: Tree Management attribute table, Workforce, and public sharing questions

JayHodny — Wed, 04 Sep 2024 17:17:48 GMT

Ah make sense Daniel, many thanks.

Re: Tree Management attribute table, Workforce, and public sharing questions

GISsolutionIZ — Fri, 03 Jul 2026 19:15:55 GMT

Hello,
I was just wandering whether the solution released with Workforce being rolled into Field Maps?

Re: Tree Management attribute table, Workforce, and public sharing questions

DanielWickens — Sun, 05 Jul 2026 02:09:09 GMT

@GISsolutionIZ - Yes, the Tree Management solution will be updated by the end of 2026. The Workforce component will be replaced with Field Maps Tasks, and will include enhanced capabilities to support recurring maintenance and inspection programs where Tasks are tied to specific assets.

Re: Tree Management attribute table, Workforce, and public sharing questions

GISsolutionIZ — Mon, 06 Jul 2026 11:40:15 GMT

Hello Daniel,

Thanks for your reply.

Our organization is aiming to implement the Tree Management solution this summer, so I've already deployed the solution and am currently configuring the essential components.

I'm looking for the most effective way to roll out the current solution for use in Field Maps. So far, I've created a task layer in Field Maps and included it in the Tree Field Maps web maps. But I am wandering how I can establish the relationship to the Inspection and Maintenance records tables where it can create a task in the task layer based on inspection and maintenance records.

Do you have a recommended approach when integrating current solution with field maps without breaking the existing solution or its relationships? I'd appreciate any best practices or guidance you can share.

Thank you!

Re: Tree Management attribute table, Workforce, and public sharing questions

DanielWickens — Wed, 15 Jul 2026 00:15:46 GMT

One approach you could take is to add GUID fields to the task layer and inspection/maintenance tables to establish a GlobalID - GUID relationship between the trees/planting areas, tasks, and inspection/maintenance table.

The task layer would have a GUID field to store the GlobalID of the tree or planting area. When creating a new task, you could use an Arcade expression in the form of the task layer to get the GlobalID of the tree or planting area that it intersects, and store the value in the added GUID field.

Then, the task layer can be configured with an integration action that opens either the inspection or maintenance table for the tree/planting area based on the task type using the addRelatedFeature URL parameter.

Optionally, you could add a GUID field to the related tables to store the GlobalID of the task, and pass the GlobalID of the task into that field as part of the integration action.

Then you can build join views based on the GlobalID and GUID fields to know which tasks are associated with an asset, and which inspection/maintenance records are associated with a task.

All of this and more will be implemented in the next version of Tree Management, but I understand if you can't wait until later this year. This will be a good starting point with adding Tasks to the current version.