topic Modelbuilder as a tool is not the same as running the same model in modelbuilder? in Geoprocessing Questions

Modelbuilder as a tool is not the same as running the same model in modelbuilder?

JamesNunn — Thu, 19 Jan 2012 09:36:02 GMT

Hi

I am having a very frustrating problem where I have created a model which is basically a spatial join with some layer creation. When the model is run inside modelbuilder, the result is as intended. If it is run as a tool (with parameters filled in correctly), the outputs are deleted/not created at all. Is there an intentional difference or is this a known bug? I am running ArcView 10 SP3.

Thanks

Re: Modelbuilder as a tool is not the same as running the same model in modelbuilder?

MichaelMiller2 — Thu, 19 Jan 2012 16:21:44 GMT

I opened a incident this morning asking this same question. I'll post the responce once I hear back from support.

Michael Miller

Re: Modelbuilder as a tool is not the same as running the same model in modelbuilder?

DaleHoneycutt — Thu, 19 Jan 2012 21:16:08 GMT

Is the output variable a model parameter? It sounds like your model creates a layer. This output layer has to be a model parameter in order for it to be automatically added to ArcMap display when the model is run as a tool. See these help topics for more info:

A quick tour of creating tools with ModelBuilder

Creating model parameters

Re: Modelbuilder as a tool is not the same as running the same model in modelbuilder?

JamesNunn — Tue, 31 Jan 2012 07:05:02 GMT

Thanks for the reply, it was a schoolboy error in not unticking the intermediate data option for some data.

I still have a similar problem which hasn't responded to unticking the intermediate button. I have a large tool which takes the point, line and polygon layer (one of each) in a FGDB, selects features by feature codes (specifically defined in each 'select by attributes' tool) and sends each selection into a defined feature class. (The tool basically takes map data from a survey database and appends them to a base map database).

If I run it inside model builder it works fine on all the feature classes, but running it as a tool causes the lines and points to be processed but not the polygons. If I set the outputs of the polygon branch as a precondition to the rest of the tool, it gets only as far as parsing the input database name and then stops with no error message, the tool thinks it has completed. Is there an intended difference between running models in modelbuilder and as tools?

Thanks for your help