Hello,
I'm testing out a process that would allow me to create co-incident points among two related point feature classes. I want to do this with editing templates because I think having a very clear UI would be best for my users. I know I might be able to configure something similar with an attribute rule, but I want the users to be able to kind of see what they're doing.
(edit to add: This is ArcPro 3.5 publishing to Enterprise 11.5)
In Pro, I have an editing template set up in the map that creates multiple features at once:
After publishing that to our web server and adding the layers to the map, I can see those two individual features among the editing templates, but it's clear from actually editing that only one feature is getting created at a time:
I've checked it out in the Field Maps Designer and there wasn't a clear way to accomplish this:
Does anyone have experience with this? I suspect at the moment that this is not possible but it would be really cool if I could get it to work.
Thanks!
@ZachBodenner - It might be worth taking a look at the workflow described in this blog post: https://www.esri.com/arcgis-blog/products/arcgis-pro/electric-gas/introducing-editing-templates-in-t...
This enables saving the template to the geodatabase, which could allow you to use it through the feature service.
Well thanks Travis, this looks like exactly what I need! I gotta upgrade the actual geodatabase a bit in order to do it, so I'll try it out in the next couple days and report back here.
Alright I have an update on this workflow. I created a new Preset Template using two point features from different feature classes and stored it in the geodatabase using the Store Templates command. The results are mixed:
Pro: immediately was recognized by the published web service
Cons: The two features in question are related feature classes and that seems to introduce some unexpected/ unhelpful behavior.
1) in the web environment, the template does not make it clear that the child feature would also be created. Here's a screenshot from Web Editor
We should expect, I would think, something like this, where both point features are represented?
Either way, I can't test out to see because I get an error immediately when trying to create the feature
2) The best practice of course would be that the template would also create that desired relationship. That was also unsuccessful, as the parent (Post) Global was mismatched with the child (Streetlight) GUID. Interestingly, I have an attribute rule running on these features where the child feature will receive the unique ID from the parent based on the GlobalID-to-GUID match. Using the template, that attribute rule actually ran successfully even though the features appear unrelated otherwise (again, all different GlobalIDs and GUIDs). That one's a bit of a stumper to me.
Finally, I can't seem to find any documentation on simply deleting the written templates from the database. The article and linked ESRI documentation points out how to overwrite templates with the same name and delete templates that don't have a matched name when attempting subsequent Store Template commands. What I want to do is simply delete this template that I just created without having to write others at the same time.