Best Of

Hi @b_rad

1 - You should be able to pass in multiple filters for different columns to filter your data. It's outlined under https://knowledge.domo.com/Engage/Sharing_Content_Outside_of_Domo/Using_Pfilters_to_Apply_Filters_from_URL_Query_Parameters_to_Embedded_Dashboards

Looking at your URL it appears you're passing in the pfilter variable twice which would cause issues. You want your pfilters to be combined in the same JSON object you're passing through to your pfilter

?pfilters=[
{
"column":"Opportunity",
"operand":"IN",
"values":["TE","WR"],
},
{
"column":"Package.Name",
"operand":"IN",
"values":["Amsterdam","Anchorage"],
}
]

This is all back of napkin untested but it'd end up looking something like this (removing the second ?pfilters=[ and replacing it with a comma - also ending your first list of values with a closing ] and closing out your first pfilter definition with } ) :

CONCAT('<a href="https://xxxxxxxxx.domo.com/page/xxxxxxxxxxx'

,'?pfilters=[{%22column%22:%22Opportunity%22,%22dataSourceId%22:%xxxxxxx%22,%22dataType%22:%22string%22,%22operand%22:%22IN%22,%22values%22:[%22'

,`Opportunity`

,'%22]},{%22column%22:%22Package.Name%22,%22dataSourceId%22:%22f7307a70-2c25-4165-bdaa-4742ea6f5499%22,%22dataType%22:%22string%22,%22operand%22:%22IN%22,%22values%22:[%22'

,`Package Name`

,'%22]}]" target=%22_blank%22>'

,'3rd Party KPI'

,'</a>'

)

2 - Only Table (HTML or Mega) cards are capable of utilizing HTML links as part of the card display.

Hi @b_rad

You'd need to aggregate your data such that you have each value separated by "," (including the quotes) so that each value is properly escaped when you pass it in as a pfilter argument list.

Hi @rockchalk629

You won't be able to combine those three separate types of graphs however there is a Line + Stacked Bar chart which would allow you to get portions without the area piece.

Hi @jgospel

It's because of the extra columns you have displayed in your chart. Because you have Compliance Error, question_max_score and answer_value it's grouping by those so it's only looking at the compliance error within that specific group rather than at just the agent full name level. If you remove several of those columns that are for debugging your query will likely work.

You just need to utilize aggregates in your beast mode to add all of the elements in the group before determining the percentage.

SUM(`performed`) / SUM(`projected`)

You can then format that as a percentage to display correctly.

The problem with the Total Row column is that it adds everything together so if you're at 80% for both weeks it'll think it's 160% instead of the 80% across the total.

You could try and union / stack your data such that there is a "Total" recruiter the the aggregated data but that won't allow you to see those total records if you're filtering on a specific recruiter.

Also, by utilizing a window function in a beast mode it'll properly handle any filtering done to the cards instead of doing it within an ETL.

Awesome! Glad to hear it @user028768

If you could mark my answer as accepted for others to make it easier to find I'd appreciate it. Thanks!