Oracle Communities

Oracle Analytics and AI

Child Item

Can you reference other parameters in the initial value's logical SQL?

For our projects report, we'd like to create a project manager parameter where we set the the project manage equal to the display name so that when project managers access the report they see only their projects. To do this, we would like to use the out of the box display name parameter.

In the above example, the logical SQL validates, however when we go to click okay we get an error about mismatch with an integer, even though we have the data type set to text and the logical SQL is also text data type.

How can we properly reference a parameter in a parameter?

Find more posts tagged with

Report

Parameter

Analysis and Data Visualization

Fusion AI Data Platform

Accepted answers

David Saggioro

Hi @Caroline Blanchard,

One thing you can do is drag and drop the Project Manager field to the filter and hide it, and then bind it to the system parameter (Display Name). It should assign it by default so once visualization is opened, it will already select the data based on the project manager selected behind the scenes with the hidden parameter.

Let me know if that works. I've tried a similar scenario myself and it worked.

Thanks, David

All comments

David Saggioro

Hi @Caroline Blanchard,

Let me know if that works. I've tried a similar scenario myself and it worked.

Thanks, David

Cade Johnston

@David Saggioro That worked for us! Thank you so much!

David Saggioro

I'm glad it worked @Cade Johnston !

Caroline Blanchard

Hi @David Saggioro! This use of the binding parameters works to get the right selection into the filter, however strangely no data shows when its used.

After binding the parameter, the person display name is properly selected, but it doesn't work to filter the table, and all other names in the list no longer show. Any suggestion on how you got it to work in your instance?

David Saggioro

Hi @Caroline Blanchard,

I guess the filter won't show other values since it is based on the parameter, which holds only one possible value (the active user in the session). So that seems to be the expected behavior.

As to the fact that no data is displayed, is the format of the person name the same as what is expected to be on the table for the Project Manager field you are trying to filter? I do not use FDI with HCM so I did it with a different field, set with a default value on a parameter and binding it to the filter. You can try with the user name (which normally displays the e-mail) and compare it to a field where e-mail is saved, to validate that the match is working.

Thanks, David