How to work with relationships on Enterprise?

[CeniltonMatosFonseca]

Hello, everyone. I hope you're doing well!

I would like to know how you handle data and its relationships in the Enterprise environment. I need a relationship that I created in an Oracle database, but when I upload it to the Portal, the relationship does not work.

When using "Join Features" in the Classic Map Viewer, it creates a new hosted layer. However, when I update my database, this layer does not update.

How do you usually handle situations like this? And what about cases with multiple relationships?

[DavidSolari]

The only reliable way to relate data in ArcGIS is with Relationship Classes, which requires referenced data published from a registered EGDB or a hosted layer created from any geodatabase. Add all the layers/tables that participate in the relationship to your map when you publish a service and you'll see relationship info once you add the service into a map.

[CeniltonMatosFonseca]

Hello, David!

I created the relationship, and it is visible in a version of ArcGIS Desktop connected to the Oracle database.

However, when publishing, the table and the layer from the project that are related in the database do not behave the same way in the Enterprise. They are uploaded separately.

This has been the biggest challenge.

[DavidSolari]

When you add the feature service you published back into Pro, are you able to select related records, add them to popups etc. etc.? If so you might want to post a screenshot or mockup of what you're trying to accomplish, you might be using the wrong tool here.