We are getting inconsistent behavior trying to use Session Variables in Datasets Expression Filters.
Anyone have success?
So… If I remove the space before and after equal sign it works
Hi Wayne,
How did you get the first one to parse in the first place? In all test cases I tried it is shown as unsupported.
Hi,
I never managed to get a valid validation, always got the "Invalid Expression. Session variables are not supported".
And I tried a number of times…
@Christian Berg-0racle - got lucky. I can get you in a zoom call to show you. First one was done by one of my colleagues and he nor I cannot replicate (my second screen cap) in different dataset.
His first one actually works which is great.
Interesting… We were able to copy the reference to Session Variable out of working into different Dataset and it Validated.
Now I'm curious: when it validate, does it work as expected?
Because if it does, I'm very much curious to know why the not-validating message is that the session variables are not supported there.
"His first one actually works which is great."
No it's not it's rather extremely preoccupying 🤣 I'll try to use the copy+paste approach in a sample.
Update: It works when you write it without any space. h/t to @Gianni Ceresa
Imagine how great it would be if we could still see the raw object definition to find out just how that JSON is written and what the interface tries to write today…
Thanks Wayne for the 'space' hint, that is the key to get it validated.
The fun thing is that the validation error doesn't come from the backend, it's a front-end limitation.
With a space after the '=' the front-end javascript doesn't even send a request to /ui/dv/ui/api/v1/queryvalidation/wheresto check for validation, it does display the error directly. I'm quite sure that if I send a validation request to that URL (it's a POST call to that URL) with the space, it will probably return result: 'pass'as well.
/ui/dv/ui/api/v1/queryvalidation/wheres
result: 'pass'
Therefore, I would say it's a bug: a front-end javascript check isn't aligned with the back-end check.
And confirmed!
/ui/dv/ui/api/v1/queryvalidation/whereswill happily validate the usage of a session variable there, even spaces around the = .
It's really just the front-end blocking the validation, and not even sending the async call to the back-end for it.
Learn how to deploy an AI Data Platform agent, register it to the AI Registry, and introduce it to business users through Agent Hub. This session covers how to prepare an agent for deployment, configure endpoint access and authentication, invoke a deployed agent, and monitor it after deployment. The session also introduces…
Can you please help resolve this error. WebLogic version is 12c. OAS is 6.4
So I have an action passing a value to another workbook. On the other workbook, I have an expression filter and a parameter I created and it does not seem to work. Any ideas. See the images
We know you can directly export workbooks and folders from within OAC, and we know you can migrate OAC content using the FDI Content bundle. However, it's unclear what settings or steps are required in order to ensure any calculations in "Shared Objects" still carry over. When making a .dva artifact export from OAC for…
The user icon in the upper-right corner of OAC (DV) is displaying more menu options for our non-admin users than we wish to display. We would like to restrict these to only "Profile" and "Sign Out" for regular users. Is there a way to customize these menu items? Especially if we can control this via security, that would be…
What is wrong with this code