Select to view content in your preferred language

Join to unregistered database view is one-to-first instead of one-to-many

151
3
Jump to solution
3 weeks ago
Bud
by
Esteemed Contributor

ArcGIS Pro 2.9.5; Oracle 18c 10.7.1 enterprise geodatabase

I have a ROADS line FC and an EVENTS standalone table. The relationship of the underlying data is one-to-many: one road to many events. No relationship class. Both registered with the geodatabase.

If I use the Add Join tool to create a join from ROADS to EVENTS, the join’s relationship will be one-to-many. That works as expected.

However, if I create a database view (not registered with the geodatabase) on EVENTS called EVENTS_VW [SELECT * FROM EVENTS], and join from ROADS to EVENTS_VW, then the relationship of the join is one-to-first, not one-to-many. That’s not expected.

The Add Join documentation says the data needs to have OBJECTIDs and needs to be located in the same workspace (same geodatabase) in order for a one-to-many join to be automatically created. The database view meets those requirements. So why does the view behave differently from the standalone table?

(I don’t want to register the view with the geodatabase because that makes it too difficult to make changes to the view in the future. I’d need to delete the view, recreate the view, reregister the view with the GDB, and re-do all the database privileges. That’s not a good use of time.)

0 Kudos
1 Solution

Accepted Solutions
Bud
by
Esteemed Contributor

BUG-000173762: In ArcGIS Pro, the Add join tool creates a one-to-one join when the join is created between a Feature class and an unregistered view, even when one-to-many cardinality exists between the data.

View solution in original post

0 Kudos
3 Replies
Bud
by
Esteemed Contributor

Esri Case #03793532 - Join to database view is one-to-first instead of one-to-many

From Support:

We are in the process of collecting a few logs that need to be submitted with the bug, I will keep you posted when it's logged.

Also while testing we have found a potential workaround for this issue:
If you navigate the view using the Browse option > even the unregistered view will create one to many join.

Bud_0-1737469751549.png
Bud_1-1737469804135.png

 



 

 

0 Kudos
DanPatterson
MVP Esteemed Contributor

Add Join (Data Management)—ArcGIS Pro | Documentation for 2.9

Add Join (Data Management)—ArcGIS Pro | Documentation for 3.4

make sure you are using the appropriate help version as well, there can be significant differences and issues raised since previous versions.

 

 


... sort of retired...
0 Kudos
Bud
by
Esteemed Contributor

BUG-000173762: In ArcGIS Pro, the Add join tool creates a one-to-one join when the join is created between a Feature class and an unregistered view, even when one-to-many cardinality exists between the data.

0 Kudos