OneStream EmployeeIn your example, the Scenario name determines "current year". Your XFBR idea will work for that. But what if your scenario name doesn't contain an indicator of "current year"? You can anchor on WF Time, Global POV Time or POV Time.
Will the job be scheduled? If so, they system won't have a POV Time or WF Time so you can't use those. If the admin isn't diligent about updating the Global POV, then the extract won't contain the data you're expecting.
Will the job be triggered by a user from a dashboard? If so, you can pass that parameter into the step's Time Filter.
Once you determine the logic for what determines "current year", you have options to make the job dynamic.
Hi, the scenario also has to be determined dynamically, which I should have included too. Yes, this job will be scheduled as the exports have to go out automatically on a scheduled basis. You have perfectly explained the issue here that I can't leverage POV time or WF Time. Global POV seems to be the answer for the Time filter if the admin is going to properly maintain it. But the Scenario can't be maintained through the Global POV as I am exporting data from multiple scenarios.
Currently it looks like XFBR would be the ideal option, but I can't find any examples or proper documents to implement it.
