Latest Contributions by RPGIS

You're welcome. ... View more

It is still a relatively new language that even I don't know why some things work and others don't. I also code in python and only started using arcade about a year ago, and I still don't understand why some things that work in other programming languages doesn't work in arcade. I also didn't realize that I made a mistake in one of the examples that I provided. You could have the field name variable used within the FeatureSetByName. That I know does work. I will need to update it to show that. ... View more

We are using 3.2 but we were told it won't work past 2.9. ... View more

The issues with this, that I have discovered, is there is a bug that ESRI is aware of where assigning the feature name to a variable will cause some issues. The FeatureSetByName is used to call an entire feature. With this you have to specify the exact name of the featureclass or table, otherwise it will result in an error when you try to run the code. The other thing is you have to include all fields that you want to check. I noticed that the "OBJECTID" field was missing which would also result in an error. It will check when running the code validation for errors but result in an error when ran. The Expects can be used on $featureset or $feature, but if used on $feature will only return values within that row/record. You will want to specify a $featureset in order to return all values within the specified table/featureclass. Give the code below a try and see if it works for you.   // INPUTS var fcName = "TEST" var fldName = "Name_Text" var OIDField = 'OBJECTID' var Testing = $feature.Name_Text // These two lines must be written with the actual strings, not the variables above. Expects($featureset, OIDField , fldName ) for (var i in $featureset) { if ((i[fldName] == Testing ) && (i[OIDField ] != $feature[OIDField ])) { return {"errorMessage": "ERROR: value not unique within field!"} } } // If error above not found, return results dict with value as-is. var fldUpdates = { fldName : Testing } Console({"result": {"attributes": fldUpdates}}) return {"result": {"attributes": fldUpdates}}   If that code does not work you can try this one.   // INPUTS var fcName = "TEST" var Testing = $feature.Name_Text var OID = $feature.OBJECTID var OIDField = "OBJECTID" var NameField = "Name_Text" // These two lines must be written with the actual strings, not the variables above. var features = FeatureSetByName($datastore, "TEST", [OIDField , NameField ]) for (var i in features) { if ((i[NameField] == Testing ) && (i[OIDField] != OID )) { return {"errorMessage": "ERROR: value not unique within field!"} } } // If error above not found, return results dict with value as-is. var fldUpdates = { NameField : Testing } var Result = {"result": {"attributes": fldUpdates}} Console(Result ) return Result     ... View more

Here is what I use which might be of some help. This function gets field names in a feature that are not in the list of omitted field names. If there isn't a list of field names to omit, include all field names.   function GetFieldNames( InputFeature , OmitFields ){ var FieldNames = [ ] var FeatureInfo = Schema(InputFeature).fields for ( var i in FeatureInfo ){ // Get the field name of the input feature var fieldname = FeatureInfo[ i ].name if ( Boolean( OmitFields ) ) { if ( Includes( OmitFields , fieldname ) == False ) { Push( FieldNames , fieldname ) } } else { Push( FieldNames , fieldname ) } return FieldNames }     This function finds all matching field names between two features.   // Get matching field names found in both lists function GetMatchingFields( FieldListA, FieldListB ){ var MatchingFields = [ ] // Loop through the list of field names in list A for ( var i in FieldListA ){ var fieldname = FieldListA[i] /* If list of field names in list B includes the field name in list A then append the field name to the matching list of field names */ if ( Includes( FieldListB , fieldname ) ){ Push( MatchingFields, fieldname ) } } return MatchingFields }     This one gets all attributes from a feature based on input field names.   // Get feature attributes based on field list function GetFeatureAttributes( FieldList ){ Expects( $feature , '*' ) var Attributes = Dictionary( $feature ).attributes var SpecificAttributes = { } if ( IsEmpty( FieldList ) == False ){ for ( var f in FieldList ){ SpecificAttributes[ FieldList[ f ] ] = Attributes[ FieldList[ f ] ] } } else { SpecificAttributes = Attributes } return SpecificAttributes }     These may be of some use to you but I have used these to automate a lot of attribute rules. It also takes the guess work out of having to do things manually.   You can also use the get matching field names function with the get field names function(s) as inputs. MatchingFieldNames = GetMatchingFields( GetFieldNames( InputFeature , OmitFields ), GetFieldNames( InputFeature , OmitFields )) ... View more

Hi @EMiller_2, Without knowing what the string looks like, it could be that the code is not set properly or there are other characters in the string that is preventing the character replacements. An option to fix this is:   """Expression""" Expression = NewString( Field or Value ) """Code Block""" def NewString( InsertString ): New = None if type( InsertString ) != str: pass else: if ',' in InsertString: New = InsertString.split( ',' ) New = '_'.join( New ) else: pass if New: return New else: return   ... View more

You can set to limit the map to only the extent of a specified shape within a map series, and you can also specify exceptions for displaying layers. This is set in the map properties. Or this option can be set within the map series setting.     ... View more

You can change the order of rule by double clicking on the order number and typing in the order that you wish. ... View more

You can always change the order of a rule by simply double clicking on the order number and changing it manually to the desired order. ... View more