Open para0056 opened 1 month ago
@para0056 , I agree, but I wouldn't expect that feature any time soon.
The resource schema doesn't even include the account name or its alias (#15), and that's just a simple 1:1 mapping.
The hierarchy of organizational units makes it more complex to model, especially given the limitations of the advanced query language.
One possible workaround:
accountId IN ('1111', '2222', '3333', ...)
It would be incredibly useful to be able to filter resource queries based on the Organization Unit of the account where the resource resides.