Latest Contributions by BrianBulla

Here is the final product.  It's working nicely! // for features without INSP_STATUS, return the subtype if(IsEmpty($feature.INSP_STATUS)) { var subtypes = ["MaintenanceHole", "InspectionMH", "BackFlow", "DiversionMH", "FlapGateMH"] var i = $feature.SubtypeCD - 1 return subtypes[i] } // for features with INSP_STATUS = YES if ($feature.INSP_STATUS == "YES") { return "YES" }; // for features with INSP_STATUS = WR LOW if ($feature.INSP_STATUS == "LOW") { return "LOW" }; // for features with INSP_STATUS = WR HIGH if ($feature.INSP_STATUS == "HIGH") { return "HIGH" }; // for features with INSP_STATUS = CR if ($feature.INSP_STATUS == "CR") { return "CR" };   ... View more

Thanks Johannes.  Arcade to the rescue again!  I will check this out and see if I can get it to work. ... View more

OK, that makes sense.  I wonder how offline data will work in Field Maps with attribute rules.  Hmmm.. Thanks for your help!   ... View more

All other values would work if I only had one type of INSP_STATUS, but I have 4 different values that INSP_STATUS could possible be. So 5 types of subtypes and 4 types of INSP_STATUS.  That's a total of 20 different combinations of symbols if I did it all manually, but there has got to be a better way of doing this. ... View more

Manual Breaks??  I'm not sure what you are talking about.  I'm using Unique Values with two attributes....Subtype Code and INSP_STATUS.  I'm not symbolizing numerical data. ... View more

Sorry @JohannesLindner .  I actually think it is working.  After trying again it's working now. Thanks for your help!!  I was actually talking about this with the Field Maps team while at the Dev Summit a couple weeks ago.  It was their idea to try Attribute Rules to automate some logic we are currently using in ArcPad applications in our transition to Field Maps.  It looks like this will work. Thanks again! ... View more

Hi @JohannesLindner  OK, so an update here... I made some code changes and it appears that when you run the "Verify" it is using the first record in the table, not the last.  So that definitely helps to know when troubleshooting. So if I edit that first record, I seem to get the results I am expecting in 'verify' mode, but when adding a new record, I do not see any change to the hydrant INSP_STATUS.  Any ideas what might be going on??   // Calculation Attribute Rule on the inspection table // field: leave empty // triggers: insert // exclude from application evaluation console("TEST") // get the hydrant feature var hydrants = FeaturesetByName($datastore, 'WAT_Hydrant', ['FACILITYID', 'ObjectID'], false); var facility_id = $feature.FACILITYID; var hydrant = First(Filter(hydrants, 'FACILITYID = @facility_id')); //Check for an Out of Service (OOS) inspection first if (($feature.OUT_OF_SERVICE != null) && ($feature.DATEWORK == null)) { console("OOS") // abort if no hydrant was found if(hydrant == null) { return }; //update INSP_STATUS in the hydrant layer to OOS return { 'edit': [{ 'classname' : 'WAT_Hydrant', 'updates' : [{ 'objectID': hydrant.ObjectID, 'attributes' : {'INSP_STATUS' : 'OOS'} }] }] }; } //Next, check to see if it's a Work Required (WR) inspection if ((($feature.HYDRANT_OPERATION != null) || ($feature.OPERATING_NUT != null) || ($feature.NOZZLE_CAPS != null) || ($feature.FLANGES != null) || ($feature.SECONDARY_VALVE != null) || ($feature.WATER_IN_BARREL != null)) && ($feature.DATEWORK == null)) { console("WR") // abort if no hydrant was found if(hydrant == null) { return }; //update INSP_STATUS in the hydrant layer to OOS return { 'edit': [{ 'classname' : 'WAT_Hydrant', 'updates' : [{ 'objectID': hydrant.ObjectID, 'attributes' : {'INSP_STATUS' : 'WR'} }] }] }; } //If it gets this far, then it's just a normal inspection, so set it to Inspected (YES) console("YES") console(hydrant.FacilityID) if(hydrant == null) { return }; return { 'edit': [{ 'classname' : 'WAT_Hydrant', 'updates' : [{ 'objectID': hydrant.ObjectID, 'attributes' : {'INSP_STATUS' : 'YES'} }] }] };   ... View more

Hi @JohannesLindner .  Yes, I have seen that before, but in this case when I run the "Verify" it is not coming up.  Here is my code where I inserted the console message, so it should come up everytime. But what is happening when I hit this verify?  What is this running against?  There are records in my table this rule is getting set on, but how does it (or I) know what record is being used when I hit the verify button?       if (($feature.OUT_OF_SERVICE != null) && ($feature.DATEWORK == null)) { // get the hydrant var hydrants = FeaturesetByName($datastore, 'WAT_Hydrant', ['FACILITYID', 'ObjectID'], false) var facility_id = $feature.FACILITYID var hydrant = First(Filter(hydrants, 'FACILITYID = @facility_id')) console(hydrant.ObjectID) // abort if no hydrant was found if(hydrant == null) { return } //update INSP_STATUS in the hydrant layer to OOS return { 'edit': [{ 'classname' : 'WAT_Hydrant', 'updates' : [{ 'objectID': hydrant.ObjectID, 'attributes' : {'INSP_STATUS' : 'OOS'} }] }] } }       ... View more

Hi Jonannes. Ok, so that error message I was getting was becuase I didn't have a GlobalID on my inspection table, so I added that, updated the code as per your sample above, and it kind of sort of works.  I don't get any errors, but I also don't get INSP_STATUS to update. I've insert a console statement to try and do some debugging, but where to the console statements come out?  I can't seem to find a console window or anything in Pro. ... View more

Hi, yes, I have been building this step by step, so the names are correct. I just did a re-type of the code and now it seems to be working.  Maybe the order in which the fields are updated makes a difference??  Or the formatting of how I have things typed in??  Now it looks like this and seems to be working. This is my first time working in Arcade.  It seems very finicky.     ... View more

Oh geez.  Yeah....that is a problem.  Always good to have a second set of eyes, but still something is not working even with this update.  Those are for sure the correct field names.   return {"result" : {"attributes" : {"FACILITYID" : "HYD-" + intersectingGrid.GRIDNO + "-" + NextSequenceValue("SeqHydrants"), "GRIDNO" : intersectingGrid.GRIDNO}}} ... View more