GrantSmith Coach

You can use a beast mode to classify the different buckets or alternatively you could use an ETL and pivot your data in there before displaying in the line + bar chart.

Looks like your python script is failing because of bad / missing certificates. Have you tried installing the certifi package to install additional certificates with pip and then running your python script? pip3 install certifi Additionally the pydomo package needs a client_id and client_secret which you can configure from…

You can use a line + Bar chart to get what you want. If you have your data formatted with option one the first field you put a at value will be the line and all others will be the bars. If you want more than one line you can change the number of fields used in the general section of the properties.

@grace Great! I'm glad it worked for you. If you could accept my answer as a solution so others could find it more easily I'd appreciate it.

What is the value that is being sent up to Domo? How are you generating your data value? Is it possible that when it's being generated before it's sent to Domo that it's getting the .0 added?

You can utilize a rank and window tile within Magic ETL to do this with the LAG function. Partition by SNO and MMODEL and Order By your date field with a lag value of 1. This will give you the prior record's date where you can then feed it into a formula tile or a date tile to calculate the number of days between the two…

CASE WHEN `Intro Call Held Date (Cleaned)` IS NULL THEN FALSE ELSE TRUE END Null is a special value and requires the IS comparator instead of = when checking to see if a value is null or not.

You can find it on the connector settings. As Excel has the row limit you'd be limited to 1M for each file upload because of Excel but it would append those records to your dataset which wouldn't be limited

How is your sort table defined? Can you just make sure you're sorting the values in ASC instead of DESC?

I'd try and use some URL encoding for your pfilters value as that's likely what's causing the issues with the quotes not working. You can refer to https://domohelp.domo.com/hc/en-us/articles/360043430113-Sample-Beast-Mode-Calculations-Miscellaneous-Transforms#5. Also you can use a website to do the URL encoding of your…

Hi @ahobson Case statements are evaluated from a top down approach and will only evaluate the first true condition it finds. In your case it'll return 'canada' first as that's the first condition that was met to be true and it won't ever return growth.

When using the file upload you should be able to set the Update Method on the settings as Append so when you upload a new file containing the new rows it should put it at the end of your dataset.

What does your HTML / beastmode code look like?

It doesn't support aliases. The beast mode you're creating is essentially the alias for your calculation

Hi @Kervin Your code should work to pull the value from the COLUMN column. If you're needing to select from a different column name based on certain criteria instead of COLUMN then you could utilize a CASE statement inside your CONCAT:…

We just need to add another match group () to the regular expression and surround the entire IP address to match the entire IP address. CASE WHEN REGEXP_LIKE(`ip_address`, '^.*199\.15\.([0-9]{1,3})\.([0-9]{1,3}).*$') THEN  REGEXP_REPLACE(`ip_address`, '^.*199\.15\.([0-9]{1,3})\.([0-9]{1,3}).*$', '$1') ELSE '' END $1 will…

It is a bit odd why your Rent Last Changed field won't take the substring as it appears correct. Here's a few other options for you to try: Utilize LEFT in a formula tile: LEFT(`dRentLastChanged`, 10) You could try to utilize a formula tile to convert it to a date: DATE(TIMESTAMP(`dRentLastChanged`)) Alternatively you…

Hi @dylang91 First thing I would simplify your beast mode. If you go in descending order of your buckets so that the largest bucket is first you can remove the secondary conditions on each of your cases because the CASE statement will evaluate the first and only first condition where it's true so future conditions are…

@JunkDoom Embed permissions are configured on a dashboard level however multiple users could embed the same dashboard. If you're worried about dashboards being shared publicly or who's embedding them you can revoke that permission in a custom role and make sure your users are set to that role.

I've done a writeup of lag functions and rolling averages before utilizing Beast Modes but the idea at the end is the same concept. You just need to calculate the Lag for 1 month ago and 2 months ago into three separate fields. Then add all 3 together (current month, 1 month ago and 2 months ago) and divide the total by 3…

You should mark your connector schedule as manual and save it, then when you get to the minute you're wanting it should update to the minute it's currently at when you save the schedule.

Hi @JR_S1L You'd need to keep your data as is to partition based on name to get the lag for the prior 3 months to get your rolling average. You can use a rank & window tile in Magic ETL to calculate the lag just make sure you're partitioning by the name and that you're sorting/ordering by the month

@yli_2596 There isn't really a simple way to change the hourly schedule to run on a specific minute of the hour. Domo did this to help spread jobs around a bit so they're all not running at the exact same time. You'd have to create the job on the minute you want it to run. Is this a workbench job or a data connector?

Use a JOIN tile instead with an INNER join to join your prod and google datasets together based on your join condition. This will fitler out any records in your prod dataset which don't appear in the google spreadsheet.

Make sure you’re filtering your data after your join so the month of the journal entry transaction is the same as the month of the budget forecast. You could do something like this in a conditional filter: LAST_DAY(`Adaptive Date`) = LAST_DAY(`Netsuite Date`) LAST_DAY is a function that returns the last date in the month…

@NathanDorsch I'd recommend reading an article I wrote up on how you can combine your data to do YoY or MoM more easily and have each of those included in the same graph using separate beast modes.

You’re correct. Administrators are allowed to see all data so you wouldn’t be able to restrict their access. you could set up an alert on the access logs to send an alert if someone other than the approved users accessed the card but they’d still have access to it and the data.

You can use pfilters in the URL to pass filter values. You can read up on them here https://domohelp.domo.com/hc/en-us/articles/360042933114-Using-Pfilters-to-Apply-Filters-from-URL-Query-Parameters-to-Embedded-Dashboards

@NathanDorsch That's quite a lot of cards on a single dashboard which typically makes it hard to tell a data story with that many. I'd recommend breaking them out into separate dashboards. Other things you can look into would be The number of beast modes stored on the dataset used or not as they're all processed when the…

I'd recommend logging a ticket with support and raising the issue with them so they have better visibility into the frustration it's causing to help encourage them to see if they can fix it in the future.