Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more.
Get startedGrow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.
Hi,
I have the following entities in my source system (simplified for the forum):
Leads
lead_id | created | updated | age | gender | sum_assured | lead_status |
12345 | 2021-01-01 01:00:00 | 2021-01-04 14:23:12 | 45 | M | 100,000 | 4 - Sold |
Note: lead_status gets updated during the sales process from;
1- New > 2 - Contacted
2 - Contacted > 3 - Quoted
3- Quoted > 4 - Sold
Calls
call_id | lead_id | created | duration_seconds |
00001 | 12345 | 2021-01-01 09:32:09 | 0 |
00002 | 12345 | 2021-01-01 10:49:12 | 0 |
00003 | 12345 | 2021-01-02 14:21:56 | 0 |
00004 | 12345 | 2021-01-03 16:45:56 | 45 |
00005 | 12345 | 2021-01-04 14:00:03 | 967 |
Tasks
task_id | lead_id | created | task_type |
00001 | 12345 | 2021-01-03 16:47:09 | Call Back Scheduled |
The current plan for the data model looks like this, in order to report on effort and time taken to get a sale
DimDate - Standard
DimTime - Standard
DimAgeGender - Agebands by Gender
DimSumAssured - Sum Assured Bands
FactCalls - Transaction Fact Table
FactTasks - Transaction Fact Table
FactLeadSalesProcess - Accumulating Fact Table
Is this a sound approach or should i be looking at Calculate Table to aggregate data from the transactional fact tables, i'm a bit confused any help is appreciated.
Best,
yokunade
Hi @yokunade ,
This video can help you model the sales process data:
Best Regards,
Liang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
User | Count |
---|---|
84 | |
80 | |
72 | |
71 | |
55 |
User | Count |
---|---|
108 | |
106 | |
93 | |
84 | |
66 |