AS Coach

Is that your error message from the NetSuite SQL engine or connector? Unfortunately I'm not familiar with how NetSuite has implemented SQL and a quick Google search doesn't reveal much, either. Just to be sure, that GROUP_CONCAT function does have an option delimiter parameter, so you might try adding that (like…

I'd do something like @Billobi recommends. Alternatively, consider reaching out to Domo and they might be able to set you up with a custom fiscal calender. Lots of customers have done this.

There's a GROUP_CONCAT function in SQL that would do this well for you. I don't think the same exists in ETL in Domo. https://www.w3resource.com/mysql/aggregate-functions-and-grouping/aggregate-functions-and-grouping-group_concat.php

That sounds like a manual process to me. To get that done in an automated way you'd probably need another application, or to have a combination of PDP/Publication Groups with the Word plugin. I haven't heard that that's available.

I thought the column limit was closer to 250, but that's nearly 5 year old knowledge and things have likely changed. Have you tried a Sumo card to see what its limit is there? Or, you could put a few cards on a page, side by side, and have them act as vertical slices of the data.

Brian makes good points. I'll follow that up with a comment. You won't really be able to dataflow your way into updating the original data in Domo (not that I'm aware of, anyway). The options presented will lead you to a second, improved version of the original data and both will reside in your data center. Best would be…

I don't think HTML will work in calendar cards. New lines appear to be restricted to new records, not different columns on the same record. You might have to break apart your values into individual records in a dataflow, if that's possible. Let me know if my assumption about your data is incorrect.

Here's what I've done in the past that has worked. Call out the denominator as zero calulcation first, then go on to the calculation if it's fine. CASE WHEN IFNULL(SUM(`AdjustedSalesRevenue),0) = 0 THEN 0 ELSE [calculation] END Does something like that work for you?

It's probably either in your date subtraction or in your assignment of the grade. I've found it works best to use the DATEDIFF() function instead of simply subracting like you might in certain database queries. BETWEEN doesn't always work well in beast modes, either. String outputs should also be surrounded by single…

Man, that would be cool, but currently that's not part of the default card functionality. You could probably code an app to do something like that. You could create a webform dataset to update that value, and use the webform in a dataflow with your card's dataset. That workflow would be a bit clumsy, but it could work as…

That looks just fine to me. Does it change if you did LEFT OUTER JOIN instead?

Do that all in one dataset if you can, unless you'd have a reason to have these as individual datasets for separate use in Domo. Most of our Workbench ODBC queries have multiple table joins. It's just passing the query to the server to process, so it should be able to use whatever logic you provide it. For example, we have…

Yes, that makes more sense. I am not aware of a way to conditionally send scheduled reports. What about setting up a publication URL where they can access the card any time they want? That still wouldn't provide the notification in their inbox, but it would reduce the clutter.

At a high level your beast mode looks conceptually ok. What kind of chart are you using and where is the value showing up as 0? Is that what your data actually looks like, or do you have more rows per month that would need to be summed up? What I'd do is break it up by the components (numerator and denominator) and then…

Maybe an alert would be better for you, and to send them daily when the total is greater than zero. How does that sound?

Graph by and period over period comparisons require that the X-Axis have a date datatype as the chosen column, in addition to other things. You also need to uncheck the box labeled "Hide date on card details".

Do you have a large number of customers that would have to be listed out in a case statement like that? I mean, if you have a few then it shouldn't be a problem to just list out a few clauses in your case statement. case when name_cust like 'CustomerName1%' then 'CustomerName1' when name_cust like 'CustomerName2%' then…

The only other thing I can think of is it's either a bug, or the annotation menu "Hide date annotations" option has been checked (right below the "Create date annotation" option). If it's a bug, you'll have to submit a ticket to Domo support.

Which browser are you using? I'm using Chrome, and I'm able to add an annotation to a month of a stacked area chart.

If you're using transforms in multiple stages, you can create new transforms, without outputs, and create indexes in them, like: alter table `transform_data_1` add index (`column_name1`,`column_name2`)

What have you currently implemented? The first option is to ensure you're properly indexing your inputs as well as your transforms. A second option would be to reduce the number of columns your inputs and transforms have.

This means there are probably more than a thousand or so individual rows coming up in the display. Domo will cut that off since your browser will be too slow when trying to handle it all. It's hard to make decisions looking at a thousand different lines anyway, so you may be better served by viewing a more summarized view.…

No. The beast modes really only work on the card level, not the dataset level. I recommend adding the idea to the Ideas Exchange here as well as submitting it to the product team through your Domo menu feedback option.

Oh, my apologies, you mean the other way around. Beast Modes built on cards and shared on datasets are what they call pseudo columns. They only exist at runtime, not as permanent columns on the dataset. They can't be used in dataflows. But you can basically rebuild the calculations inside the dataflow, too, after all the…

A stacker output is essentially a data table just like any other dataflow output, so you should be able to make beast modes wtih stacker datasets. There may need to be more conditional statements in your beast mode like sum(case when `column` = value ...) than you're used to.

Regex could work as long as there's a pattern with the random character prefix and suffix. Is the prefix always only 3 characters, for example? If that's the case you could just as easily use some substring funtions to extract the value. https://www.w3schools.com/sql/func_mysql_substring.asp Another way to join would be to…

That looks like a bug. There shouldn't be anything special about using that connector. I'm able to grab that calendar without a problem.

Since this is two datasets, it's definitely an ETL thing (probably SQL, not Magic ETL). Like you said, you'd want to review each search by person and product and time window to see if there's a match in the sales records. Pseudo SQL: SELECT search.search_id ,search.user_account_id ,search.date ,search.product_id ,CASE WHEN…

If you're looking to try a beast mode at the card level, instead of a SQL or Magic ETL dataflow to run the numbers, you'll have a bit of nested code. Something like this, which may or may not actually work: CASE WHEN COUNT(`WhseLoc`) = SUM(CASE WHEN `Proj Inventory` < 20 AND `Previous Inventory` >= 20 THEN 1 ELSE 0 END)…

I've done something similar here and I basically created a transform for each aggregated metric, and unioned them all together. There were some datatype mismatching in that first date column and other issues that had to be ironed out, but each row (after the daily aggregations) is simply a rerun of the same aggregations…