AbandonRows

[gprocino]

Check existing issues

• [X] I have checked for existing issues to avoid duplicates.

Markdown file

AttributeAssistant.atbx/Abandon Rows (v3.3)

Description

hi, I used Abandon Rows script for two features. The attribute rules "Abandon Rows" on master feature (like device) doesnt work if the field (like lifestatuscycle=10) change from null value to number 10. Instead if the field value change from number X to 10 it works. Another question is about Association table. If I use "rim" prefix - in abanon rows - for class1 and class2 the system use the some association table for both classes? Do I need to change the prefix for each class when I call the setting script?

thank you

Comments (optional)

Work enviroment: Pro 3.3.1 - UN7 in FileGeodatabase No response

[MikeMillerGIS]

If I use "rim" prefix - in abanon rows - for class1 and class2 the system use the some association table for both classes? Do I need to change the prefix for each class when I call the setting script?

• Yes, that is expected, if a class exist, it will use it.

Looking into the other issue

[MikeMillerGIS]

Can you post this part of your script? Want to see what SQL you used:

[MikeMillerGIS]

Ok, need to think how to properly handle this generically, but for your implementation, you can make the fix by changing

 var a = `__oid__ = 1 AND NOT (${where_clause})`;

to changing to the field in the where clause.

 var a = `__oid__ = 1 AND (NOT (${where_clause}) or <FIELD> IS NULL)`;

To detect if a feature transitioned into the desired state, we not the sql statement, but this does not detect if a feature is null.

[MikeMillerGIS]

The other option if you do not want to change the code, change your where_clause to include a AND FIELD is not Null. Since we not the whole this, that will check to see if the original feature was null and moved to a state.