RabidCougar Member

Comments

  • In that case, unless there is a reason you can't do it, then I would second Kurt's recommendation that you get both datasets on the same level of granularity. My answer assumes that dataset 2 has data that looks like this: Name Date Available_Hours John Doe 01/01/2018 140 Jane Roe 01/01/2018 119 John Doe 02/01/2018 115…
  • That is a fantastic question. There are two ways you can go about this. If you were to use a Domo Webform, instead of a Google sheet, that will let you enter data directly into Domo. It isn't quite as straightforward as using Google Sheets, however. The second solution involves embedding a Google sheet inside of Domo. This…
  • Great question! As long as the card is reporting by month, the following will work: SUM(`Hours_Field_From_Dataset_1`) / AVG(`Available_Hours_From_Dataset_2`) You could also use MAX() or MIN() instead of average since there's just one value per rep per month. Should you wish to report by quarter or year, you will need to…
  • Excellent! I am glad you were able to find them.
  • That's a great question. Unfortunately, I have never experienced this. One thing I would check is your DoubleClick for Publishers settings to make sure there isn't something causing it to be multiplied before Domo grabs it. If there's nothing there, then this is something I would want our developers to take a look at to…
  • Fantastic question. Deleting beast modes can be challenging due to all the places they are used. One of the things that can complicate the issue is drill paths. Because those are technically cards too--albeit dependent cards. So the first thing I would do is check the drill paths of the cards Domo says are using the beast…
  • @paulogaspar What you are describing is what we call "sticky filters". That feature is coming and is currently in beta. In the meantime, any user who is above a Participant level user can add/remove page filters. The values each user chooses for the filters is specific to them, but which filters exist can be changed by…
  • That's a great question. I don't know the answer off the top of my head. I would have to test it out to know for sure. But I wouldn't expect filtering on one page to affect filters on cards on anothter page.
  • Upon further review, it doesn't look like you can change granularity for all cards based on a page filter. But you can filter date ranges. I really like the idea of being able to do it. That would require a feature request: 1. Post your idea to our Ideas Exchange board. This is a board where customers can post their ideas…
  • @RGranada Yes. This is expected behavior. Anytime anyone with access to the page changes any of the page analyzer filters, it changes it for all users.
  • @RGranada Thanks for the question. I had another customer of mine ask the same thing, and the answer we got back was that, unfortunately, this is not currently a feature, but it's a great idea. Here are a couple of things you can do to help change that: 1. Post your idea to our Ideas Exchange board. This is a board where…
  • Actually, under Edit Columns there is a transform called Add Constants. This is how you add a new column via Magic ETL. If you leave the Constant Value field blank, it will create the column without populating it.
  • I agree wholeheartedly that this would be something we should be able to do. So without hesitation I upvoted your Idea. Since there is a series in a stacked bar chart graph, which makes it create a sum based on the combination of the series and x-axis parameter, I suspect that to get the sum of the stacked bar, it would…
  • Just curious, nlombardini, have you had a chance to try out my proposed solution yet? If so, I'm curious to see if it does the trick or not.
  • You would be getting a text result, yes--and that's where it's blowing up. Hmm . . . If this will work, I think I might have a way around that. Try this: Let's convert the number to a date, which will then sort the same whether it's a date or a string. FROM_UNIXTIME(SUM(`Open Pipeline`)) As to your question about my logic,…
  • Hmm . . . what happens if you remove the series? Does it work then? If not, I would try looking at the results of the beast mode by itself in a table card to make sure it looks like you'd expect to see it.
  • Gotcha. Change it to SUM(`Open Pipeline`) and let me know the result.
  • There is currently no option to display colors in a table card using the functionality present in the Domo interface. That said, it is technically possible to do it using HTML and beast modes, but that's not an approach we recommend you take. I wish I had a better answer for you than that. Nevertheless, I can definitely…
  • It looks like it might be an incorrect approach. You're wanting to sort on the x-axis, but your sort is using the dimension on the y-axis. I wouldn't expect that to work. Based on your screenshot, you're using a Beast Mode to create your product grouping. So try this: Copy everything that's in your Product Grouping Beast…
  • Nick, We're looking into this and will let you know as soon as we have an answer for you.
  • I don't know if this will be applicable to you and what's causing you to encounter this error, but I have run into this issue before. In my case, what happens is that internally, we make use of virtual machines with Workbench installed on it. When we copy a VM with the standard configuration and don't make any changes, it…