topic Re: Attribute Assistant: INTERSECTING_FEATURE doesn't work with split and there is a relationship using the field to copy. in Electric Questions

Attribute Assistant: INTERSECTING_FEATURE doesn't work with split and there is a relationship using the field to copy.

JeremiahMartin — Fri, 04 Jan 2019 16:18:33 GMT

Michael Miller attributeassistant‌

I have Attribute Assistant configured to copy a ServiceID (Foreign Key field) from one Intersecting Service Pipe to another Intersecting Service Pipe. This works correctly when placing a new Service Pipe feature; however, I get inconsistent results when splitting an existing Service Pipe feature. If the ServiceID field has a value that doesn't link to a record, it will work correctly and copy the ServiceID to the new Service Pipe feature that gets created by the split. However, if the ServiceID field has a value that does link to a record, the value is not copied.

In the AA code,

sourceFeature.get_Value(sourceField) returns null if there is a linked record, but returns the ServiceID value when I put in a ServiceID that doesn't match a record.

Is this a bug, or does anyone know a way to work around this?

Here is the exact configuration:

TABLENAME	FIELDNAME	VALUEMETHOD	VALUEINFO	ON_CREATE	ON_CHANGE	ON_CHANGEGEO	ON_MANUAL	RUN_WEIGHT	COMMENTS
P_Service	ServiceID	INTERSECTING_FEATURE	P_Service\|ServiceID	1	0	1	0	10

Re: Attribute Assistant: INTERSECTING_FEATURE doesn't work with split and there is a relationship using the field to copy.

MikeMillerGIS — Fri, 04 Jan 2019 17:05:24 GMT

There is an option to suspend the AA on split, can you check that in the loaded.aa.config file?

Re: Attribute Assistant: INTERSECTING_FEATURE doesn't work with split and there is a relationship using the field to copy.

JeremiahMartin — Fri, 04 Jan 2019 17:11:44 GMT

The key "OnCreateWhenSplit" has it's value set to "False". Should I change this to "True"?

Re: Attribute Assistant: INTERSECTING_FEATURE doesn't work with split and there is a relationship using the field to copy.

MikeMillerGIS — Fri, 04 Jan 2019 17:19:13 GMT

I was thinking of something else, but I do not see that option. Could you activate the log file and maybe that can help us narrow it down. How are you splitting the service line? Does not make sense that get_value is not getting the value when split, unless the new feature is not getting is ID carried over because of the 1:M relationship. If you split a main that has a valid ID, with the AA turned off, do the resulting 2 features have the same ID, hence violating the 1:M relationship?

Re: Attribute Assistant: INTERSECTING_FEATURE doesn't work with split and there is a relationship using the field to copy.

JeremiahMartin — Fri, 04 Jan 2019 17:19:21 GMT

OK, so I tested changing this value from "False" to "True" and it still doesn't work. The fields that do not have a relationship class with a link record work correctly, but the ServiceID field doesn't. For example, my InServiceDate and InServiceYear will copy to the newly created split feature, but the ServiceID does not.

Re: Attribute Assistant: INTERSECTING_FEATURE doesn't work with split and there is a relationship using the field to copy.

JeremiahMartin — Fri, 04 Jan 2019 17:28:38 GMT

Let me try to explain the data model a little better:

There is a table called P_ServicesSummary. This table gets a uniqueid called ServiceID generated by Attribute Assistant. There is a 1:M relationship between P_ServicesSummary (Origin) ServiceID (PK) to the feature class P_Service(Destination) ServiceID (FK).

If the P_Service feature that I am splitting has a ServiceID value that matches a ServiceID in the P_ServicesSummary, it will return null as the value; however, if I enter "dumb data" into the ServiceID field like "12345", so there isn't a matching record in P_ServicesSummary table. The get value will return the "12345" and copy it to the newly created service feature correctly.

I will send the log information shortly.

Re: Attribute Assistant: INTERSECTING_FEATURE doesn't work with split and there is a relationship using the field to copy.

MikeMillerGIS — Fri, 04 Jan 2019 17:33:01 GMT

Please do and a small sample dataset would help. I can run through it in a debugger and see what is going on. What version of the AA are you using. This sounds oddly familiar.

Re: Attribute Assistant: INTERSECTING_FEATURE doesn't work with split and there is a relationship using the field to copy.

JeremiahMartin — Fri, 04 Jan 2019 18:02:54 GMT

I have attached two log files. One where I am splitting the line with a valid relationship, ServiceID = 007000026, and one where I entered an invalid one, ServiceID = 12345. You can see that when the ServiceID = 007000026 the AA returns Null/Empty String, but when it's 12345 it correctly returns 12345.

I am still working on getting you a small dataset.

Re: Attribute Assistant: INTERSECTING_FEATURE doesn't work with split and there is a relationship using the field to copy.

MikeMillerGIS — Fri, 04 Jan 2019 18:11:25 GMT

Don’t see the logs, just email me at mmiller@esri.com<mailto:mmiller@esri.com>. I am off all next week, so will be a delay

Re: Attribute Assistant: INTERSECTING_FEATURE doesn't work with split and there is a relationship using the field to copy.

JeremiahMartin — Fri, 04 Jan 2019 18:21:05 GMT

I believe it is the latest version as of June 27, 2018, as that is when I downloaded it from Git. I don't think there have been any new releases since January 8, 2018.

Re: Attribute Assistant: INTERSECTING_FEATURE doesn't work with split and there is a relationship using the field to copy.

MikeMillerGIS — Fri, 04 Jan 2019 18:24:01 GMT

Ahh, can you try the version in the preview builds. I knew this sounded familiar?

Check out this issue:

https://github.com/Esri/local-government-desktop-addins/issues/224

preview builds

https://github.com/Esri/local-government-desktop-addins/tree/dev/PreviewBuilds

Re: Attribute Assistant: INTERSECTING_FEATURE doesn't work with split and there is a relationship using the field to copy.

MikeMillerGIS — Fri, 04 Jan 2019 18:25:13 GMT

Just reviewing the issue, looks like I did not fix it, and it is something I cannot fix

https://github.com/Esri/local-government-desktop-addins/issues/224