This content has been marked as final. Show 3 replies
but seems it has to do something with GTT data hodling capability to the session level.
Try creating GTT with PRESERVE ROWS or ON ROLLBACK DELETE ROWS.
seems the session which populates GTT is different from the session which selects data from it so data gets deleted even before the table is accessed.
Please mark if it helped.
Thanks user2534719 for the response. Yes I think that may be the issue. THe requirement is to "NOT TO" run that report until all 5 parameters are selected in the prompt and all 5 presentation variables have the data.
Any other suggestions.
If you are using a GTT, you need to run the function which populates the GTT before OBI server executes the select query on that table.
In your case, the OBI server is executing the select query from the table before the data is populated in the table.
In order to force the BI server to run the query after the GTT is populated, you need to specify the condition in the connection pool settings under the connection scripts tab.
In the execute before query, enter your physical query which runs the function to populate the GTT.
Hope this helps !