Second TableView won't work. it will combine and prompt all TableView Parameters at once. using a separate cube view connection only for parameters solved my issue.
Sure. You just reference Param_1 in the configuration of Param_2, with the standard syntax (i.e. |!Param_1!| ).
Hello Jack, it is not working like this in the Table view case.
Here is the code below for your reference,
1) Table view BR where I'm calling these Parameters.
2) Definition of Parameters.
3) XFBR Business rule used in Parameters.
4) The Result I'm getting (Error)
The second Parameter is not going to XFBR only when I'm passing the first Parameter in it. If I pass a fixed value instead of a Parameter, it is working
Ok, I see. Yes, the issue is likely due to the fact that we don't do multiple resolution rounds in TableViews; so the Input dialog will show the XFBR unresolved. After you click ok, though, the XFBR is actually triggered correctly with the passed parameter (or at least it is in v8.1 that I tested it on, on an Input or Literal parameter).
So you can have a Parameter relying on another Parameter, but (at the moment, in Table Views) they cannot both be things the user will interact with. If the second parameter was a simpler Input or Literal, things would work: the user would be prompted for the first Parameter only (or both, but the second would show the xfbr unresolved), and the Table View code would receive the second Parameter resolved correctly too.
You can raise this with Support and see what they say, I would expect something might have already been filed about this but maybe not.
Jack, thank you for the clarification, yeah will take this to the support and let you know as well if anything comes up.
