The OneStream Community is temporarily frozen until June 29th due to the ongoing maintenance. Please read the blog post here to learn more.
Forum Discussion
Solved
Parameter Value Not Resolved
I have an issue that I have seen before I never figured out so want to see if others have encountered this and figure out what I am doing wrong. I have a data adapter that calls a Dashboard Dataset ...
It is related to the processing order of the components, data adapters, and parameters. In your case, the parameter „someotherparameter“ is needed to build the data adapter, but it doesn’t exist yet. And the query fails.
The solution is easy, you just need to test, if the parameter already exists, and exit the business rule if not.
I‘m not at my desk, so I can‘t post a sample.
ChristianW
OneStream Employee
OneStream EmployeeIt is related to the processing order of the components, data adapters, and parameters. In your case, the parameter „someotherparameter“ is needed to build the data adapter, but it doesn’t exist yet. And the query fails.
The solution is easy, you just need to test, if the parameter already exists, and exit the business rule if not.
I‘m not at my desk, so I can‘t post a sample.
I agree with Christian, sometimes a data adapter (or other object) is triggered multiple times, if your parameter is not resolved yet it will be returned in its original name (|!name!|). to test this run a brapi that writes your parameter to the errorlog and you should see it more then once, first as the |! !| and then the updated one with the required content. As a solution you could exit your function if your parameter contains |!.
so just add
If sParameter.XFContainsIgnoreCase("|!") then return nothing