ArcGIS Pro 3.0.2: The “solve” tool in model builder produces results different from the “solve” button in the ribbon with same network dataset setting

[JamalNUMAN]

ArcGIS Pro 3.0.2: The “solve” tool in model builder produces results different from the “solve” button in the ribbon with same network dataset settings and configuration,

As per the screenshot below, the solve” tool in model builder produces results different from the “solve” button in the ribbon with same network dataset settings and configuration.

What could be the issue here?

[MelindaMorang]

Hello Jamal.

It's difficult to determine what's really happening from these screenshots.  It looks to me like the results might be the same but with different symbology and different draw order.  I suggest you check the attribute tables of the resulting Polygons layers and check whether they are the same.  You can use the Feature Compare tool to compare the attributes and geometry exactly.

[JamalNUMAN]

I tried all possible symbology ways to see if the result of the “solve” from model can be identical to the one obtained from the “run” from ribbon as the geometry option is set to be “overlap”, but failed.

The data is attached

[MelindaMorang]

Can you tell me what you're really trying to do?  What is the goal of your analysis? I don't really know how to answer this question, but maybe if you tell me what you're actually trying to do, I can advise on a good approach, and then this question will become irrelevant.

[JamalNUMAN]

All what I wanted to do is to calculate the population size within the cutoff ranges of 500, 800, and 1200 meters from the ATM machines using the model builder.

What I observed is that the result that respresents the cutoff ranges is different if the “solve” is applied in model builder than the one applied from the “run” in ribbon particularly if the geometry option is set to be “overlap”.

[MelindaMorang]

I looked at your model, and I noticed that you are creating the network dataset in the model.  This is a bit unusual, particularly using the Create Network Dataset tool, since (as you pointed out in one of your other questions), you can't adjust any of the network dataset properties.  Normally, you should manually create your network dataset with all the desired configurations.  Once it's created, you don't need to do it again.  You can just use it in the model (or set it up as a parameter so the user of the model can optionally select a different network dataset if desired).

Alternatively, if you need to create a different network dataset in the model itself (maybe for a different city or region?), you could use the Create Network Dataset From Template tool to ensure you're creating a network with all the desired configurations (which you should set up in advance when creating the template).

In summary, I don't think it makes sense to create the network from scratch and build it every time you run the model.  It's possible that this is causing the discrepancy with what you're doing in the map because you're testing with a different network dataset or something.

I don't really know how to help you, and I think at this point you might have better luck calling Esri Support or whichever distributor handles Support cases for your country.  A Support analyst can spend more time with you understanding your workflow and diagnosing and troubleshooting problems.

[JamalNUMAN]

We can live with this behavior as the result obtained from the “run” tool in the ribbon and the “solve” tool in the model can be identical if the “geometry at overlap” option is set to be “dissolve” as per the screenshot below.