@BrianJ
still, you know if there are no doctors or internet in a small town a dude who goes to the city and googles the symptoms and gives a diagnosis is considered as a Doctor in that town? so it’s close enough
Thank God for google.
@BrianJ
still, you know if there are no doctors or internet in a small town a dude who goes to the city and googles the symptoms and gives a diagnosis is considered as a Doctor in that town? so it’s close enough
Thank God for google.
Hi everyone
My considerations
DATAMODEL
There was a lot of dimension. In the excel file from sheet Complaint Data I when through all the dimensions sheet to find which column could be linked to sheet Complaint Data.
Then I found that Sheet Regions and State Regions had connection to the customer and not Sheet Complain Data.
In the beginning of my process I thought the main Fact table was Complaint Data and the table Status History Data should have link to Table Complaint Data.
Afterwards I realize that all the dimensions from Complaint Data should be merge to Status History Data and table Status History Data had also record on claims which still where in process.
QUERY
The table Regions in some of the columns, had also Underscore between the words. I could handle it manually but looks in M code to see how this should be handled if there was a lot of tables with this issue. Because there was no function in Power query to handle this.
I came to this M-code.
“= Table.TransformColumnNames(#“Changed Type”,each if Text.Contains(,"“)
then Text.Replace(,"”," ") else _)”.
This M-code look for the Underscore and if not, it leaves the column.
There was a function to change word where, so the first word starts with Capital letter. I used that afterwards on column name.
MEASURES AND CALCULATED COLUMNS
I did only make one measure it was DISTINCTCOUNT to count number of claims.
What I found interesting was to show how many days a claim was in each status. In last challenge 5 with eyes I would also like to calculate how much have the ex. Left eyes change from last time. Could not solve that.
This time I solved it. Each claim has many records for each status and a date for when the claim started the new status. I had to Range each claimID limited to the each ClaimID. Afterwards calculate the dates between to days. So, Rank 1 Status Start days 2019-01-15 and Rank 2 Status Start days 2019-01-20. So, Rank 1 status has then been on its status up to the day where Rank 2 status get its start date.
Remembered that I have read something about this issue. Now I found it SQLBI.COM. I used RANK as calculate column and then LOOKUPVALUE as calculate column. The calculated columns is placed in table Status History Data.
There is one issue. If the user gives a claim two different status on the same date. So, Rank 1 have two different status and up to Rank 2 the days will be counted twice.
I would say this could be an issue for the Internal Audit , as it should not be allowed. If change status on a date where it already has a status. The right way should be changing the status on an already record on the date.
I also decided that below 1o days in one status was fine. < 10 Green, < 20 Yellow, >= Red.
VISUALIZATION
One factor we should consider was “Complaints broken down by the dimensions”. I find there was so many dimensions and not all I know what means.
I decided to show this as a Decomposition Tree Visualization, so the user can decide what to look at.
INSPIRATION
This time I did not see in challenge 6 to get in inspired.
Now I look forward to being inspired.
Challenge 6 - Insurance Complaints Data Amdi Silword.pbix (1.7 MB)
(upload://obPdeb9RZ0e46hd8uUAlp2appMm.pbix) (1.7 MB)
Have a good day everyone,
Here is my submission for this challenge.
https://drive.google.com/file/d/1VITQoLF8la9w3bRj9XXjJUFeMoOYIPa9/view?usp=sharing
Thanks & Best Regards
Nhat Lam
Hello all,
Please find below my entry for the Challenge number 6. I went for a different approach for this challenge.
I wanted to try out some new ideas and techniques and also concentrate on the message to transmit.
GLOBAL OVERVIEW
I started with a Global Overview which contains the main information I considered useful. I wanted the end users to know the main facts and numbers. Basically I wanted them to know the “WHAT and WHEN”
The main KPI, the one related to the Average Duration, has more information to it then we consider at first glance. We have the card that shows the average duration, the trend below, a tooltip and a Visual Header
BROKERS
My second page navigation focuses on the “WHO” question.
ZOOM into MAR-APR 19/ OCT 19
By now I should have the attention of the public and the story needs to focus to smaller details.
I built the navigation so that the user could drill down into 2 periods that are the outliers of the data.
2 Periods are in this category, MAR-APR 2019 and OCT 2019
INSIGHTS AND RECOMMENDATIONS
The difficulty of this challenge is that we have to provide a lot of information to the user. But to much information presented could create to much mental fatigue. In order to avoid that, I concentrated to show only informations I think are useful and added an Insight and Recommendation page.
Best regards,
Alex
GIF
Update: With the help of @BrianJ, I can now share the link for those interested to have a look.
Thank you Brian
Hello everyone,
Here is my entry for this challenge. Full write up will follow in the following days, since this is a holiday weekend for us in the States. I do want to point out that I took a slightly different approach to this challenge. From the Customers table, I only chose “Individual”, not “Company”. Therefore, my numbers will be slightly different than other entries.
Here are some screen shots of my report pages:
Here is the link to my report:
Thanks
Jarrett
@alexbadiu wow really cool work again. Absolutely love the theme, tooltip and the way you highlighted the months in the trend chart. That’s awesome.
Were you having Whisky while deciding colors? because at a first glance It reminded of it. Great report!
Lol @AntrikshSharma ! not quite from whisky. My inspiration came from Microsoft Windows 8
a) for the blocks
and
b) From Microsoft Power Bi site for the colors
Hi all,
Here is my submission for the challenge. I will put write down my considerations later on. It’s a simple report.
![CH6 DA 3|690x380]I can’t publish to the Power BI Service because of policies so I’ll provide my PBIX.
eDNA CH6 DA.pbix (1.9 MB)
Looking forward to feedback.
Daniel
Thanks for the shout out @Neba, but all the pattern posts are a collaborative effort of the expert group and the eDNA team (and most often to follow-on forum posts), so thanks to all.
Greg
@uriah,
Very cool - I love the interaction between the small multiples and the mapping tooltip – I’ve never seen that done before.
P.S. I just sent you a published to web link you can include with your submission.
Hi All!
Here is my submission: DataZoe Power BI Challenge #6
Some images:
Tooltips:
I used the PowerBI.tips theme “Spash-o-Red” available here: https://powerbi.tips/product/layouts-splash-o-red/
I also found some guidance on the Status History from the Microsoft docs on using DevOps feeds to Power BI here: https://docs.microsoft.com/en-us/azure/devops/report/powerbi/create-timeinstate-report?view=azure-devops
Hi All:
Here is my (incomplete) submission for challenge #6. I didn’t even get to the Status History table, but thought I’d submit what I had.
I started out on this challenge with more of an experimental sandbox mindframe, and never quite made it to a fully prepared report submission, but there were many areas I wanted to explore, which are below the “liked” notes:
What I liked:
What needs more attention/what I didn’t like:
Here’s a more detailed list of some of the techniques I used in my report:
Wow I really like your design, very polished! Great job!
@datazoe Great work. What’s the chart you used on Trends? Amazing how everyone looks at the data differently.
@Greg you deserve an award just for explaining in detail the steps and tricks you used in creating the report. I haven’t yet seen the TopN and others technique in donuts and pie charts. Would love to try the technique in other visuals.
I like the red abstract theme you used and you really made the theme work. Only if you could have carried the red theme in all of the visuals it could have been awesome. Blue and green color doesn’t seem to be working in the report.
Lots and lots of tricks to learn from your report.
Thank you for completing the challenge as these types of reports give the motivation to learn more and more.
Totally agree with @MudassirAli in that I think the bright red theme looks awesome, but wish you’d committed to it fully. As always, so many detailed touches to love in this report (I’m 100% stealing that Chevron page navigation construct). One thing I absolutely cannot figure out is how you got the publish to web to default to full-screen with no other on-screen navigation except that which is native to the report itself?