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

[DylanHinton]

 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

[SarahHurley1]

This is also what I am experiencing. Need to create a new project locally in order for it to work. 

[AF2023]

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. 

[Bud]

Have you reported the problem to Esri Support?

[KevinDicks]

Same issue here.  This is happening if I'm exporting non-joined data, or joined data.  Something has changed on this last ArcGIS Pro update.  

[KatherineMichael]

I also have this issue, currently with non-joined data. Trying to export a new table using a selection results in an output with completely null attributes, version 3.3.1.  I see there is another patch available, but every time I patch up to solve an issue I end up with another issue.  I just updated to 3.3.1 from 3.2.2 two weeks ago to try and fix an issue with text callouts not resizing or positioning normally.  I would just reinstall 2.9.5 but I've already up saved all my projects to 3.x and the thought of having to rebuild them all crushes my soul.  I guess I'll just install the 3.3.2 patch and see if that fixes it. 

[Paul_C_Anderson]

I've been installing new versions hoping to free myself of bugs since 9.2 lol.

[KatherineMichael]

Lol, that is the absolute truth. 

For what it is worth, the 3.3.2 patch appears to have worked. I followed the identical workflow with the same data and now have a new table with attributes intact. 

[AnnieD_WLP]

I had the same issue with exporting in ArcGIS Pro 3.3.1. I tried the Option setting "Use field types that are compatible with ArcGIS Pro 3.1 and earlier releases when adding query layers and text files" and it didn't work. I had to find another computer that is still in Pro 3.2 to get the job done properly. 

The Pro 3.3.2 did not resolve my issue. Pro 3.3.1 only had joined fields NULL, but Pro 3.3.2 had all fields 0 or NULL.

[KSter]

Just chiming in that I had the same issue. Upgrading from 3.3.1 to 3.3.2 fixed it, so thanks for mentioning that @KatherineMichael 

[AdrianaDelucchi]

This happens to me as well and is a bug I've identified if you do a join and export on a layer multiple times. The first time, the values of the join fields export properly, but if you remove the join and try to join and export again on the same layer, that's when the values aren't carried over and are replaced with NULL. The only way I have found around this to to open a new map, and put both your input layer and export layer in a new file geodatabase.