DIM_DATE Calendar Issue

[FLPylot]

I have gotten myself confused on bringing in a DIM_DATE table from DB2. Everything seems to tie in fine but the report writers are seeing issues when they try to use the current date against the DIM_DATE to get data for previous quarters, months, etc. Do I need to do something additional in FM to give them this functionality or is it a Report Studio function I am missing?

I have attached my dimension for your review.

[bdbits]

Everything seems to tie in fine but the report writers are seeing issues when they try to use the current date against the DIM_DATE to get data for previous quarters, months, etc.

It might help if you tell us what "issues" they are having.

[FLPylot]

When the report users try to pull in previous quarter to retrieve data, it will bring in only the current data or the current quarter data. Something we are doing does not allow the report to understand that, based on current date, we want to get the previous quarters data.

I apologize if this seems like a dumb question. I am fairly new to this version of FM.

[MFGF]

When the report users try to pull in previous quarter to retrieve data, it will bring in only the current data or the current quarter data. Something we are doing does not allow the report to understand that, based on current date, we want to get the previous quarters data.

I apologize if this seems like a dumb question. I am fairly new to this version of FM.

Hi,

I don't see current date or DIM_DATE in your dimension. How are these modelled? Where are they coming from? PREV_QTR appears to be just a quarter number, ranging from 1 to 4. When users bring this in, all they would see is that number? Can you explain how you have modelled things in FM and give us more accurate details on what your users are trying to achieve vs what they actually see?

MF.

[khandfw]

Just to confirm, your table date is joined to he dimdate.dateid and they are filtering dimdate.quarter,-1?

Sent from my Nexus 6P using Tapatalk