ColemenWilson Coach

@MarkSnodgrass Awesome solution! I immediately thought that this would have to be a loop in python but I love your non-python solution!

I replicated your sample data and plugged in my beastmode to the data and it worked as expected. See test column above. Here is the exact beastmode using your field names as provided: CASE WHEN MONTH(`Monthly`) = MONTH(CURDATE()) THEN `Goal` * (DAY(CURDATE()) / DAY(LAST_DAY(CURDATE()))) WHEN MONTH(`Monthly`) >…

I'd suggest talking to your Account Executive and/or CSM about Python scripting tiles or Jupyter workspaces. From there you can find python packages/libraries that help with fuzzy matching:

If you have pre-defined groupings then you can use a formula tile or beastmode to create a new field that groups the data together based on your criteria. You could start with something like this: CASE WHEN LOWER(`Underwriter`) LIKE '%bankers trust% OR LOWER(`Underwriter`) LIKE '%bankerstrust% AND LOWER(`Corporate…

This was just announced today as a new Domo feature release! Reach out to your CSM for beta access!

Assuming your data looks like this: CASE WHEN MONTH(`Month`) = MONTH(CURDATE()) THEN `Goal` * (DAY(CURDATE()) / DAY(LAST_DAY(CURDATE()))) WHEN MONTH(`Month`) > MONTH(CURDATE()) THEN 0 ELSE `Goal` END If your data is structured differently and you can't figure out how to modify the beastmode to work please let me know and…

@zacpolin There is a brand new chart type announced today called Packed Bubble chart that could be an option for your hierarchical data.

I think I have an idea of how you would do this with a beastmode, but wanted to make sure I understand you question. So for example, for this year, January through september would be 100% for each month since they are complete. In the current month, the value would be 18/31 = .58 and future months would currently be 0…

You would use a rank & window tile in Magic ETL. You would rank your data on date in descending order partitioned by the ID field. You would then use a filter tile to only keep rows where rank = 1. If you get stuck let me know!

A similar question was asked yesterday: You'd need the conditions to be in a beastmode so that the color rule can evaluate based on that one field. I think what you are trying to do is compare one column to the target column and then determine if it meets the criteria for a color rule based on that which is not possible.

Gotcha! @MarkSnodgrass code should work. Although, I use a slightly different beastmode at my organization: CONCAT('<div><a href="https://xyz.lightning.force.com/lightning/r/Opportunity/', Opportunity.Id, '"', '"target="_blank">', Opportunity.Name, '</a></div>') If this doesn't work for you please let me know.

Also, as @GrantSmith pointed out, if you have sales in the future then you would also need to include TODAY() or CURRENT_DATE() or CURDATE() in the formula to prevent records into the future from being included. Additionally, on the card you choose date ranges for the data displayed and generally they are: -Year to date…

Yep! You can. Here is the beastmode: CONCAT('<div><a href="',`Link`,'"', '"target="_blank">',`Link`, '</a></div>') You can also replace the 2nd occurence of `Link` in the beastmode with any other field to display that in the table instead of the link.

You'll need to change the card interaction on the dashboard to Drill in place.

Thanks @MarkSnodgrass for pointing that piece out as well! Mark is right, the values you are comparing would need to be on the same row of data or in a beastmode that aggregates the data.

You would use the color rules for the card. Click "Colors" in the Chart Properties in card analyzer view Choose the field that the conditional formatting will be applied to Set the condition Choose the color Choose if you'd like it to be applied to the cell only or the entire row.

They cannot. They can be copied within the same dashboard but not to a new one. What I would recommend doing is build the logic in a beastmode or ETL so that it can be used on as many dashboards as needed.

Hi @Gunjan , drag the date field being used in the x-axis into the “sorting” section of card analyzer. Then choose “ascending”.

You need to partition on both facility and engine. This is an optional step that is needed in your use case. You'll see in the image below that you can partition on multiple columns:

I would use a lag function in an ETL to get the previous value. You'll want to use the rank and window tile, sort on your date field, use an offset of 1 and partition by facility and engine I would assume.

I'm wondering if there is some other filter aggregation being used on your card that may be causing no results to be shown. Are you using this formula in an ETL or in a beastmode on a card?

I replicated your data and beastmode and I am getting the expected results: Could you try creating a table card as I have done with your original column and then your beastmode column next to it? What results are you seeing?

In 2013 I was the monopoly guy (without a mustache because I can't grow a thick enough one)

CASE WHEN MONTH(`DATE`) = 1 THEN LAST_DAY(`DATE`) + INTERVAL 1 DAY - INTERVAL 1 MONTH WHEN MONTH(`DATE`) = 2 THEN LAST_DAY(`DATE`) + INTERVAL 1 DAY - INTERVAL 2 MONTH WHEN MONTH(`DATE`) = 3 THEN LAST_DAY(`DATE`) + INTERVAL 1 DAY - INTERVAL 3 MONTH WHEN MONTH(`DATE`) = 4 THEN LAST_DAY(`DATE`) + INTERVAL 1 DAY - INTERVAL 1…

This is not possible using the calendar filter. You could create 2 drop-down style filters, one for the start date and one for the end date. End users would either have to type the date to search through the possible values or scroll through to make a selection. Not a perfect solution but I would say better than the slider…

Yes, that makes it much easier! Just date added on the x-axis and then a COUNT(DISTINCT(`id`)) beastmode on the y-axis.

Does your data have a date field that indicates when the ID was added?

You would have to do some work in ETL. I would create a recursive dataflow with a monthly snapshot. Then you could do a join of the current month in one branch and all other historical data in the other branch. Any ID's in the current month branch that don't find a matching ID in the historical data would be new ID's and…

This can all be done in a single ETL. Just go through the flow as you have in your head in Magic ETL and add the inputs along the way joining them as you go. You got this! Let us know if you get stuck!