Linked object drill-downs
The below example shows the user experience of ecommerce org using external objects for orders and products.
An ecommerce company use Salesforce to record sales to the standard objects Accounts and Contacts. However, due to the nature of its products, order are contained in a large dataset that's too large to be stored on-platform. Orders and product details are stored off-platform in a cloud data warehouse, Snowflake.
With Omnata the architect can link objects where Orders is the child of Accounts, linked by the Account ID. This allows users to natively drill-down from on-platform to off-platform objects.
Continuing on the same use case, product details will become the second level in the drill-down. The architect can make the Product Details object the child of the Orders object, linked by a Product ID.
Users can now natively drill down from Accounts to Orders to Product Details and back up again.
Moving over to the repairs department, they are using external objects differently. The standard object Cases are used to manage the repair lifecycle for customers. In this case, Product Details recorded by the item's serial number is stored off-platform and is the parent of Case and Case Comments.
Users can drill-down from a product to all of the cases and comments for that product and back up again.