Latest Contributions by JohannesLindner

Ah, OK. For that, you need 2 rules (you should be able to do it in one, but I couldn't get it to work correctly, and it doesn't really matter).   The first rule is a variation of the rule in my previous answer. Instead of only calculating the OutrunNumber for Medium Voltage conductors, it will calculate for all conductor types (but it will skip connectors, banks, etc). And instead of traversing a line, it will traverse a network. // Batch Calculation Attribute rule on ElectricLine // field: OutrunNumber // subtype: empty // exclude from application evaluation // Not a conductor? -> abort if(!Includes([6, 9, 2], $feature.ASSETGROUP)) { return $feature.OutrunNumber } // load all conductors and devices (split into switches and others) // 6: Low, 9: Medium, 2: High voltage conductor var conductors = Filter($featureset, "ASSETGROUP IN (6, 9, 2)") // 23: Low, 37: Medium, 10: High voltage switch var devices = FeatureSetByName($datastore, "ElectricDevice", ["OutrunNumber", "GlobalID"], false) var switches = Filter(devices, "ASSETGROUP IN (23, 37, 10)") var other_devices = Filter(devices, "ASSETGROUP NOT IN (23, 37, 10)") // get the touching switch var out_switch = First(Intersects(switches, $feature)) // no intersecting switch? -> abort // the OutrunNumber will be supplied by the Feature that touches a mv switch if(out_switch == null || IsEmpty(out_switch.OutrunNumber)) { return $feature.OutrunNumber } // traverse the conductor network var c_to_do = [$feature] // conductor features that need to be processed var c_globalids = [] // GlobalIDs of already processed conductors for(var i = 0; i < 9999; i++) { var current_conductor = Pop(c_to_do) Push(c_globalids, current_conductor.GlobalID) for(var next_conductor in Touches(conductors, current_conductor)) { if(!Includes(c_globalids, next_conductor.GlobalID)) { Push(c_to_do, next_conductor) } } if(Count(c_to_do) == 0) { break } } var conductor_updates = [] //var device_updates = [] var new_att = {OutrunNumber: out_switch.OutrunNumber} for(var i in c_globalids) { Push(conductor_updates, {globalID: c_globalids[i], attributes: new_att}) } return { result: out_switch.OutrunNumber, edit: [{ className: "ElectricLine", updates: conductor_updates }] }     The second rule copies the OutrunNumber from an ElectricLine feature to all intersecting ElectricDevice features. // Batch Calculation Attribute Rule on ElectricLine // field: OutrunNumber // subtype: empty // exclude from application evaluation // Not a conductor? -> abort if(!Includes([6, 9, 2], $feature.ASSETGROUP)) { return $feature.OutrunNumber } // load all devices, filter out switches var devices = FeatureSetByName($datastore, "ElectricDevice", ["GlobalID"], true) devices = Filter(devices, "ASSETGROUP NOT IN (23, 37, 10)") var device_updates = [] for(var device in Intersects(devices, $feature)) { var update = {globalID: device.GlobalID, attributes: {OutrunNumber: $feature.OutrunNumber}} Push(device_updates, update) } return { result: $feature.OutrunNumber, edit: [{ className: "ElectricDevice", updates: device_updates }] }     The order of these rules is important! First, the OutrunNumber has to be calculated for the Lines, then it has to be copied to the Devices. Be sure to not select a subtype. ... View more

Convert Time Field indeed seems to ignore milliseconds. Instead, you can use Calculate Field with this Python expression: datetime.datetime.strptime(!TextField1!, "%d-%m-%Y %H:%M:%S.%f")   (Replace "TextField1" with the name of your text field, take care that the name is surrounded by exclamation marks)   Here's a quick test of the Converted vs. the Calculated dates (after I set the Date format for both fields):   ... View more

Not directly, no.   What you could do: Instead of referencing a layer/expression and doing the filtering and grouping in the Indicator widgets, you could create an expression that returns a featureset with two fields: an indicator id and the corresponding value. Then, each Indicator widget would only have to filter for its id and display the value. Something like this: var fs = FeaturesetByPortalItem(...) var out_fs = { geometryType: "", fields: [ {name: "Indicator", type: "esriFieldTypeString"}, {name: "Value", type: "esriFieldTypeDouble"}, ], features: [] } // Indicator 1: var v = Count(Filter(fs, "Field = 123")) Push(out_fs.features, {attributes: {Indicator: "count of 123", Value: v}}) // Indicator 2: var v = Count(Filter(fs, "Field = 345")) Push(out_fs.features, {attributes: {Indicator: "count of 345", Value: v}}) // ... return Featureset(Text(out_fs))   And for the final Indicator, you could just use the SUM of the Value field.     Of course, that would require you to edit all the other Indicator widgets, so it might be easier to just redo the filter for the final Indicator... ... View more

Option 1: Use the Attributes Panel. If you select a feature, you can show all related features in the Attributes Panel and manually select them there.     Option 2: Automatically select all related features You can make it so that when you select a feature, all related features get automatically selected. This options can be found in 2 places: The layer options:   The Attribute Table:   ... View more