There are no appropriate templates

23184
49
08-15-2019 08:06 AM
CraigHartel
Emerging Contributor

I am using Pro 2.3.2. I am trying to copy line geometry from one feature class into a new, empty feature class. I successfully select the geometry I wish to copy and when I attempt to copy it into the new feature class, I get the error message that "There are no appropriate templates".

In the Manage Templates pane, there is very definitely a template for the destination feature class. I've even tried deleting and re-creating the template but this does not work.

Always, always "There are no appropriate templates".

I have resorted to working back in 10.6 in order to not be so frustrated by something so simple that won't work. I've referenced thread after thread I've found online about this - I've followed YouTube videos on how to do this everything I can think of and still "There are no appropriate templates".

At this point I see no reason to continue using Pro nor even bothering to transition to fully working in the platform. 

49 Replies
WAC_GIScoordinator
Emerging Contributor

I'm in 3.5.3 and just ran into this issue. Not surprised to see the length of this thread.

"Weird. Happens for no reason". ESRI, I'm sorry, but around here we call that 'ESRI being ESRI'.

My solution:  I had to Append the features I wanted to copy into another Feature.

- Append tool - Target is where you want to copy to

                           - Input Datasets is where from (and it honors selections)

 

m3
by
Frequent Contributor

Who else is here in 2026?

BrandonGuo
Frequent Contributor

I still have this issue, not sure if it's the same bug as BUG-000113948. 

0 Kudos
JoeKonczyk
Emerging Contributor

One thing that has worked on and off is to make sure that you have the map tab selected and then make sure that you have the feature that you are pasting in selected.  I did also look into creating a template.  It is sketchy and needs to be address by esri. 

0 Kudos
BrandonGuo
Frequent Contributor

Thanks, I tried both but neither worked for me.

0 Kudos
JoeKonczyk
Emerging Contributor

Sorry to hear, We have ArcMap in shop as well, and I tend to go there when I need to.  One last thing that I would note.  I seem to have that issue in Pro when I select records in a table.  I have had success when I go to the map and reselect the geometry instead of selecting from the table.  a hail mary for you today.

0 Kudos
BrandonGuo
Frequent Contributor

I give up... Use QGIS instead, so much easier...

DianaBrown1
New Contributor

Just wanted to keep this thread alive and if anyone has found a cure.  It seems very random.  

0 Kudos
AndrewWillingale
Regular Contributor

I have a user who is migrating to ArcGIS Pro from ArcMap who has raised this issue with us. I have been able to recreate it on ArcGIS Pro 3.6.2. I have created two file geodatabases with a feature class in each. One feature class in one project and one in another. When trying to copy a feature from a layer in one project to a different layer in another project I get this error.

@Scott_Harris Are you able to advise or get someone else from ESRI involved please? You commented on this discussion over 6 years ago but we've not heard anything from ESRI since. Thanks.

Scott_Harris
Esri Regular Contributor

Hi @AndrewWillingale My original responses were in regards to bugs that were fixed in version 2.x and involved copy/pasting in the same project and same map.

My advice for you is to try your workflow in the same map. To do this, you can copy the layer from project B into the contents of project A - and then try copy/pasting features from/to the layers in the project A. It should result in the outcome you desire: specific features from a feature class in GDB B copied into a feature class in GDB A. This method should be more reliable, and gives you more control, since there is a field mapping control that exists for layers in the same map: https://pro.arcgis.com/en/pro-app/latest/help/editing/configure-field-mapping.htm

If there is a bug with copy/pasting between projects, it's best to create a case with Esri Technical Support: https://support.esri.com/en-us/contact

0 Kudos