Time dimension in SSAS - time

I am trying to understand Time dimension is SSAS.
In SSAS we have an option to create Time dimension. I have two questions related to it
What difference it makes if i generate, Regular calendar, Fiscal
calendar, Manufacturing Calendar or ISO 8601 Calendar?
Once the dimension is created, is it possible to update it. Let
say i generated it for the range of 1 Jan 2012 to 31 DEC 2012 and
now i want to increase it to 31 Jan 2013 is it possible.
Thanks in advance.

I don't know the answer to #1, but to #2, yes, you will be able to extend the range of your time dimension after it is created.

Related

What is the timestamp unit of an exported TwinCAT Scope measurement?

I took some measurements with TwinCAT Scope and exported the results as a CSV. The measurement series started at 17 August 2022 at 10:32:25.290 which has timestamp 133051987452906875. This is not UNIX time, because that time would correspond to 1660725145. Adding some miliseconds would add some zeros at the end.
So what is the unit of the TwinCAT timestamp?
The same time format is also used at more places. For example in ADS. From the C++ ADS library I found that the unit is
the number of 100-nanosecond intervals since January 1, 1601 (UTC)

How to create Period-Over-Period Insight To Display Last Two Completed Periods

In Amazon Quicksight, you have the ability to create a "Period over Period" insight. This would, for example, show "Sales increase 10% from January 2020 to February 2020.
However, it seems that the "current" period is not configurable and always takes on the period a user would find themselves in. This means that the statistic is a little misleading since on January 2nd, it might say "Sales decreased 89% from December 2019 to January 2020". While true, it's not apples to apples since January isn't finished yet.
Is there a way to have it compare the last two completed periods? For example, if January 2nd, it would compare November vs December?
You should check on the following for the answer:
amazon quicksights compare time periods
Basically, if you want to calculate the 'price' (amount), then use the runningSum(sum()), and if it is a count of users, then use runningSum(count()).
runningSum(sum({sale price}),[truncDate("MM",{saleDate}) ASC], [truncDate("YYYY",{saleDate}])

DAX Query ( Using FIlter and MAX function ), calculate Total Sales for the last running 30 days

I am new to DAX and encountered a measure as below,
30 Day Running Total = CALCULATE([Total Sales],
FILTER (ALL (Dates), Dates[Date]>(Dates[Date]) -30 && Dates[Date] <= (Dates[Date] )))
i.e. to calculate Total Sales for last 30 days in a cumulative way for the data from 1st January 2018 to 30 December 2021, the above measure i am not able to understand
My understanding is as below, please let me know where I am moving in wrong direction
FILTER ( ALL(Dates) -> Removes all filters means take date from minimum to maximum from the complete table and i.e. between 1st January 2018 till 30-december-2021
Dates[Date]>MAX(Dates[Date]) -30 -> "Takes Total Sales from the current row in table minus 30 days".
For example if the DAX calculation is on 30th January 2018 then it considers all the total sales from 1st January 2018 till 30th January 2018
Then why do we need to mention another filter Dates[Date] <= MAX(Dates[Date] )?
Thanks in advance for your time
Regards
Sumit Malik
Sumit your main concern seem to be Point (3)
why do we need to mention another filter Dates[Date] <= MAX(Dates[Date] )?
Your doubt is correct, if the data is clean, you do not need to define that upper-bound filter because theoretically considering sales from 30 days ago, there should not be sales after today.
Unfortunately, often data is dirty and there might be Sales in the future. Therefore, defining an upper-bound is a best-practice to avoid this kind of dirty data issues. Remember that in software engineering you program thinking the worst-case scenario, therefore, defining an upper bound does not harm :)

Forecast period starting earlier than defined

My dataset has multiple variables and I am using TSModel for forecasting. I have data till December 2017 but a lot of them are either 0 or missing. During the forecast, it is starting the forecast from July 2015 onwards whereas it should actually start from January 2018.
Can someone help with what might have gone wrong?
If for a particular series all values after a given date are missing, then the estimation period for that series ends at the last observed value's date, and the beginning of the forecast period is the next date.

How to add a simple calendar to my windows store app

I'm working on a Universal windows store app and I want to add a simple calendar so that users can add birthdays of their friends and save them and some other stuff. Is there any simple way to do this?
PS: Using Visual Studio 2013
What I do understand about Calendars, is there are fourteen of them in total that are possible - seven for each day of the week a normal year begins on, and seven more for leap years. You may have to create all fourteen and put them in somehow. There is instead a formula for working out what day of the year anyone was born on by their date of birth, and formulae can be programmed into r or other programmes using perhaps the for loop, or if command. This formula is :
{4(d+y)+x-4c}/28, where d is what number day of the year it is - so Jan 1st, d=1, and so on, but for Leap Years it gets different from Feb 29, y is the year in question, x the closest year before y divisible by four, and c an era constant. For modern dates, c=0, so no worries, but if You go back before September, 1752, it changes, as this is when the British went from the Julian to the Gregorian, while in Catholic Europe it was October, 1582, but these are only a concern if You are into such historical dates. For those, c=1, but may have different values much earlier - if You want to know more, reply to this, and I will get out what I have written on it.
For example, if one was born on 17th May, 1979, you would go :
{4(137+1979)+1976-4 times zero}/28, which equals 372 plus six sevenths - you ignore the whole number, and look at how many sevenths there are. Six means Thursday, and thus the 17th May, 1979 was a Thursday. This is it in short - for more details, if this interests, feel free.
The simple way is in use third-party controls like Telerik Calendar or something free like this one.

Resources