Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
ashishkalia
Partner - Creator
Partner - Creator

Master Calendar without transaction dates

Dear Qlikers,

We are going to implement HR module at one client.

The scenario is, We are having Employee information like Date Of Joining, Date of Leaving, Dept and other information related to the employee.

Now we don't have any transaction date field related to employees and reports to be created are like below:

  • Monthly>Yearly Hiring/Leaving trends
  • Monthly Strength/headcount
  • Yearly Strength/Head Count
  • Headcount, Employees about to retire in next N months.

Need your advice and suggestions on how to build a data model in Qliksense so that we can work with calendar flexibility

Many Thanks in advance..........

3 Replies
Anil_Babu_Samineni

I think you need 2 master calendar here. Because, you don't have transaction date. Create one calendar for DOJ and other is for DOL

Please add me Anil_Babu_Samineni to interact faster when reply back. Speak low think High.

Before develop something, think If placed (The Right information | To the right people | At the Right time | In the Right place | With the Right context)
effinty2112
Master
Master

Hi Ashish,

                    Check out this post by hic that sets out very clearly when multiple calendars will meet your needs and when you may need something extra called a canonical calendar.

Canonical Date

cheers

Andrew

marcus_malinow
Partner - Specialist III
Partner - Specialist III

Ashish,

if you decide to go down the route of creating a single master calendar, it might be useful to think about what events are associated with your employees. In this case this might be a joining event and (possibly) a leaving event.

If you then create a fact table based on these two event types, it's a simple matter to create a single date field, and a couple of flags, one for a join event and one for a leave event. With this in place, you can chart your joiners, leavers and headcount (using accumulation).

Marcus