Isn't this working?
My issue is that Col1 and Col2 wouldn't always be a static scenario/UD4. Based on how far along the fiscal year has gone then columns would move from forecast to actual.
My current solution is to build column templates where the user would have to select a parameter for last completed month and that parameter would select the correct column template. The column template would be pre-built to reflect Col1 as actual and Col2 as forecast and so on.
Hi Carlos_S: maybe the missing piece is that parameters you might need? I'm not sure how your UD4 fits in, but the solution Christian proposed is exactly what we use and it works great.
To help reinforce his proposal, here is how we implemented it:
Here are our components (very similar to what Christian listed):
And here is what it looks like what a user makes a selection for 'Month-End Close Period' (our |!Select_Time_Close!|)
When selecting 2022M5
When selecting 2022M6
You'll notice how the periods (and formatting) dynamically move with the time period selection. Hope this helps and would encourage that you give ChristianW proposal a try. Cheers! -db
Thank you, I'll give it a try.
