Joins in Pro 3.5.2 - more like 'We're standing in the vicinity of each other, but we don't know each other'

[RTPL_AU]

Is anyone finding Joins in Pro 3.5.2 just a bit off?  (not game for 3.5.3 yet) 

I am using FGDB feature classes and tables and the results I get from definition queries on layers I have joined just don't give me what I expect. 

Queries that I run in ArcMap on the same data with valid results, would just give no results in Pro and I'll have to figure out creative ways to make it work (without adding or editing attributes).

I don't think I've had it return incorrect results, just no results often enough that it bothers me enough to write this post.

Am I expecting too much from Pro for it to be able to do what we did in ArcMap? This line is a bit old now but really?

[Robert_LeClair]

@RTPL_AU - without seeing the data or the definition queries you're applying, it's difficult to troubleshoot this issue.  If you're able to share those details via an email/attachment, my email address is rleclair at esri dot com or you may consider logging a case with Esri Support Services and work directly with a support analyst.

[RTPL_AU]

Hi @Robert_LeClair 

Is there a reason that joins would act different in Pro compared to ArcMap?

Yesterday was the first time I decided to check the same data, same join, same filters/query in ArcMap compared to Pro 3.5.2 and it worked as expected in ArcMap.

In this case it was a monitoring site polygon dataset (about 90 sites) and a table of maintenance works. 
It was a 1 to 1 join with about 30% of the sites having a table entry; so nothing complicated or large.

A simple table.site_id IS NOT NULL gave zero results after the join.  table.site_id IS NULL gave the sites with matching records but I wanted to check something and also show the unmatched sites in the background. 

Doing exactly the same thing in ArcMap works as expected. 

This has happened every now then and due to data complexity I just thought it was the way I wrote the query etc and figured out another way. I can work on 5 projects a day, so taking the time to work out exactly what makes Pro get the hiccups is a pain. 

I also see it more often these days that the actual Join would fail. 
The Join will work in ArcMap (it was in used in a map I was trying to import to Pro a few weeks ago) and the same data exported to Excel would work with VLookup etc. 
Restart Pro and the Join will suddenly work again.  

It just feels flaky and prone to suffering glitches.  With the various known bugs in 3.5.x related to selections/queries/edits/etc who know what else is broken that could affect Joins when the wind blows and a scrub turkey walks past the window. 

[RTPL_AU]

@Robert_LeClair  The thing is - if you start your computer, open Pro, do a few small things, in general it works OK. 
Have it open in a project for a few hours while you edit various things (of course using single workspace editing due to edit visualisation bug and having to enable editing multiple times), work with symbology & labelling to get the right look, run queries to check against data emailed by client while you are working on the 'latest' version, etc and more often than not Pro will spit the dummy in some form. It will start running slow (more lag in UI than usual), joins will stop working, queries on joined data will give unexpected results, etc. 

The overall badness has been around since launch, a decade ago, so has ZERO to do with my data, pc, network, os, etc, as all of these have changed over time.  Every new version of Pro seems to fix one thing and break another so the exact nature of bugs & irritations have changed. 

The Join issue feels new (3.5.x cultivar so to speak).   

EDIT:
I skipped 3.4 due to specific bugs it had compared to 3.3.x, so my perception of issues starting with 3.5 might be affected accordingly.

[Robert_LeClair]

@RTPL_AU - at this point, I am not sure what assistance I can provide you as I do not work on the Esri Pro Development Team nor any of the Esri dev teams so cannot comment to the differences between versions and apps.  You may want to contact Esri Support Services and elevate the case to get the details you're seeking.  May be the best approach for the time being.

[jefferypickard]

Yeah, I’ve run into this too in Pro 3.5.2—joins just don’t behave as smoothly as they did in ArcMap. Some of my definition queries return nothing even though they should. I had a similar headache while testing data workflows for my pak game project, and exporting the join to a new table before running queries usually worked. Fingers crossed 3.5.3 handles this better.