nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Problem with Field Calculator

aam

I am using ArcGIS Pro, I have a Feature Class along with standalone tables, the content of tables need to be brought into the Feature Class.

The Table contains over 6000 records and I use Definition query to filter out the records that I need to bring in. I do a join based on the Primary ID and then using the Field Calculator to populate the records from the joined table. However when I run the Field Calculator, the records that I are suppose to be hiding (filtered out) are being populated.

Has anyone experienced this before, how can I overcome this?

Encuentra más publicaciones etiquetadas con

Analysis

Content Management

Geodatabase

Accepted answers

All comments

rzufelt

Good to hear.

Sometimes there is no "answer", so you just trial and error until you find out where the issue is.

aam

So I just exported the filtered results to a separate table and then did the join based on the new table. It worked.

aam

This is what I am going to do next. I feel the project file might be corrupted.

rzufelt

You can do a "reverse" join, but you can only calculate on the original table, not the joined table, or it will give you errors like you see.

So, exporting the feature class and table to new geodatabase items, loading the new FC and table into a new project (could be issues with data, table or aprx.), you still have these same issues?

aam

I've never used Arcade. Curious to know where exactly do I write the code?

aam

I get this error if I do the reverse join.

BryndaHatch

could you try doing the join in the other direction?

rzufelt

I agree, it kind of looks like an indexing issue, but I don't know if/where that could be changed with the calculate tool.

I'm at a loss. I've tried what I can to reproduce, but can't.

Thought maybe it was getting confused with the alias (with special characters and all), but doesn't seem to make a difference for me (on 2.9.2).

If it were me, I'd add just the FC and single table to a new Pro project and see if the issue persists. If so, would export the table to a new geodatabase table (maybe even check geometry on the FC), add that and see if it works. Might be some mystery "corruption" in the table or FC somewhere.

(Actually, if it were me, I'd try the arcade by @jcarlson as it helps me learn other ways. Also, if the Arcade produces the same results, would defiantly suspect a data issue).

aam

I edited the original post as the main concern here is the values that are supposed to be hidden are being used to populate the records.

I used this same table before to populate the total population and now using it for each age group. The values that are being populated are the ones for the total count. I wonder if Indexing has anything to do with it?

aam

That was a good suggestion and I tried that but I am getting the same results.

rzufelt

I see you changed the original question from populating with the wrong field values to filtered out fields are being populated as well. Yet, the video demonstrates what the question "used" to be, populating from a different field.

Are you seeing both of these?

rzufelt

Are the tables geodatabase tables or Excel?

What if you don't put a definition query on the lookup table, but put the join on the Feature class, show only matching data (when establishing the join), then put the definition query on the feature class only.

jcarlson

Something must be going funny in between the join and the calculation. Thank you for sharing the video, it's much easier to see what's going on.

Personally, I would use Arcade to make absolutely sure that the other table is being filtered the way you intend it to be. You can get the matching feature based on the ID and filter the layer at the same time.

var x = $feature.['primary_id_field']

var lyr = FeatureSetByName(
    $map,
    'the other layer',
    [
        'primary_id_field',
        'the_other_attribute_you_want',
        'attribute_in_your_definition_query'
    ],
    false
)

var feat = First(Filter(
    lyr,
    `primary_id_field = ${x} AND attribute_in_your_definition_query = some_value`
))

return feat['the_other_attribute_you_want']

aam

Here is the video of what I am doing

aam

Here is the video of what I am doing

BryndaHatch

The Field Calculator will either work on a selected set of records or, if nothing is selected, it will work on all of the records. Perhaps, after setting your definition query to hide the records you don't want, select the remaining records before running the Field Calculator.

jcarlson

To prevent populating the other features, you can:

Select by Attributes first, run the calculation on the selection. Or,
Include a statement in your calculation that checks the attribute value, and leaves it alone if it is not one of the target rows

What language are you using? If you use Arcade, there's no reason to perform a join ahead of time.

var x = $feature.['primary_id_field']

var lyr = FeatureSetByName(
    $map,
    'the other layer',
    ['primary_id_field', 'the_other_attribute_you_want'],
    false
)

var feat = First(Filter(
    lyr,
    `primary_id_field = ${x}`
))

return feat['the_other_attribute_you_want']

rzufelt

Screenshot of the calculator tool?

Is it possible you have the same attribute name in the feature class as well as the joined table?

If so, make sure you scroll down far enough to pick the joinedtablename.FieldName (not just FieldName) so it knows to pull the data from that table/field.

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.