Got Warning 003106 when rebuilding locator in Pro 3.3, but was fine in Pro 3.0.3

Question

I recently upgraded Pro from 3.0.3 to 3.3.2.  Now, right after upgrading, I am suddenly having a problem with rebuilding address locators.  The problem is that rebuilding takes 30 minutes; it used to take under 1 minute.  I got Warning 003106:

"The 'Point Address' dataset has a unique ID field mapped to the 'Address Join ID' role field. This join strategy is not optimal and may lead to degradation in performance and increased locator size."

I had not changed anything in the locator's configuration in the meantime.  The locator was working perfectly before this Pro upgrade.

Why is this happening??  I mean, why is the version of Pro causing this to happen now?  Is this a bug or a real problem with my locator?

AllenDailey1 · Answer

I kept digging into this and discovered that the warning was accurate - there really were unique ID fields mapped to all of the "join" role fields, for all of our address locators.  Yet no one had done it.  We do not even use alternate name tables for our address locators, which is what those fields are for.  My guess is that this happened automatically in the software somewhere between Pro 2.7/2.8 and 3.0, when Pro gained the capability to have locators with alternate name tables joined to them (we have had the same address locators since around Pro 2.8 or so).  And then the fields caused this warning to occur in 3.3.

Anyway, it looks like we will have to re-create all of our locators anew with Pro 3.3, because it is not possible to edit out the fields mapped to those join ID role fields, even though the documentation says the configurations are editable.

If anyone else is experiencing this situation, I'd be very interested to hear about it.  I'm curious if we are the only ones or not.

DanPatterson · Answer

3.4 Pro help topic which may differ from 3.0 003106: 'The '' dataset has a unique ID field mapped to the '' role field. This join strategy is not optimal and may lead to degradation in performance and increased locator size.—ArcGIS Pro | Documentation

JesseCloutier · Answer

Hi @AllenDailey1, we appreciate you sharing a potential bug with the broader Esri Community; however, Esri does not actively track software defects posted here. The official channel for investigating and validating bugs is Esri Technical Support. All customers experiencing a potential software bug should leverage technical support to report and investigate the issue.

By reporting bugs through technical support, Esri can better track the scope and impact of the issue across all our customers and better prioritize it with our product teams. Our teams can also investigate the issue more thoroughly to see if there is a solution, workaround, or patch to get you back up and running as soon as possible.

As a reminder, Esri Community is primarily a self-service support platform where Esri users can ask or answer each other’s questions, share feature requests, and collaborate to solve problems with GIS.

*Note that this is a scripted message prompted when posts allude to a potential product bug.