Forum Discussion
Solved
incorrect scenario running scheduled job using WFScenario parameter
Currently, we have a manual process that involves a user running a Load and Transform that uses a data source with a DM Sequence as its source. That sequence uses the |WFScenario| parameter.
This a...
Alright, si.PovDataCellPk still failed but it did inspire me to check other parts of si and this solves the problem:
si.WorkflowClusterPk.ScenarioKey = BRApi.Finance.Members.GetMemberId(si,DimTypeId.Scenario,scenario) si.WorkflowClusterPk.TimeKey = BRApi.Finance.Time.GetIdFromName(si,year) si.WorkflowClusterPk.ProfileKey = BRApi.Workflow.Metadata.GetProfile(si,wfName).UniqueIDThe profile key override isn't strictly necessary for the export/import part of this but there's additional downstream code that looks at the staged results and for that the WF key is relevant. I've shipped this off to my users for testing but it appears to be good for now.
JackLacava
OneStream Employee
OneStream EmployeeIf you're triggering this from a rule, you could try setting the POV by manipulating the SessionInfo object, changing si.PovDataCellPk.
To be honest, I'm not entirely sure how you're executing things. Could you post your Sequence and Steps definition maybe...?
Alright, si.PovDataCellPk still failed but it did inspire me to check other parts of si and this solves the problem:
si.WorkflowClusterPk.ScenarioKey = BRApi.Finance.Members.GetMemberId(si,DimTypeId.Scenario,scenario) si.WorkflowClusterPk.TimeKey = BRApi.Finance.Time.GetIdFromName(si,year) si.WorkflowClusterPk.ProfileKey = BRApi.Workflow.Metadata.GetProfile(si,wfName).UniqueIDThe profile key override isn't strictly necessary for the export/import part of this but there's additional downstream code that looks at the staged results and for that the WF key is relevant. I've shipped this off to my users for testing but it appears to be good for now.
Just randomly came across this thread. I wonder if it would be safer to override the whole workflowcusterPK. E.g.,
Dim wfClusterPK As WorkflowUnitClusterPk = brapi.Workflow.General.GetWorkflowUnitClusterPk(si,wfName,scenario,year) si.WorkflowClusterPk = wfClusterPK
There are two DM sequences. One is the export that is the source of the data for the data source. The second is just used to schedule/execute the workflow.
The scheduled sequence accepts a parameter, Scenario=BudgetFinal, to determine what scenario to use for the trigger file name for and to run the harvest API call. The data export sequence is just set to use |WFScenario| and I would expect that a workflow currently importing for BudgetFinal would also cause |WFScenario| to be BudgetFinal. It's not.
However, I've never attempted to manipulate the si object so that seems worth a try.
