Contributor

Re: Time Dimension - date


@rob_marshall wrote:

@kavinkumar ,

 

From the original attachment, I believe the data was at the day level, thus start() would work great.

 

Thanks,

 

Rob


yes! start() formula also worked :) thanks

Highlighted
Contributor

Re: Time Dimension - date

Yes, the long formula worked. I needed a "per day" date in my line item that's why I didn't used Start () or end () and used the long formula instead. Thanks everyone for the help :)


@kavinkumar wrote:
Hi @david,

The above formula that you mentioned will work only to return 1st and last day of the month. But here the requirement is to get each date across the Time period.

@sarahcorrect me if I am wrong!!
Thanks,
Kavin.

 

Contributor

Re: Time Dimension - date

Another question re TIME DIMENSION. I have this encounter on calculation of working days, when I created a module with PERIOD as line item, the "count" line item formula produces result, whereas, if i use PERIOD as a TIME DIMENSION, the "count" formula in my line item does not produce any correct result. Do you know why if I use a time dimension, the formula should have a different approach?
Community Boss

Re: Time Dimension - date

@sarah.esguerra 

Could you post some screen shots of the modules and line items.  It would help to understand the detail more fully

Thanks

David

Contributor

Re: Time Dimension - date

Hi @DavidSmith attached is the screenshot, thank you :)

Community Boss

Re: Time Dimension - date

@sarah.esguerra ,

 

You have a couple of things going on in here.  First, the formula.  Start() is resolving the date that you are currently looking at, in this case Jan 19.  So, in this case, what the formula is saying, if 1/1/19 is greater than 3/4/2019 and 1/31/2019 is less than 3/8/2019 then get the working days count from the Calendar module.

 

So, a couple of issues:  One, Jan 1st is not greater than 3/4/2019 while Jan 31st is less than 3/8/2019.  In using the AND, this will not resolve to a true.  Second issue: your Count module is at the day level while the Deadline module is at the Month level, the number that will be returned will be at the Month level (so not the highlighted values you have in the doc).

 

Hope this helps,

 

Rob

Community Boss

Re: Time Dimension - date

Can you explain exactly what the use case and what you are trying to achieve?

you seem to have a time vs time construct, so it would be useful to know what you are expecting to see; that will hepl define the solution

David

Contributor

Re: Time Dimension - date

Hi @DavidSmith here you go, hope this helps for you to understand my question better :) 

Thank you!

Community Boss

Re: Time Dimension - date

@sarah.esguerra 

Yes, thanks, that was the missing piece

As ever I think the solution is quite simple

Your holiday calendar is perfect; you were almost there, and with an extra line item we can solve it2019-03-08_12-31-42.png

I've created two alternatives for the cumulative calculation  If you timescale is large, the alternative one is more efficient

But the line item formulae are:

Cumulate WDs = CUMULATE(Working Day Count)

Alternate Cumulate WD = Working Day Count + PREVIOUS(Alternate Cumulate WD)

Then in your target module you lookup the running total for the Due Date and subtract the running total from the Submit Date

Excuse my date format, but I'm based in the UK!!

2019-03-08_12-35-14.png

One question I did have and I've assumed it above is that you do need to different dates per month.  If that is not the case you can removed the time dimension from the module entirely, as below2019-03-08_12-42-48.pngI hope that solves it for you

David