nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ArcGIS Pro Modelbuilder keeps putting single quotation marks/apostrophes around output feature class name

christinebrooks

ArcGIS Pro Modelbuilder keeps putting single quotation marks/apostrophes around output feature class name/directory.
This provides the error "ERROR 000271: Cannot open the input datasets" when i run the modelbuilder.
When i remove the apostrophes, it recognises the dataset again and works, but it means I have to do this every single time for all geoprocessing actions.
Also it might be worth noting that I converted a modelbuilder from ArcMap into Pro? Could this have something to do with it?
Can someone please tell me how to make sure it doesn't put the output dataset directory in single quotation marks like this? Thank you!

error is fixed when i remove the single quotation marks/apostrophes:

Find more posts tagged with

Accepted answers

Chris Underwood

Hello @christinebrooks , is ArcGIS Pro feeling the need to add Quotes/Apostrophes around your Output Feature Class name because your path has a space it in, ie \STATS<space>Pro\ ? When there is no space in the path it seems to behave as expected.

All comments

sarahc_WellingtonCounty

Hey Justin,

Any chance you figured out how to resolve the issue with model builder not being able to open input datasets (from a feature service)? I'm running into this as well and can't figure out why its happening or how to fix it. Its happening sporadically, not every time which makes it even more frustrating.

Thanks!

JustinH

Model Builder seems to do something similar with me when it will add an "_Layer" to the end of the output file path and I will get the same Warning "The Value is Not a Feature Class".

I am also running into the issue where the export Features will not "open the input datasets" but it is not consistent and totally random. Basically I am just trying to export a Feature Service so I can manipulate it and push it to a different feature service.

christinebrooks

@ChrisUnderwood @DuncanHornby thank you both so much!! im new to coding/modelbuilder so this is a very big lesson i will never forget!! 🙂

Hornbydd

Having spaces and characters that are not letters or number is bad practise for folder names and invalid for geodatabase feature classes. You are digging yourself into a big hole, especially if you need to automate processing with model builder and or python. Don't do it!

Chris Underwood

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.