We've applied the patch to ArcMap 10.3.1.
I built a brand new model from scratch using the same tools and exported it as a runtime geoprocessing package. Unfortunately, the patch did not work. I am still receiving the same exception.
I have opened a case with Esri support about this. Hopefully they can help resolve this quickly as my time is running short.
In the meantime, I'll tell you what I'm doing (I've explained this in other posts, but I'll repeat it here). And maybe you can give me some insight into a better way:
Our old applications use ArcObjects. We want to move to .NET with x64 support, so we're using the runtime SDK to build a new mapping component.
The previous component would create an MXD document, and populate it with layers. Some of these layers were Route Event Layers that used SDE connections to the client SQL servers (these were updated on the fly when the connection info changed) to dynamically retrieve data and route it along a central line using routing measurements supplied by our clients.
This allows our clients a great deal of flexibility when manipulating their data.
In our upgrade, I've managed to generate the centerline (plus some ancillary layers that don't apply here) by using a ServiceFeatureTable (and now direct JSON calls because the ServiceFeatureTable refuses to accept custom Measure values). This part works very well, and it generates fast.
Now it is time to add these dynamic layers (facilities layers). We have the facility data, which only contains a start and end point. Using this we need to overlay the facility feature on top of the central line on the map. Unfortunately, I cannot use SDE connections to the tables (or at least, it's never worked for me) using a map package and the LocalFeatureService. So, I built a GeoProcessing package to do the job. Here's what I do:
- Get feature data from the central line that fits within our view extent. I managed to get the central line data back with M values by using a QueryTask (hopefully it's correct, I can't tell at this point).
- Load data from the SQL table that matches the feature data by a specific ID value.
- Convert that data to a Feature Set
- Execute the geoprocessing package with the 2 feature sets as parameters.
- The model will take the central line feature set parameter data, and convert it to an in memory feature layer via the Make Feature Layer tool.
- The model will take the event feature set parameter data, and convert it to a Table View using the make Table View tool.
- The outputs from these two tools are then passed to the Make Route Event Layer tool.
- The output from Make Route Event Layer tool is read by my application and an empty pre-existing layer will be populated with the routed features from the make Route Event Layer tool.
So, as you can see, it's a pretty complex workflow here. Any suggestions on how I could simplify this (locally, we're not ready to jump on ArcServer yet as our clients may freak out over that)? Since ArcMap refuses to dump out a geo processing model that works for me, I'm hoping there's a potential solution here that I've overlooked or something.
