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
FdxExecuteCubeView parameters
If I build a cubeview that contains the desired POV and functions on its own, using FdxExecuteCubeView seems to work great. However, there is no documentation available on actually using the FDX func...
You're not missing anything obvious, it's the documentation that's missing...
From some internal resources, i see a comment like this over all the "filter" parameters of FdxExecuteCubeView:
'when the extracted cube view references an entity parameter called |!FDXEntity!|, this field needs to be set to the name of the entity dimension the extracted entities exist in 'if the cube view does not use an entity parameter called |!FDXEntity!| then this field can be left blank "" or as String.Empty Dim entityDimName As String = args.NameValuePairs.XFGetValue("", String.Empty) 'when the extracted cube view references an entity parameter called |!FDXEntity!|, this field needs to be set to an entity member filter that controls the extracted entities based on the member filter 'if the cube view does not use an entity parameter called |!FDXEntity!| then this field can be left blank "" or as String.Empty Dim entityMemFilter As String = args.NameValuePairs.XFGetValue("", String.Empty) 'when the extracted cube view references an scenario parameter called |!FDXScenario!|, this field needs to be set to the name of the scenario dimension the extracted scenarios exist in 'if the cube view does not use a scenario parameter called |!FDXScenario!| then this field can be left blank "" or as String.Empty Dim scenarioDimName As String = args.NameValuePairs.XFGetValue("", String.Empty) 'when the extracted cube view references a scenario parameter called |!FDXScenario!|, this field needs to be set to an scenario member filter that controls the extracted scenarios based on the member filter 'if the cube view does not use a scenario parameter called |!FDXScenario!| then this field can be left blank "" or as String.Empty Dim scenarioMemFilter As String = args.NameValuePairs.XFGetValue("", String.Empty) 'when the extracted cube view references a time parameter called |!FDXTime!|, this field needs to be set to a time member filter that controls the extracted time periods based on the member filter 'if the cube view does not use a time parameter called |!FDXTime!| then this field can be left blank "" or as String.Empty Dim timeMemFilter As String = args.NameValuePairs.XFGetValue("", String.Empty)So I assume those fields do nothing unless those Parameters are present on the cube view.
JackLacava
OneStream Employee
OneStream EmployeeNo, it's the same for FDXScenario. I expect it's because that, if you use the parameter, the cube view gets both dimension and member filter from the parameter itself. I suspect your troubles might come from not having "E#" in the filter...?
Hm, mixed results. If I use |!FDXEntity!| in a row, it fails, If I use it in the POV, it succeeds. I don't know why that would be (beyond "it's a data unit thing") but I think I read that the FDX function will intelligently run a separate CV query for every member in the filter and then append all the results into a single dataset. I'll have to do a row count on the output of each method to see if they're really the same.
I do see why it's referenced twice in the documentation though. The cube view can take an entity filter without needing to specify the entity dimension but the FDX function cannot. So, for FDXEntity to produce a value, both entityDimName and entityMemFilter have to specified. It was two requirements but only produces the member filter as output.
At first I thought it was failing but my row counts are now lining up. I'm going to push it back on the business side to provide historical data I can compare against.
I also want to figure out how to pass arbitrary name/value pairs "the right way" (presumably with nvbParams) but that can wait.