My issue is similar but different. I have a number of processes that are related but independent of each other, I would like to force them to go in a particular order as its easier to diagnose issues when looking at logs after the model fails. For instance, I have found that my services tend to lock my SDE after a short period and I would like to run the longest process first in order to make sure it gets done and doesn't have to be rerun if locks develop during the model run.
The one at the bottom should run first since it is so long. I know rearranging the graphic wont help a bit. The top four processes are much quicker and should be run after the long one.
Make the element Parcels_1 with URL Populated a precondition to all four "fast" tools. (Use the magic wand tool to connect the output to each tool and select "Precondition."
I had it all set up the way I wanted and it would run without errors. Trouble was, the feature classes were never created at the end. I've basically abandoned my efforts to make this easier because the work to get it that way is harder than just continuing to do things the same way.
Hey Joel,
You can use 'Preconditions' to control Order of Operation: A quick tour of using preconditions—Help | ArcGIS for Desktop
In the above example, process 2 cannot start until the Feature Dataset has been created by process 1.
I've used this to control dependant field calculations, where the value of one calculated field is used to calc another field.
This is very simple to setup and does not require you to alter the workflow or logic of your existing process.