nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Advice needed on how to manage 2 reporting periods in a Board application

Aleksandar

Hi everyone,

We have the following situation. Our client has multiple companies, 2 companies have the reporting period from February until January, and the 3rd company has a regular reporting period, from January until December.

Currently, we set up 2 Timelines (entity called Cluster Timeline) and it appears in the master data hierarchy.

https://support.board.com/servlet/rtaImage?refid=0EMVj00000JFOBy

Because of these 2 timelines, we have additional Time entities (ST means Jan-Dec timeline, SV or no suffix means Feb - Jan).

https://support.board.com/servlet/rtaImage?refid=0EMVj00000JFNpO

And we have a regular entity called Time Period that is basically used as a generic Year entity and is present in most cubes and used in selections.

Is there any advice you can share with us on how to improve the current situation?

Find more posts tagged with

Data Modeling

Time range

Accepted answers

All comments

Robert Barkaway

Hi Aleksandar, those images you've posted are showing as Not Available for some reason, would you be able to repost them please so I can see what your current setup is?

Aleksandar

Seams I can't add images because of a permission problem. I added the image link above the images. Hope at least that works. And thanks a lot for the help!

Miran Saric

Hi Aleksandar, Miran with the Board Community team here. You should now be able to upload images, but let me know if you're still running into any problems. Thanks!

Aleksandar

Thanks a lot Miran!

Here's the master data tree:

And here are the Time range entities:

Aleksandar

@Robert Barkaway yes, that's correct

Robert Barkaway

Okay, what challenges, if any, are you encountering doing it that way? Managing multiple calendars like that is always a bit of a pain I know but it sounds like you have a working solution?

Aleksandar

This is currently working for us, however, if users want to view data on the quarterly or annual level, we can only build that if we built 2 screens with different calendars (one for Jan - Dec, other for Feb - Jan). Maybe I'm wrong here

Robert Barkaway

The only real alternative would probably be to map to a separate standalone date structure where you could map the two data sets to a common date hierarchy by reporting quarter and reporting year, mapping the respective months as appropriate. However you wouldn't then be able to use the inbuilt date calculations, they would be able to drill back to the main calendar if you kept that dimensionality in there though.