Latest Contributions by Billy

Hi, It work well in a FGDB. No error. ... View more

Test went well. But I made a small change to the IF statements. It should be " If Not Empty" --> If (!IsEmpty()){} Here is the updated code: var atts = { 'phasesnormal': transf_phase, 'phasescurrent': transf_phase, 'phasessummer': transf_phase, 'phaseswinter': transf_phase, 'addpowerrating': closestf['Bayonet_fuse_rated_amp'] } if(!IsEmpty(closestf['InstallationDate'])){ atts['installdate'] = closestf['InstallationDate'] } if(!IsEmpty(closestf['TapDate'])){ atts['inservicedate'] = closestf['TapDate'] } return { 'result': field_value, 'edit':[{ //updates the fuse feature attributes 'className': 'UN_MODEL_V34.MODEL_V34.ElectricDevice', 'updates': [{ 'globalID': $feature.globalID, 'attributes': atts } }] }] } }   ... View more

Hi Josh, Your code looks like another way to avoid the error with lest code, and it should save me the work to find all the feature that were assigned the date "12/30/1899" and replace it with a field calculation process in the attribute table. I will test it and report back the result. Thanks.   ... View more

I will test it and get back to yo with the result. Let me take the opportunity to see if you can take a look at this question that I posted about copying attachments with Arcade: Copy Pictures Taken with Field Maps to Utility Net... - Esri Community Thanks.   ... View more

Hi, I'm running Pro 2.8, but Enterprise 10.8.1 ... View more

Hi Josh, Thanks for your answer. Below you can see the section of the code where the assignment is done and the returned dictionary is defined. Before this section the code is just finding the closest source feature, which is not related to the problem. As you can see, I'm updating multiple fields, hence the used of the dictionary. The IF statement is the workaround that I mentioned in the third paragraph of my original question. Below you can see images with the field view in ArcGIS Pro for the source class and the target class.   // Extract fuse attributes from closest source feature var fuse_addpowerrating = closestf['Bayonet_fuse_rated_amp'] // This is the fuse rated current var fuse_installdate = closestf['InstallationDate'] // Fuse installation date var fuse_inservice_date = closestf['TapDate'] // Fuse inservice date var phasesnormal = transf_phase // Domain assign to field var phasescurrent = transf_phase // Domain assign to field var phasessummer = transf_phase // Domain assign to field var phaseswinter = transf_phase // Domain assign to field if (IsEmpty(fuse_installdate) || IsEmpty(fuse_inservice_date) ) { fuse_inservice_date = null fuse_installdate = null } // Return dictionary with the data to transfer to the target feature return { 'result': field_value, 'edit':[ { //updates the fuse feature attributes 'className': 'UN_MODEL_V34.MODEL_V34.ElectricDevice', 'updates': [{ 'globalID': $feature.globalID, 'attributes': { 'phasesnormal': phasesnormal, 'phasescurrent': phasescurrent, 'phasessummer': phasessummer, 'phaseswinter': phaseswinter, 'addpowerrating': fuse_addpowerrating, 'installdate': fuse_installdate, 'inservicedate': fuse_inservice_date, //'model': fuse_model } }] } ] } }   Source Feature Date Fields     Target Feature Date Fields     ... View more

Hi Johannes, Thanks for the answer. It makes sense. I think that the documentation should be more clear about this. In my process of trying to identify the source of the error, I notice that even if I change the global $map to $datastore, on line 20 of the code above, if I used a variable to input the class name ('source_layer') this will also trigger the error 999999. Only when I used the literal name of the class in the database the error was not triggered: var fsSource = FeatureSetByName($datastore, 'UN_MODEL_V34.MODEL_V34.Poles_to_Riser_Disconnect_Match',['*'], false)   ... View more

Hi Michael, I stopped the service in Server Manager only. I didn't do anything on the machine running ArcGIS Server. ... View more

Hi Hussein, Thanks for the link to the blog, it was very useful. It looks like this blog is not part of the "Attribute Rules" forum because I did several searches before starting this question to see if there was a blog or previous questions related to this topic. After following the examples in the blog I was able to find that the problem with my original rule was that I was using the keyword "fromTerminal" instead of "toTerminal" to connect to the "SS:S2" terminal of the Fuse feature. Here is the correct code: // Assigned To: ElectricJunction // Name: Proximity_Connectivity_Association // Description: Upon insertion of an ElectricJunction of the allowed AssetTypes // creates the connectivity association to the closest ElectricDevice MV Fuse or // MV ElectricJunction Line End // Subtypes: All // Field: notes // Execute: Insert // Exclude from application evaluation: True // ************* User Variables ************* // This section has the functions and variables that need to be adjusted based on your implementation // The field the rule is assigned to var field_value = $feature.notes; var association_class = null; var search_distance = 100; var search_unit = 'feet'; var feat_globalid = $feature.globalID; var valid_asset_types = [103]; // 103 = MV Line End\Riser // ************* End User Variables Section ************* if (indexof(valid_asset_types, $feature.assettype) == -1) { return field_value; } //Find the closest MV Fuse var fsDevices = FeatureSetByName($datastore, 'UN_MODEL_V34.MODEL_V34.ElectricDevice',["GLOBALID"], false) var fBuffer = Buffer(Geometry($feature), search_distance, search_unit) var fsClosest = Intersects(fsDevices, fBuffer) var fsFuses = Filter(fsClosest, 'ASSETTYPE = 565') //565 = MV Fuse\Overhead Cutout Fused Load Break var minDistance = Infinity if (Count(fsFuses) <= 0) { var fsElecJunction = FeatureSetByName($datastore, 'UN_MODEL_V34.MODEL_V34.ElectricJunction',["GLOBALID"], false) fsClosest = Intersects(fsElecJunction, fBuffer) var fsLineEnd = Filter(fsClosest, 'ASSETTYPE = 100') //100 = MV Line End\Overhead Line End if (Count(fsLineEnd) <= 0) { return field_value } else { association_class = 'UN_MODEL_V34.MODEL_V34.ElectricJunction' var closestle = null // closest MV Line End feature for (var p in fsLineEnd) { var pDistance = Distance(p, $feature, 'feet') if (pDistance < minDistance) { minDistance = pDistance; closestle = p } } } } else { association_class = 'UN_MODEL_V34.MODEL_V34.ElectricDevice' var closestf = null // closest MV Fuse feature for (var p in fsfuses) { var pDistance = Distance(p, $feature, 'feet') if (pDistance < minDistance) { minDistance = pDistance; closestf = p } } } if (!IsEmpty(closestf)) { var assocation_update = [{'globalID': closestf.globalID, 'toTerminal': 'SS:S2' ,'associationType': 'connected'}]; } else if (!IsEmpty(closestle)) { var assocation_update = [{'globalID': closestle.globalID, 'associationType': 'connected'}]; }else { return field_value; } var edit_payload = [{'className': association_class, 'updates': assocation_update}]; return { "result": field_value, "edit": edit_payload };   ... View more

Hi Johannes, Thanks for your reply. The behavior without your suggestion is this: Code: if (!IsEmpty(closestf)) { var assocation_update = [{'globalID': closestf.globalID, 'fromTerminal': 'SS:S2' ,'associationType': 'connected'}]; } else if (!IsEmpty(closestle)) { var assocation_update = [{'globalID': closestle.globalID, 'associationType': 'connected'}]; }else { return field_value; } var edit_payload = [{'className': association_class, 'updates': assocation_update}]; return { "result": field_value, "edit": edit_payload };   Error message trying to Create Association between the Riser and the Fuse with terminals (line 2 of code above): Error in Pro:   Successful when trying to Create Association between the Riser and the Line End (line 4  of the code above), and I'm not using the "attributes" keyword in the dictionary as you suggest:   2. Behavior with your suggestion to include the "attributes" keyword in the dictionary: Code: if (!IsEmpty(closestf)) { var assocation_update = [{'globalID': closestf.globalID, 'attributes': {'fromTerminal': 'SS:S2' ,'associationType': 'connected'}}]; } else if (!IsEmpty(closestle)) { var assocation_update = [{'globalID': closestle.globalID, 'associationType': 'connected'}]; }else { return field_value; } var edit_payload = [{'className': association_class, 'updates': assocation_update}]; return { "result": field_value, "edit": edit_payload };   Error message trying to Create Association between the Riser and the Fuse with terminals (line 2 of code above): Successful when trying to Create Association between the Riser and the Line End (line 4  of the code above), and I'm not using the "attributes" keyword in the dictionary as you suggest:   My conclusion at this point is that the documentation explaining the syntax of the dictionary should be expanded with better examples on how to create the different associations (connectivity, attachment and containment) between the utility network features with and without terminal. Also, I'm not sure if I have to use the keyword "adds" or "updates". One of the examples in the arcade-expressions github page uses "adds" to create new association (https://github.com/Esri/arcade-expressions/blob/master/attribute_rule_calculation/CreateAssociation.md); the other uses "updates" (https://github.com/Esri/arcade-expressions/blob/master/attribute_rule_calculation/CreateAttachmentAssociationByProximity.md). Also, notice that none of these sample codes use the keyword "attributes" in the returned dictionary.   ... View more