Latest Contributions by MikeMillerGIS

When you add a tier and there is data, it cannot add it as nullable.  In the asset package, just delete those fields from your classes.  The apply asset package will add these fields/tiers before data so they will be added correctly as nullable.   ... View more

You can check the min version and details on the rule in the Attribute Rule design view.  You can also look at the functions online FeatureSetByRelationshipClass was new at 1.24 https://developers.arcgis.com/arcade/function-reference/featureset_functions/#featuresetbyrelationshipclass If you need to support older versions, you would need to move to https://developers.arcgis.com/arcade/function-reference/featureset_functions/#featuresetbyrelationshipname or manually build the sql and use FeatureSetByName   Here is your code with some checks to handle empty stuff if ($originalfeature.Assembly_ID == $feature.Assembly_ID) { return } var table1FS = FeatureSetByRelationshipClass($feature, "OCGIS.DPW_TESTING_REL", ["Assembly_ID"], false); var first_hop = First(table1FS) if (IsEmpty(first_hop)) { return } var table2FS = FeatureSetByRelationshipClass(first_hop, "OCGIS.DPW_TESTING_Secondary_Table_REL", ["globalid","Assembly_ID"], false); var updates = [] for(var f in table2FS) { if(f.GlobalID == $feature.GlobalID) { continue } if(f.Assembly_ID == $feature.Assembly_ID) continue; var u = { globalID: f.GlobalID, attributes: { "Assembly_ID": $feature.Assembly_ID } } Push(updates, u) } if (Count(updates) == 0 ){ return } return { edit: [{ className: "OCGIS.DPW_TESTING_Secondary_Tabe", updates: updates }] }   ... View more

you just need to add some checks for first(fs) returning null ... View more

Simply closing a map does not work, you need to close and restart pro.  Once a map is open, it is always open in that pro session.   You do not need a new asset package, just use the one you have on 3.3 ... View more

Did you run Upgrade Geodatabase first? Important note in Update Dataset: For Utility Network Version 7 and later, the enterprise geodatabase version must be 11.2.0 or higher to support 64-bit object IDs and big integer fields. ... View more

This is BUG-000157937 and was fixed in 3.3 btw.   ... View more

We have seen this when you run apply and have maps in a project.  Especially active maps.  There is a corruption that occurs.  We suggest running apply asset package in a pro project with no maps.   ... View more

If the row is coming over, but the blob is not usable, then I suggest you log a bug.  Something is not loading correctly with the attachment.  Are your attachments photos? ... View more

I would suggest just removing the FeatureGlobalID field.  It was needed in an earlier version, is no longer needed. ... View more

Sorry, not FeatureSetByAssociation(was working on a rule using that).  FeatureSetByRelationClass Needs a lot more work, but something like this.   var table1FS = FeatureSetByRelationshipClass($feature, “pole_inspection”, [“comments”], false); var table2FS = FeatureSetByRelationshipClass(First(table1FS), “pole_history”, ["globalid",“comments”], false); return { 'edit': [{ 'className': 'pole_history', 'updates': [{ 'globalID': first(table2FS.globalid), 'attributes': { 'comments': first(table2FS.comments) } }] }] }   ... View more

sure, you need to use FeatureSetByAssocation($feature) to get the table 1 feature, then use that feature again in FeatureSetByAssocation(ResultFeatureFromFirst) to get the second.  Then issue the DML to update that feature. You can also just use featureSetByName and just build the pkey/fkey sql if you want too.  Same process ... View more

Not sure a relationship class will work, unless you publish a service without version management. We suggest using a client side relate. You can create them in pro or via arcade(not using feature set by relate) using a feature set query in a pop up ... View more

If you put a SQL query on batch trace for that one row, does it work? What if you put default terminal Id to 1? Does your junction layer have a field called terminalid or featureglobalid? If you pass in the starting point layer that you used to test the trace(in default database) to batch trace, does it work? For tracing junctions, the required fields are featureglobalid(if does not exist, batch trace looks for globalid) and terminal Id. ... View more