Jonathan53891 Contributor

Hi @haipham, I'm not sure how closely this translates to this particular use case, but I can generally explain how to handle the grouping logic in a similar scenario. My general recommendation would be to split the data between forecast and actual data so they are calculated separately. Then I would use an Add Constants…

No problem, @Barb! Let me know if you are able to complete that and I can assist you with the grouping logic from there.

My pleasure! Always more than happy to help!

Thank you for the additional context, @Barb. Here's what I recommend doing for the time being: Move your 'Actual v. Forecast' and ROAS calculations into the ETL Have two separate output datasets in the ETL: One that contains the current output dataset you are using to power all of those cards without any changes made to…

Hi @Barb, Would you be able to clarify which of the columns in your pivot table are using Beast Mode calculations? If you are just using Beast Mode calculations for the variance columns in the "Actual vs Forecast" grouping, you can certainly move those into the ETL and create the grouping logic in the sample screenshot you…

Got it. Unfortunately, there is not a native function in Domo that can produce the top N analysis that you are trying to accomplish. However, I believe you are able to achieve this by coding a Python script in the ETL that can dynamically adjust the summary number at the card level after filters have been applied. Please…

Are you trying to create a dynamic Beast Mode calculation that adjusts based on the filters applied to your dashboard, ensuring the summary number reflects the top 5 provinces' parcel quantities under those conditions? Or are you looking for a static calculation that consistently shows the top 5 provinces' parcel…

The SUM DISTINCT function is interesting in that it only sums the distinct values in the column you are referring in your Beast Mode calculation. For instance, let's consider an example where you have two projected load values for 2024-05-01 (10, 20) and three projected load values for 2024-06-01 (30, 10, 10). The SUM…

The reason why it is sorting in the way it is currently presented is because the months are in text value. Since it is being sorted in ascending order, it is sorting from A to Z (Feb, Jan, Mar). The easiest solution would be to drag-and-drop a date field into the "Sorting" section (Order Date in your provided screenshot…

Hello @Parkerains, this will depend on how you have the Magic ETL dataflow set up. One solution to this would be to use the "Add Constants" ETL tile in your dataflow if you are appending your data sources together. Once you have finished creating the dataflow logic for each of your respective data sources, you can place a…

While it isn't a perfect solution, one work around I have found is using an HTML Easy Brick that uses Google Fonts for my desired font. After navigating to the app store and launching an HTML Easy Brick, this is all of the code I need for a simple text box for one of my instances that prefers Montserrat as their…

Thank you so much, @david_cunningham & @JasonAltenburg! So excited that we were able to all work on this together and share this knowledge with the rest of the Domo community!

Thank you so much @JasonAltenburg!

Thank you so much @MarkSnodgrass - always happy to help out the Domo community!