Apply Utility Network Copy Workbook Error

[TanyaWright1]

Hello, 

I am trying to use the copy/apply utility network workbook to add the water service line asset types from the expanded model to the essentials model. I was able to add the other asset types I need using this method, but I am getting an error for the service lines. (error shown below). Any ideas how to fix this? Or do I need to manually add these asset types?

Error: 

The 'Subnetwork Controller' category requires a terminal configuration to be assigned  error

Thank you!

Tanya

[gis_KIWI4]

@TanyaWright1 - This is peculiar. The question suggests that you are trying to work with the WaterLine but the Error suggests something wrong the WaterDevice. Could there be something wrong in another sheet? 

[TanyaWright1]

I didn't make any changes to the other sheets, so that shouldn't be the case that I am aware of. 

[PatrickGCowan]

I believe this error is related to the previous asset types you applied, not the Service Lines you're currently working on. Prior to every apply process, the target asset package is validated. The tool doesn't copy terminal configurations; it only sets them. This means a device was copied with a terminal configuration that doesn't exist in the target AP. In the target, it was assigned the subnetwork controller category (which requires terminals), but the terminals weren't set because they don't exist in the target AP.

We'll discuss this internally to find a better way to handle this situation. Meanwhile, you can set the Terminals option to False when you apply the workbook to fix the error. This prevents the assignment of terminals and subsequently the subnetwork controller category assignment. To identify the offending asset type to change the setting on, check the B_NetworkCategory_Assignment table for OBJECTID 17 (as per your error message).

To correct this, start with a fresh target AP since the incorrect settings have already been applied. Alternatively, you can manually apply terminals to the problematic device via the AP tables.

[TanyaWright1]

I have experimented with a few things and have gotten some varying results. First I started over with a fresh asset package and a new workbook to copy asset types from the expanded to the essentials model. This new asset package copied everything over. However, then I realized I needed another device asset type and tried to add just that one to the new asset package. It then gave me the same error message as when I was trying to add just the service lines. So I tried a brand new asset package again with a workbook containing everything I want to copy over. This time it would not copy the service line asset types over saying that they already exist. Attached is the copy of the workbook if any one wants to see if they get the same error. 

[PatrickGCowan]

I can replicate the original error by running the workbook twice. The error appears on the second run because the asset type "Test Point" is missing a terminal assignment. In the expanded model, this asset type acts as a controller for the cathodic protection tier, thus it has the network category "Subnetwork Controller" set on it. However, subnetwork controllers require terminals. Since the terminal definition "Terminal Block" for this asset type does not exist in the essentials, it gets assigned the category but skips the terminal assignment as it can't find it.

On the first run, this does not cause an issue as it simply skips the assignment. However, at the start of each apply process, a validation of the target asset package is done. This is where it fails on the second run, indicating that for the Test Point asset type, a category of network controller was assigned, but no terminals were assigned.

To fix this, toggle the Terminals option to False for the Test Point asset type. That should fix the error.

[TanyaWright1]

HI Patrick, 

It still did not let me copy over the asset types for the various service lines. Any idea why? Did those copy over for you?

Thanks!

Tanya

[PatrickGCowan · Accepted solution]

That message is telling you that there is a conflict in the naming of the asset group between the source and target. They share the same asset group code, but have different names. This is probably due to the essentials using the name Service Line and the the expanded using the name Service. We will be updating the naming to be consistent between the models in a future release so this issue doesn't arise. You can change Service to Service Line in the ToAssetGroupName column and then it should work.

The other way you can make sure this doesn't happen in the future is to use the drop downs in the ToSource and ToAssetGroupName columns. The drop downs are derived from the target asset package, so they will always be correct. The ToAssetTypeName, ToAssetGroupCode, and ToAssetTypeCode columns do not have drop downs and need to be typed in (or copied from the source columns).