MarkSnodgrass Coach

You can use the QUARTER function to create a beast mode for your series like this: QUARTER('datefield') You can create another beast mode so that the x-axis always shows 1 - 13-ish for each of the quarters with this: WEEKOFYEAR(`datefield`) - ((QUARTER(`datefield`)-1)*13) Having said that, you can use period over period…

@jmcgurl you need to replace 'datefield' with the actual date field that is in your dataset. That was just a placeholder since I didn't know the name of your field.

@jmcgurl to @jaeW_at_Onyx 's suggestion that I totally agree with, you can create beast mode to just return the day of the week and bring that into your quick filters. You could do this: WEEKDAY('datefield') or you could use DAYNAME('datefield') which would Sunday, Monday, etc, which would be more readable to people than…

When troubleshooting, I try and break things down and also use a table card to easily see the results. I would try making 3 separate beast modes, one for each criteria in your beast mode and then put each of them in your table card. Something like this: Weekday beast mode field CASE WHEN WEEKDAY('datefield') = 1 THEN 'Y'…

Sorry, that slipped by me the first time. To get Sunday from the date, you just need to do this: WHEN WEEKDAY('datefield') = 1 AND `SESSION PURPOSE` = 'FULL_STORE_SCAN' AND `REGION CODE`= 'NA' Then COUNT(DISTINCT `STORE NO`) End Replace datefield with the actual name of the field that has the date.

Your case statement is close, but you need to use AND to include multiple criteria, like this: case when WEEKDAY(1) AND `SESSION PURPOSE` = 'FULL_STORE_SCAN' AND `REGION CODE`= 'NA' Then COUNT(DISTINCT `STORE NO`) End

In Magic ETL, I would do a LEFT JOIN with the customer table to the credit limit table so that you would have rows for every date. Next, use the Rank & Window tile and use the LAG function pull the credit limit from the previous date. You would then replace nulls with the last value This will get you close, but will be an…

I just had to do some password resets yesterday and I didn't have any issues. I would make sure the user's browser isn't putting in a saved password automatically for them.

You can use the SPLIT_PART function primarily to split these all out: First Name SPLIT_PART(TRIM(SPLIT_PART(`Name`,',',2)),' ',1) Last Name SPLIT_PART(`Name`,',',1) Middle Name SPLIT_PART(TRIM(SPLIT_PART(`Name`,',',2)),' ',2) Based on your examples, this will do the trick.

@user048760 in Magic ETL, you can use the String Operations tile and choose Right/Left Substring, select your column, enter 10 for the substring length and choose Left for side to start from. This will remove everything from the T and later, leaving just the date. Next, drag in the the Set Column Type tile and connect it…

According to Microsoft's documentation "each private channel has its own SharePoint site". Within Teams, if you click on Open in SharePoint for the secure channel on the Files tab and look at the path and then do the same for a regular channel in within the same Team, compare the URLs and see if they are different. Here is…

That seems quite odd and that job became corrupted somehow. Can you try changing the schedule and see if re-saving a new schedule fixes it? Or try re-creating it as a new job? Those would be the first two things I would try.

If you are the owner of the account, you can go to the data center and then click on Accounts on the left. Then find the account you want to rename and click on the wrench on the right and choose Edit Account. This will let you rename the account.

I believe you need to start using the client ID and secret with OAuth 2.0 in order to connect now. You may want to review this page:

You might try appending your call outcome codes rather than joining. When appending, choose to include all columns. This should keep your data from duplicating, but still allow you to filter in various ways.

If the connector is living in Domo, then the computational costs will be on Domo's side and not yours and also should be negligible with one line of code. Having said that, you could let it come in as is and then use a Magic ETL dataflow to convert it to a datetime if Domo doesn't automatically recognize it.

If you switch your card type to Line + Grouped Bar chart type, you can set the last value projection for both the line and the bar.

In the analyzer click on "Add Calculated Field" in the bottom left and write the following formula: CASE WHEN 'bRentable' = 0 THEN 'Unrentable' WHEN 'bRentable' = 1 THEN 'Rentable' ELSE 'Unknown' END I used the else clause in case you have empty or null values and didn't want to assume it was rentable or not.

Since Zulu time is the same as UTC and Domo is expecting the datetime to not have a timezone label at the end, I would either use the LEFT function to get only the datetime data, or use the REPLACE function to remove the Z from your string and then Domo will interpret it as a datetime value. REPLACE('datefield','Z','')

I might be able to make better recommendations if you provided a sample of your data, but it is likely giving an error because of the quotes around 1 after your greater than or equal to. Try this for starters: (CASE WHEN (COUNT(DISTINCT `ReportDate`)) >= 1 and (COUNT(DISTINCT `Agents`)) >= 1 THEN '1' ELSE ? END)

@dacorson I have had the same experience myself when converting Redshift dataflows to Magic ETL and have had to be very mindful of my naming conventions because Analyzer is case sensitive. It would be a nice enhancement if Analyzer did not care what case a field was when you changed datasets. I would recommend submitting…

The period over period chart expects a single date column, so you are going to want to restructure your data, or look at a different chart. If you restructured your data like this: Machine Name DateLastSync PC1 7/1/2021 PC1 6/1/2021 PC2 6/1/2021 The period over period chart could work for you.

That is the correct way to do it. Sometimes, there is a delay in the output dataset seeing the new column order. Try refreshing your browser when looking at the data. You might also try adding an additional column temporarily in your select columns tile and verify that the output dataset display is seeing it.

@moneyshot Divergent colors were added as a chart property to heat maps a couple months ago. If you select that, it will default to red to green for the divergent colors. There are several additional properties within the divergent section to give you more flexibility. You can read about them in the Heat Map KB article.…

You can do this by creating a beast mode that would rename your fields and then drag that field into your series. Your beast mode would look something like this: CASE WHEN 'fieldname' = '{"Mode":"Auto","Rule";"Tree"}' THEN 'Point - Tree - Batch' WHEN 'fieldname' = '{"Mode":"Manual","Rule";"Tree"}' THEN 'Point - Tree -…

@eriena The screenshot that you provided is just a condensed list of connector, which you can get to by click on Connectors from the data center, just to the left of File. You can then type in the name of the specific connector that you want to use. I imagine, Domo will fix the "more upload methods" eventually, and you…

One easy way in the Add Formula tile is to multiply the column by 1 like this: "count"*1 I have used this multiple time to get a number to integer that didn't start out that way. If you aren't doing any data cleansing along the way, you can also click on the input dataset and change the data type for that column. (This…

@eriena I am getting the same thing in my instance. However, I never have to click on "more upload methods" to upload my Excel file. I just drag and drop it into where it says "drag and drop file" or click on the browse link just below that and navigate to where my file is. I noticed some recent changes they did to the…

If you are doing this in a beast mode, you can use INSTR and SUBSTRING to get it. It would like like this CASE WHEN INSTR(`column`,'876') > 0 THEN SUBSTRING(`column`,INSTR(`column`,'876'),7) WHEN INSTR(`column`,'877') > 0 THEN SUBSTRING(`column`,INSTR(`column`,'877'),7) END

@dacorson given that Domo just did a big release on the 14th. My guess is that something got messed up in your instance that is causing the issue. If you want to post the syntax for the window function beast mode that is in use when you try and save the card, we might be able to reproduce in our instances and see if the…