Re: data model design - facts / dimension - best practices
Looks like you are modeling facts revenue about a company
There are lots of ways you could do this and it depends what you are lookng to achieve.
Start by seperating your data into dimensions and facts.
In the fact table you might have
adding a fact type will allow you to grown your model as you bring in more facts about your company.
In the Company table you might have
State, Type and flag im unsure if these are related to the company or the revenue you might discover other dimensions you need to report on as you investigate further.
For the user manipulation let Qlik create a calendar on your revenue date and the users can fliter to their hearts content on months, quarters, years etc... manipulating the date load is the wrong place for users to get invlovd unless you have a data size/business constraint that means you can only report x number of years of revenue.
If you need to control the user interaction more then your getting into variables and extensions but problably not need yet.