Latest Contributions by JeffMiller

Hello all, I have what seems to be a fairly simple question, but for whatever reason I'm having trouble with it.... I am attempting to geocode a table that I've received from a third party application.  Aside from an address field, there are several other fields in this table I would like to use in my geocoding result.  After running the geocode, which does its job, I get a typical geocode table, with the addresses and match value information.  My question is, is there a way to include the other fields present in the input table to the geocoding result when the process is ran?  I'd like to do some mapping with these fields, but they are not brought over through the geocoding process. Any guidance is appreciated ... View more

Hello all, I seem to be having an issue with one of the value methods I am trying to employ.  I have several "copy feature" value methods set up in the attribute assistant dynamic value table.  They are designed to copy a feature to a historic feature class when the plan status field is changed to abandoned.  I have set up the value info field as follows: A|ssHPIPE||CUT|FACILITYID-LEGACYID I am aware that newer versions of the attribute editor no longer support the CUT option, but the version I am using does still support it, and it is functioning properly in dozens of other instances.  The problem I am having is specifically with the ssMANHOLE, ssMAIN and rwMAIN feature classes.  When I set the plan status field to abandoned on these feature classes, I receive the following error: The property values cannot be changed Unable to obtain primary key value for origin object The feature is deleted The feature is deleted The feature is deleted I'm not sure if the disconnect is in the structure of those specific feature classes, in the attribute assistant tool itself (perhaps this is why CUT is no longer supported), or something completely different.  Has anyone experienced this, and if not, any thoughts as to where I may be going astray? Thanks in advance! ... View more

Hello all,      I have a question regarding the nearest feature function in the attribute assistant, and I was hoping someone far smarter than I could shed some light on this.      I have an odor control feature class that contains a field called featuretype, which is populated by a domain containing SINJECT and AIRJUMP options.  Utilizing the nearest feature rule, I would like to populate the SFACILITYID field in this table with the facility ID from the nearest Facility whenever a new odor control line is created.  The catch, however, is that I only want this to occur when the featuretype is set to SINJECT, as the AIRJUMP devices are not truly associated with a facility.  I'm not sure if there is a way to modify this rule, or if there is another rule that I'm missing that may do the job.       Any help would be much appreciated! Cheers! ... View more