KurtF Contributor

Since my first response, new functionality has been added to Magic ETL for this. You can use a Rank & Window tile. Check out the documentation at this link: https://knowledge.domo.com/Prepare/Magic_Transforms/ETL_DataFlows/03ETL_Actions%3A_Rank_and_Window At a high level, you will use the Rank & Window tile to create an…

In SQL syntax we write this as follows: CASE WHEN `Alpha` IN ('A', 'B', 'D') THEN `v-Inefficient` WHEN `Alpha` IN ('C', 'E') THEN `v-Efficient` END This should do exactly what you are looking for.

How do you know which row pertains to a particular date? It's possible you could write a BeastMode that executes CASE statements against another field to generate a date value.

I don't think you need to put the three fields into a single BeastMode. If your Series field is numeric you should be able to drag more than one into that space within the Analyzer. Try dragging each field separately into the Series space. You may need to select an Aggregate option of SUM to be able to drag the subsequent…

Whenever you are combining fields in a Summary Number it can get complicated. Here is link on how to handle font size via HTML tags: https://dojo.domo.com/t5/Beast-Mode-ETL-Dataflow/How-do-I-change-font-size-for-summary-number-display/m-p/23226

When you concatenate values together MySQL treats them all as text. That's why you lose the automatic formatting of numbers that Domo usually does for you. You would have to format the number as a string with the commas inserted in the correct spots and then concatenante together. This will be tricky to do based on how the…

I think I would approach this by bringing both datasets to the same date grain before the join. In Data Set 1 SUM up all the the hours in the month by employee so that you have just one row per employee per month. This would be my prefered method. Alternatively, you might try something like this: SUM(`Hours Logged by…

It doesn't look like that is actually a date field. If it is concatenanted month and year then the Analyzer will not treat it as a date. You will need to write a BeastMode to format this as a date (which might be a little tricky). It would look something like this: DATE( CONCAT(LEFT(`Dimension.MONTH_AND_YEAR`,2), '-01-',…

In order to do annotations the x-axis has to use a date value. Most often when the Annotations option is grayed out it's because you're not using a date field. Can you confirm the data types being used in your card?

If I'm understanding you correctly, you could add both the current row score and the lag row score to the final dataset using the dataflow. Then create a BeastMode calculation to subtract one from another. You could then filter on the BeastMode value not equal to zero.

You might add a Lag function to your dataflow to get a prior user score. Then calculate the difference between a row and its precedent. You could then add a filter to the card that displays only when that calculation is not equat to zero.

If Allow Text to Wrap does not resolve the issue then you might try the Full Size Settings and select a width and height for the card. Then after you save the card select the Full size option box. You can make adjustments and try out a few different height and width settings until you get what you need.

Can you post a screenshot of what the result is? If the users have an individual score on each day you should see their score on each one of those days. I don't think I'm totally understanding what you would be missing so I'm hoping the screenshot will help me.

This is an awesome suggestion and it's something that is available in several other toolsets. You can "disable" steps to prevent them from processing. It's kind of like commenting out code in your SQL. Any chance we could get this on the roadmap for Magic ETL?

It looks like you may be trying to add a dataset to a pre-existing dataframe within R? If that's the case, it looks like the number of columns (and perhaps rows) is different from what R expects them to be. Try the command: newdf<-DomoR::fetch('[dataset_id here]') Does it create a new R dataframe that you can view within…

It looks like maybe not all RegEx is created equally and the language the RegEx is implemented in can require slight variations. I found this thread on Stack Overflow that shows a couple different variations on it. Magic ETL may be using javascript in the background or it might be something else. Try a couple of those…

It looks like for multiline RegEx you may need to add '/s' at the end of your expression in order to ensure all lines get searched. It's also possible that you'll need [\s\S] Let me know if either of those helps.

Here's how I would approach this. Ideally, you would have your Salesforce dataset configured to Append when it updates each week. Use your Salesforce opportunity dataset as an input to a Magic ETL dataflow. Connect the input dataset to an 'Add Constants' widget, create a new constant column called ReportDate, select Date…

That's how I would approach it. You would do an outer join of the person list with your dataset that has your actual results. Depending on how you approach that you may have some persons in the final dataset with NULL values. You can always create a BeastMode to set the value to zero if there is a NULL there. CASE WHEN qty…

I believe you would need to do this within a data flow. You would want to add a column to the dataset that includes the total for given category. For example: DateEmployeeGroupActual HoursTotal Group Hours6/21/17JillCustomer Service6.5436/21/17BerniceSales7456/21/17JeffSales7.2545 You would need to create a branch in your…

What does your underlying data look like? Is there a row with a person's name and a NULL value for that person for a given week? Something like this? DatePersonQty6/21/17Joe56/21/17Jill 6/21/17Bernice1 Or is there just not a row for the person during the week you want their name to display a zero for?

I'm assuming you have a series selected. You could probably create a BeastMode for each of the series members and then create one that contains the average. I think it would look something like this: Brand A SUM(CASE WHEN `Dimension` = 'Brand A' THEN `Metric Total` ELSE 0 END) Brand B SUM(CASE WHEN `Dimension` = 'Brand B'…

Thanks for the question, TC. Once users have had the card shared with them they should have access to the dataset. You should be able to remove the card after that point so that it doesn't create additional clutter. There isn't really a setting in Workbench that will affect this that I know of. Please also see this idea…