ModelBuilder alters names of output tables, breaking the model

[GiuseppeBaiamonte]

In ArcGIS Pro 3.3.1 ModelBuilder, the first time a model is run it operates correctly.

After the first run, in several tools (but not all) the names of the output tables are altered (_View is appended at the end).

For example, this Export Table uses an AGOL layer as source and outputs the table to a local file geodatabase (path present but not shown):

After the first run, with no user interaction, output is altered as following (path is lost):

Running the model in this altered state results in Error 000271 (cannot open the input datasets):

To have a functional model again, it is necessary to edit all the output table names that have been altered, removing the "_View".

Export Table and Table Select both exhibit this unwanted behaviour.

We have reproduced the issue on several different PCs and with at least two versions of ArcGIS Pro (3.1 and 3.3.1).

[DuncanHornby]

Over the years I found various ArcPro tools to have unwanted behaviour when employed within a model builder environment, especially field mapping, seems to be quite problematic.  I've always felt it has been a sort of chicken and egg situation in these cases.

By far the path of least resistance in your case is to run the tools in a python script environment. You have much more control over what goes into the parameters.

[David_McRitchie]

Hey Giuseppe, 

I had a recent case where at the latest version of ArcGIS Pro variables where having their name adjusted if they pointed to a dataset via filepath, rather than selecting them in a dropdown from the Contents pane. If you use file paths then I would recommend loading the data into the Pro project and picking these references in the model.

Hope that helps,

David

[GiuseppeBaiamonte]

Thanks for your suggestions.

@DuncanHornby, I agree Python has many advantages. It is a good solution for me, as I'm familiar with it, but for many users a model is more convenient.

@David_McRitchie, that's good to know. Unfortunately it does not solve our current issue.

As a general consideration, ModelBuilder is part of ArcGIS Pro and it is supposed to work reliably.

In my opinion, the fact that a model is altered after running (and without notice!) is an big issue and needs to be addressed.