Comments
-
It would be best to use the LEFT and SUBSTRING functions to look for those characters since they are always in the same spot. I would write the statement like this: CASE WHEN LEFT(`shipmenttariffid`,2) = 'AP' AND SUBSTRING(`shipmentariffid`,5,2) = 'MA' THEN `shipmenttariffid` ELSE '#' END In my case statement, I am looking…
-
You can use the QUARTER function and the YEAR function eliminate all of your case statement. You could do this: CONCAT('Q',QUARTER(`dt`),' ',YEAR(`dt`))
-
@Jones01 I don't have a good dashboard to test this with, but you can try using the Date Ouput Format field in the General properties of this card and format it to month-year by using this format: MMM-yyyy Try that and see if it will respond that way you want it to. You'll likely have to do a week number format to get it…
-
Have you looked at the trellis chart option? That might work for you. Here are a couple resources. https://domohelp.domo.com/hc/en-us/articles/360043428713-Applying-DataSet-Columns-to-Your-Chart#6. https://youtu.be/hfIUQqeRVkM
-
A couple things you can try, depending on what your data looks like. Try the Grouped and Stacked Bar Chart. KB article here: https://domohelp.domo.com/hc/en-us/articles/360042924574 Another option is to change the chart property that is called "Series on Left Scale", which is found on most bar charts. Changing this option…
-
@jhester yes, the formula tile in magic ETL gives you beast mode functionality within the ETL. You can overwrite existing columns or create new columns. You can find the formula tile under the utility section on the left side. I have created a video that walks you through using the tile that you may want to watch.…
-
I would first try using the formula tile in Magic ETL and wrap the DATE() function around your field. Domo will convert them to the same format and make your field a date field which you can then use in Analyzer. DATE(`Start Date`)
-
Your differing values is because you likely have a client id in multiple locations. For example, if your data looks like this: Your distinct client id count is 3. However, when broken out by location, your counts look like this: Denver - 2 Boston - 1 Austin - 1 Adding those totals up equals 4 because client ID A is in two…
-
@Sam_Donabedian The list of functions in the beast mode editors are inconsistent in the different areas of Domo, even though you can use almost all of them in each area. I have posted in the Idea Exchange to get these consistent to make it clearer for users to know which functions are actually available.
-
Have you tried INITCAP? That function works in beast modes and formula tiles.
-
See how close this gets you: DATE( REPLACE( REPLACE( REPLACE(`Interview Scheduled Date`,'00','') ,'-','/') ,'.','/') ) This still might not work for 100% of your data because it seems like you have rows with 2 digit years in different spots and Domo won't know if that is a year or a day. You might need to try and thinking…
-
Can you post your formula? Wrapping the DATE function around everything should normalize the years.
-
You can wrap a couple REPLACE functions around your field that replaces the hyphens and periods with slashes followed by the DATE function to format these as date. It would look something like this: DATE( REPLACE( REPLACE(`String`,'-','/') ,'.','/') )
-
Did you try the Shopify Quickstart App in the Domo App Store?
-
This is available through the Domo Governance datasets. If you haven't used this connector before, it has quite a bit of information about your instance. Go to your data center and then click on Connectors and search for Domo Governance. You can then choose Beast Modes as a report and it will add the dataset with the…
-
Oh I agree that they should return the 'x'. Just pointing the second way to remove a field for those that didn't know about it yet.
-
A lot of people are not enjoying the new feature that requires the extra step to remove an item. If they don't return the "x", another way to quickly remove an item is drag it away from the field and that will remove it. This is proving to be quicker than clicking on the down arrow and clicking "remove".
-
I assume your cc emails are in one string and separated by a comma or semicolon. You are going to need to get them separated so that you have one e-mail address per row. You can do this with a method that I walk through in this video. In the walkthrough, I am separating out strings of words into single words by looking for…
-
@jaeW_at_Onyx here's a breakdown of how my card is set up that makes it work. I create a "standard date" beast mode field that takes the date field in the dataset that you need to do YoY on and moves it into the current year. DATE_ADD(`datereported`, interval (YEAR(CURRENT_DATE())-YEAR(`datereported`)) year) My year field…
-
I created a video that shows how you can create a standard date, which then allows you to look at different years next to each other. My video uses a line chart, but you can switch to a pivot table and format the date fields as needed to get the look you want. https://youtu.be/mDwSQGAjIrs
-
Totally agree with you. It's a bit unfortunate, but I try to limit how often I edit my published dashboards because I can't go around making sure every child instance received the refresh properly. I'm hoping they will continue to improve the process and I can regularly make changes to the dashboard and not be so reluctant…
-
@Jones01 I will often edit the publish job and click through everything to make sure everything is properly selected and then choose refresh after that is done. I don't completely trust the numbers that show the number of datasets, pages, cards and subscribers. Mostly because I know my subscriber count is incorrect (mine…
-
I have found that I have to wait 30-60 minutes for a child instance to see the changed charts after the publish refresh job has told me that it is finished. Domo also recently implemented targeted refresh, so it is worth double-checking that all of the appropriate child instances are targeted when refreshing. Hope this…
-
You can use the formula tile and the concatenate function to build your ratio string like this: CONCAT(`Usedfield`,':',`Newfield`) This would build your string.
-
@moneyshot glad I could help!
-
Do you not have a date in your inventory table? You can always add a date in the etl process, such as the first day of the month. There are several different ways you can derive a date dynamically depending on your data. You can give it the same column name as your orders table date column so that the filtering will work.
-
A second option is to not join your data in the ETL, but union your data with the append rows tile. Choose include all columns when appending. This will keep your inventory rows from repeating and then you should be able to use SUM(orderqty) / SUM(qtyavail) to get the percent sold.
-
You can get around the fact that the qtyAvail is repeating by using the average function in your beast mode like this: SUM(orderQty) / AVG(`qtyAvail`)
-
No, your sum would be your sales amount column, not the date calculation. What does your data look like? Do you have one entry per day? One entry per week? That will make a difference in the lag.
-
In your OVER clause, you should be able to add ORDER BY and list current run DESC, total current run DESC so that it will sort by current run first and then total current run after that.