Logical SQL is not recommended?
SummaryIf Logical SQL isn't the answer what is the recommended approach?
I've been told through a recent Technical SR that Logical SQL is not a recommended approach to building analyses in OTBI.
While I agree that using the subject areas as designed is best, I've found that there are cases where logical SQL seems unavoidable. The example that was being refuted through the SR was trying to connect "Human Capital Management - Transaction Administration Real Time" to "Workforce Goals - Goal Plan Assignments Real Time". I don't believe there's a way to have an analysis show information about the goal plan and derive the current task the assigned to the worker in goal setting without Logical SQL.