Oracle Transactional Business Intelligence Idea Lab

Home› Oracle Analytics› Oracle Analytics Idea Labs› More Solutions Idea Labs› Oracle Transactional Business Intelligence Idea Lab

Categories

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

Enable vice-versa Standard-Custom Object (1:M) searching in Workspace

Submitted
11
Views
1
Comments
Gerald Feudo
Gerald Feudo Rank 1 - Community Starter
edited September 2024 in Oracle Transactional Business Intelligence Idea Lab

We've currently implemented a relationship between a Standard-Custom object via DCL, Custom object records is tagging a record from the standard object (Account). Searching a custom object record in the custom object workspace using an account filter would work, however searching an account in account workspace using any of the custom object field is not possible unless we'll build a relationship via reference Customer-Standard object but cardinality can only be 1:1 or 1:M picking any wouldn't follow the same relationship as the original and would cause conflicting logic.

Tagged:
1
Up
1 votes

Submitted · Last Updated

Comments

  • Gerald Feudo
    Gerald Feudo Rank 1 - Community Starter

    Posted the idea in sales and fusion service as this was incorrectly posted in "Oracle Analytics" idea lab