topic Re: ArcGIS Pro 3.3.1- Exporting Join Creates NULL values in New Feature's Table in ArcGIS Pro Questions

ArcGIS Pro 3.3.1- Exporting Join Creates NULL values in New Feature's Table

DylanHinton — Tue, 30 Jul 2024 15:04:52 GMT

I updated my ArcGIS Pro from 3.2.2 to 3.3.1 last week and its impacted my weekly workflow a little bit. Once a week, I will perform a join between a feature layer (which is connected to an sde database) and an already exported/static table, and then export the resulting joined layer as a new feature in Pro and publish it online. Now, I can perform the join successfully between my feature layer and table with all the attribute fields showing their values. Unfortunately, the values in the join table become null once they are exported as the new joined feature. I was wondering if anyone has run into this issue?

To trouble shoot this issue, I have tried to index the fields, as well as, ensured that my project is using field types that are compatible with 3.1 and earlier versions. If I export both my feature layer and table separately and then try to join and export them it preserves the joined attributes in the export. It just seems to take a long time to perform the export.

I can also perform the join in ArcMap and bring the exported feature into Pro and go from there, but I wanted to see if this has happened to anyone using 3.3.1. My workflow has not changed between 3.2.2 and 3.3.1 but the null values from the export are new.

Thanks for your time

Re: ArcGIS Pro 3.3.1- Exporting Join Creates NULL values in New Feature's Table

MichaelVolz — Tue, 30 Jul 2024 15:13:02 GMT

Dylan:

How did you ensure that your field types are compatible with 3.1 and earlier versions?

Re: ArcGIS Pro 3.3.1- Exporting Join Creates NULL values in New Feature's Table

DylanHinton — Tue, 30 Jul 2024 15:18:35 GMT

Under Projects>Map and Scene>Add Layers and Tables>"Use field types that are compatible with ArcGIS Pro 3.1..." I just keep that box checked due to some issues we were having a couple of months ago with one of our field types breaking

Re: ArcGIS Pro 3.3.1- Exporting Join Creates NULL values in New Feature's Table

MichaelVolz — Tue, 30 Jul 2024 15:27:18 GMT

Do you think the new data types are being added with the tabular data that is being joined to your SDE data, even though you have that setting checked?

Have you verified that the data is still in Pro 3.1 compatible format where it is not using the high precision data field type or big integer field type (I would suggest seeing if you can load the table into ArcMap as a test)?

Re: ArcGIS Pro 3.3.1- Exporting Join Creates NULL values in New Feature's Table

DylanHinton — Tue, 30 Jul 2024 15:43:56 GMT

I can bring in both the feature layer and the table and perform the join and export successfully with no issues in ArcMap.

Re: ArcGIS Pro 3.3.1- Exporting Join Creates NULL values in New Feature's Table

MichaelVolz — Tue, 30 Jul 2024 16:11:59 GMT

So I am doing similar automated operations using python where I am trying to revert to Pro 3.1 field types using useCompatibleFieldTypes, but this code just gets ignored.

I am wondering if you can bring the table into a file gdb in Pro 3.3.1 with the Pro 3.1 field types checked and then see if you can view that file gdb table in ArcMap after it was initially created in Pro 3.3.1.

Re: ArcGIS Pro 3.3.1- Exporting Join Creates NULL values in New Feature's Table

DylanHinton — Tue, 30 Jul 2024 16:28:41 GMT

Hi Michael, so I tried viewing the attribute field for the feature after performing the export in Pro and saving it to a local gdb. Unfortunately, its still showing the null values for me.

Re: ArcGIS Pro 3.3.1- Exporting Join Creates NULL values in New Feature's Table

Bud — Tue, 30 Jul 2024 19:07:26 GMT

Is your join one-to-many? If the answer is no, are you 100% sure?

I ask because one-to-many joins in ArcGIS Pro are pretty buggy. Is ArcGIS Pro the right tool for tabular/join-based geodatabase analysis?

Possibly related:

Export join to FGDB: Join table ID field is null

Esri Case: 03616469
BUG-000146098

Join with definition query: Export has more rows than input (definition query is ignored)

Esri Case: 03619440
BUG-000167563, BUG-000135505

Re: ArcGIS Pro 3.3.1- Exporting Join Creates NULL values in New Feature's Table

Bud — Tue, 30 Jul 2024 18:54:13 GMT

If your join is one-to-many, you could try creating a one-to-one join instead and see if you have the same issue. Pro now has the option to choose the join type: Choose if join will be one-to-first or 1:Many

You could also try removing any definition queries to see if it behaves differently.

Re: ArcGIS Pro 3.3.1- Exporting Join Creates NULL values in New Feature's Table

Bud — Tue, 30 Jul 2024 18:56:29 GMT

Does the Join Field geoprocessing tool (exports a copy FC) behave the same way as Add Join (dynamic)?

Re: ArcGIS Pro 3.3.1- Exporting Join Creates NULL values in New Feature's Table

DylanHinton — Tue, 30 Jul 2024 20:20:17 GMT

Hi Bud, so I'm joining one-to-one with no issues. My join is successful and I can see the data when I open up the input's attribute fields. Once I export the feature, however, the exported table nulls out the join table's values. Pro 3.3 allows me to export the same table join with another feature layer though. So, I'm guessing its something to do with this specific feature layer

Re: ArcGIS Pro 3.3.1- Exporting Join Creates NULL values in New Feature's Table

Bud — Tue, 30 Jul 2024 20:36:00 GMT

Sounds similar to what I had in BUG-000146098

Re: ArcGIS Pro 3.3.1- Exporting Join Creates NULL values in New Feature's Table

DylanHinton — Tue, 30 Jul 2024 20:53:51 GMT

Yep that sounds exactly it. For whatever reason, it just doesn't want to export the join between this one specific feature layer and the table. I may have to just put a ticket in with ESRI and go from there

Re: ArcGIS Pro 3.3.1- Exporting Join Creates NULL values in New Feature's Table

MichaelVolz — Wed, 31 Jul 2024 18:33:11 GMT

The bug was supposedly fixed at Pro 3.0 as it was initially reported at Pro 2.9.1.

Re: ArcGIS Pro 3.3.1- Exporting Join Creates NULL values in New Feature's Table

DylanHinton — Wed, 31 Jul 2024 21:21:53 GMT

It wasn't an in issue in 3.2.2 for me, but I updated to 3.3.1 and now its a problem. I did not change my workflow and it just doesn't like keeping exported join values for whatever reason

Re: ArcGIS Pro 3.3.1- Exporting Join Creates NULL values in New Feature's Table

Bud — Wed, 31 Jul 2024 21:35:43 GMT

Sometimes, there are "regression bugs" in Pro. An issue was fixed in a previous version, but then the devs made a mistake and the issue re-appears in a newer version. I've seen that a handful of times.

Re: ArcGIS Pro 3.3.1- Exporting Join Creates NULL values in New Feature's Table

Paul_C_Anderson — Thu, 01 Aug 2024 22:49:57 GMT

I was just having a similar issue today- I joined a table to a feature class and was trying to save the result as my new working layer. I kept getting null values, or "0" values in one case. Weird thing was, after goofing around with it for an hour, I was able to get it completed successfully when I created a fresh project on my local drive, copied the layer and table to the new project and completed it all locally with no issues .

I have had other performance issues solved by moving everything to the local machine, but this would be suboptimal long term because I work a split in-office / remote schedule and use two different machines.

Re: ArcGIS Pro 3.3.1- Exporting Join Creates NULL values in New Feature's Table

AF2023 — Fri, 16 Aug 2024 10:43:05 GMT

Hi - I am also experiencing this issue for both 1 - 1 joins and 1 - many joins since updating ArcGIS pro. A workaround I have found for 1-1 joins is to perform a clip or intersect on the joined layer instead of exporting it.

Re: ArcGIS Pro 3.3.1- Exporting Join Creates NULL values in New Feature's Table

Bud — Fri, 16 Aug 2024 10:58:30 GMT

Have you reported the problem to Esri Support?

Re: ArcGIS Pro 3.3.1- Exporting Join Creates NULL values in New Feature's Table

JeremyLyman — Tue, 27 Aug 2024 16:02:25 GMT

I just experienced this today, except that it was exporting null records after I REMOVED the join from the features. I started poking around in the Export Features field map and found that it was not updating the expected fields when joins were added or removed. (not sure I've found any consistent behavior) But I think if I open the edit field window and reset the field map then it uses the current fields.