Branched updates from single Join

Question

If I run the updates individually, the attribute table is updated correctly.

If I have all branches in places from the Join and run, the Updates do not perform. What is the correct way to handle a flow like pictured below, where multiple fields are being calculated from a joined database.

Thanks

ToddPlank2 · Answer

1.  Each update is going to a different field. One update is not overwriting the value in a field of a previous update. There are four updates and four separate fields being updated.  It is just taking the value in a joined field and calculating it to a corresponding field in the feature layer.

When I run the pipeline, I can see it go through each update, one at a time, and give the green checkmark after each, but you're telling me this is not a correct way of doing the pipelines.  I'll revamp and try again.

Thanks

BethanyScott · Answer

Hey @ToddPlank2 ,

Thank you for the quick response!

Some thoughts:

* I believe what is happening with your current workflow is that each output is being overwritten with the next. For example, in the first output you see the CBL field calculated as expected. But once the next output is run, it's going to overwrite that CBL field with nulls (or whatever is in the CBL field before you calculated it).

In order to get all field values in the output, they must all be in the dataset that you use to update the layer. This means you'd need to string the calculates from one to another instead of having them on their own.

* Filter by attribute will remove records that do not meet the conditions specified in the query. If the intention was to only calculate records that meet certain conditions, but keep the others in the result, you'll need to use a conditional statement in your Calculate field expression. For example, when you calculate the UVD field you could do something like this:

if ( $record.S_M != Null) {
return "Value I want in the UM field when S_M is Null"
}
else {
return "Value I want in the UM field when S_M is not Null"
}

This will keep all records, but only calculate for the ones you want to keep. Note: The else is optional, by default any records that do not meet the if condition will be calculated with Null values.

Ultimately, you'll want a linear data pipeline (example below) where all fields are being calculated in sequence. This means when you update the layer, all fields will be populated as you want them in the feature layer.

If you need help with how to craft the conditionals you need in Arcade, please feel free to ask here. I also want to highlight the Arcade playground, here: https://developers.arcgis.com/arcade/playground/ . You can use this to try things out.

Please let me know if I'm misunderstanding or if you have any additional questions. 🙂

Thanks again,

Bethany

ToddPlank2 · Answer

1.  All outputs are updating the same layer

2.  Within the pipeline each process runs and I get the Green dot for each output but the results are not written for each of the fields to the output.  If I break the tree and run each one individually, the output is written.

3. Records do display in the preview.