ST_Superman Domo Employee

Could you provide a small sample of your dataset? Maybe for 2 or 3 projects so that we can understand the structure of the data?

I would lean towards adding a `Latest Hire Date` in the dataflow. This would let you add a case statement that would let you only count the occurences when they occur after the latest hire date.

I don't believe this is possible via beastmode. I have heard rumors of being able to add aggregate fields to a filter, but that is not yet in the product so I think you will need to make these changes in a dataflow.

You should be able to use something like this: COUNT(DISTINCT case when `Status on Date`='Active' then concat(`ID`,`Date`) end)/COUNT(DISTINCT `Date`) This will let you graph the Average headcount for any period instead of just the active headcount.

Unfortunately, GROUP_CONCAT() is what you are looking for, but that is not available in a beast mode. You would need to aggregate COLUMN A in a dataflow using GROUP_CONCAT()

Hi @Whimzyy It looks like what you are trying to do is subtract 1 day from the submit date and then add 27 days to it? What happens if you try something like this: DATE_ADD(`Submit Date`, INTERVAL 26 DAY) Or did I not follow your code correctly? 

I don't think you will be able to create a filter. However, if you create a beastmode that counts the number of times a value was searched for you should be able to accomplish something similar using the DATA TABLE to limit the number of rows. COUNT(DISTINCT `Value`) This should give you the distinct count for each "Value"…

There is currently a product in beta that grants this ability. Filter views. If you are interested in joining, you should contact your Domo CSM. I'm not sure when the beta is scheduled to be released into the main product.

this is what I get for select version() 5.6.28-76.1-56

My first question is did you save the =Rent Status beastmode to the data set? The field has to be saved to the dataset for the Page filters to work. If not, then save it to the dataset and refresh your page. See if that works.

The filter card should work to apply filters to the page, and those should go through to the drill path. Could you share the analyzer settings for your filter card, the first view of the card in question, and the drill view that is causing you troubles? Hard to troubleshoot without a little more info.

I think this will get to what you are looking for: case when month(`Date of Invoice`)<MONTH(CURDATE()) then 'Historic' when month(`Date of Invoice`)>MONTH(CURDATE()) then 'Future' when day(`Date of Invoice`)<DAY(CURDATE()) then 'Historic' else 'Future' end In this statement, if the month is less than the current month then…

If you are just looking to denote if it is historical... Why not just use CASE WHEN `date` < CURRENT_DATE() then 'Historic' ELSE 'Future' End **** I just read the question a in a little more detail. Your solution is only going to work if you are already past leapday. and only for 2020. I would try to use something more…

@user06643 did you have a question we could help with? Otherwise, I would make this comment using the feedback tool and try to keep this forum free for those that are looking for help. If you feel something needs to get updated from a knowledge article written over a year ago, you are probably right. Submit the feedback.…

The updated navigation is part of a new feature that Was released last year. You may need to talk to your admin or to you Domo success partner to get that turned on for you

To convert the excel field to an actual date, you just need to create a beastmode using ADDDATE (or DATE_ADD ... they are the same function I believe). The excel format is to count every day forward from January 1, 1900. This means to convert it you need something like this: DATE_ADD(STR_TO_DATE('1900/01/01','%Y/%m/%d'),…

I didn't have a dataset with a timestamp on it, but here is a similar view using days and months: Here are the chart properties: Let me know if that helps. Or, if you don't mind attaching some sample data that I could use, I could try with some of your data.

My first suggestion would be to try removing the "Date Output Format" and setting the "Never Use Time Scale" back to default from the Category Scale (X) section.

Can you show the chart properties of the card you are building?

You could potentially highlight the dates when you have data entered if you change to a heatmap. I'm not sure what your specifice use case is, but see if this would work for you:

Unfortunately, you can't filter a card based on an agregate value. That means that if you want to filter out the combinations on Date and Collection Code that contain no Data entries, then you would need to first work that into a dataflow. Either ETL or MySQL, so that the card can then filter on it. Let me know if you want…

Wait a few weeks. The beast mode manager is still in Beta. You can try reaching out to @chucki to be included in the beta, but it is not available in the general release yet. I would anticipate that you will hear more about this feature in the Domopalooza streams.

Just out of curiosity, what would happen if you added a filter to that card for `Value` not equal to 0?

I would open a ticket with Domo support if you haven't already. Is this happening for all users in your instance?

This should be doable. Would you mind sharing some screenshots of the ETL? Specifically, the configuration for the tile where you try to change the name?

I'm not sure where that pop up is coming from then. Do you partner with any 3rd party developers to help with your Domo content? I would try checking there. Otherwise, my best guess would be that it is related to completing your profile:

I've never seen that before. However, if I had to guess I would say that it is an achievement that your company has created in your Domo instance: See if you can have an admin either remove the achievement, or remove your visibility to it. I'm pretty sure you can assign achievements by user.

You can update your calculated field to something like this: case when `Total Sales` is null then 0 else `Total Sales` end If you can share your `Total Sales` beast mode, I could give you a more concrete example

@Valiant is on the right track. The way that a case statement evaluates is in the sequence of the when statements. In your example, CASE WHEN `Case Owner Manager` IN ('a', 'b,'c') THEN 'Tier 1' CASE WHEN `Case Owner Manager` IN ('d','e','f','g') Then 'Tier 2' CASE WHEN `Case Owner Manager` IN ('h', 'i') Then 'Strategic'…

Hi Kevin, I'm not sure why this works. But, I was getting the same odd sorting that you were: However, if I added a rank function to it, the sort worked: ... or it did when I included one extra column??? Very odd. In conclusion... I would say to cautiously use the ORDER BY in redshift. If you do, you will want to…