Forum Discussion
Solved
SetDataCells error: workflow settings do not allow input for Time member (not solved)
Hello again, it seems that the error was not completely corrected, so I have the same problem as my previous post.
Scenario 'Forecast 2023M10’s workflow settings do not allow input for Time memb...
You can trigger the DM job from the rule, there are examples scattered across these forums. You can also try triggering the Custom Calc directly from a button, I've not tested it.
I don't think you'll be able to use direct data-manipulation APIs from a dashboard extender for those periods, if the Dashboard is executed as a Workspace step in Workflow, because (as you've seen) the Workflow controls will kick in.
Edit: sorry, re-reading, you mean changing the Scenario property that defines the noinput periods? That might trigger even worse things and force you to reset the scenario, losing all data for that Scenario in the year. Big no-no.
Is a dashboard extender
JackLacava
OneStream Employee
OneStream EmployeeOk. Can you post your Scenario configuration too? Forecast scenarios are often set with Range frequency; I suspect you can't bypass that from Dashboard Extenders executed in a Workflow step, you might have to use a Custom Calc instead.
- JackLacava
Yeah that's what I thought. M9 falls into the "no input periods", so you can't write directly to it in a workflow context.
A workaround that I believe will work:
- Write your data to a temporary intersection in M10;
- trigger a Data Management job that will execute a Custom Calculation;
- Custom Calc will take the value from the M10 dummy intersection and copy it to M9;
- optionally you can then clear the dummy node, but tbh I'd leave it as it is to tally up things.
Note that this goes against the spirit of Workflow configurations, so from an auditing perspective it's not great - you're declaring in Scenario settings that workflows won't change previous periods, and then you do it anyway - but at least you should get some traces from the DM job (Custom Calcs often don't leave any trace).
Is there a way to change that noinput value in the BR?