When One Agent Tried to DO Everything

Image
When One Agent Tried to DO Everything The second article in my Finance Agent series My first Collection Manager Agent worked well - until I kept giving it more jobs. What started as a customer-review assistant grew to hanle automated credit-hold analysis, collection-call preparation, and customer email drafting. Each addition made sense. Together, they created a problem. In my first article, I mentioned the importance of narrower scope. This time, I want to show you what happened when I ignored that lesson. Watch: Why I Split One Agent Into Three What the First Version Was Asked to Do The first Collection Manager Agent started with a simple job. Review a customer. Pull the aging, the credit limit, the open invoices. Tell me what to do next. It did that well. Then I started adding to it. • I wanted it to react automatically when a sales order was placed on credit hold. • I wanted it to prepare me for a collection call. • I wanted it to review disputes and promises to pay. • I wa...

Covid Dashboard - Article 6 - Creating a group for a slicer

I will continue to build on my earlier posts about my COVID19 Dashboard.  In this series, I have written a few different blog articles describing not only how I built it, but some things I learned in the process.
The current list of topics include:
Today I am going to look at a question one person asked me.  When they were using the dashboard, they wanted to be able to filter the global results by countries of similar size.

After thinking about this for a while, I decided on the following approach.  There are probably different approaches that can be used, and that is one of the things I really like about Power BI.  In this case, I tried to take a very simple approach.

Step 1 - I had to decide how I wanted to group the countries.  

I took a look at the data, and decided it would be best to group the countries together in five groups.
  • > 100 million
  • 50 - 100 million
  • 10 - 50 million
  • 1 - 10 million
  • < 1 million
Step 2 - Add a new column to the country population table.

I decided to use a conditional column to add the group for each country in the population table.

Population Group = if('Country Population'[Population] > 100000000,"> 100 Million",
if('Country Population'[Population] > 50000000,"50 - 100 Million",
if('Country Population'[Population] > 10000000,"10 - 50 Million",
if('Country Population'[Population] > 1000000, "1 - 10 Million", "< 1 Million"))))

This is simply a combined if - then - else formula.  I started with the largest option first and worked down to the smallest option.

Step 3 - Add a slicer to the report

Once this column was created, I simply added it to the report as a slicer.



You will notice the drop down list for the slicer is not in the correct order.  I would like to have the largest group "> 100 Million" listed last.  This is because the field is sorted alphabetically and numerically, the symbols come before the numbers.

Step 4 - Create a sorting column

In order to fix the sorting of the slicer, I created another column where I replaced the text names of the groups with numbers.


Population Group # = if('Country Population'[Population] > 100000000,"5",
if('Country Population'[Population] > 50000000,"4",
if('Country Population'[Population] > 10000000,"3",
if('Country Population'[Population] > 1000000, "2", "1"))))

I was able to use the Population Group # as the "Sort by column" for the Population Group.  Sort by column can be found on the Column tools menu on the ribbon bar.










With these two columns, I was able to quickly provide the additional information the user was looking for in a very easy, straightforward approach.

If you have any questions about my Covid 19 dashboard or about other Power BI topics, please do not hesitate to leave a comment. 



Comments

Popular posts from this blog

Showing the last 12 months based on a date slicer

A look at Dynamics 365 ERP and ERP Analytics MCP Servers

Adding a new entity to Dual-write in Dynamics 365 Finance