Comments
-
use a group by tile to combine your field with commas as your aggregation
-
Currently this isn't an option with the HTML table, I'd recommend adding this as an idea to the idea exchange.
-
You can do this with a Magic ETL Group By tile to combine the values with a comma separator.
-
You can use a formula tile and a case statement to set the value: CASE WHEN REPLACE(`City`, '.', '') ILIKE '%st george%' THEN 'St. George' ELSE `City` END You can have multiple different WHEN clauses to handle other scenarios. ILIKE is the case-insensitive version of LIKE where you're matching based on a string with the %…
-
You can’t get access to the current page URL within a beast mode so there isn’t an easy way to dynamically pull it
-
You can write your own connector in Python with the pydomo package to upload data into your Domo instance which gives you more control over how the data is processed but will be a much more technical route. You’ll need to work directly with the Comscore APIs
-
It's treating your 'Repeat' clause in your logical expression as TRUE as it's not 0 value. You need to compare the value again to your field: CASE WHEN `PRODUCTSTATUS` = 'R' OR `PRODUCTSTATUS` = 'Repeat' THEN 'Repeat' ELSE 'New' END
-
The Domo App is used in conjunction with the NetSuite App TBA Connector to utilize saved searches to get your data out of NetSuite.
-
Ad Hoc groups don't have an owner. It's more a kin to an open group where others can add users to the group. You can edit the group type and convert it to either Open, Dynamic or Closed from Ad Hoc but can't change it back.
-
A very unsupported method would be to create a dataflow where you have your input and output with the transformations you want to clean up the data. This will write out to a new dataset as you suggested but this is good for validation purposes. If the output dataset now meets your criteria you can hack the JSON powering…
-
This is a limitation with the Xero API that Domo is utilizing. You need to reach out to Domo Support to have their development team address this.
-
Your format string isn't quite correct. You need something like DATE_FORMAT(`Month of the year`, '%Y%m%d') One concern though is that the months are set to a specific year - is this intended or will other years have the same month?
-
You can use a case statement in a beast mode to conditionally bucket your values CASE WHEN `Compsny` IN ('A','B','C') THEN 'B2B' WHEN `Compsny` IN ('D','E','F') THEN 'B2C' END
-
Domo doesn't have a direct connector for those however you could attempt to utilize the JSON No Code type connector to see if you can get the data that way. Alternatively you can write your own custom connector:
-
Agree with @MarkSnodgrass, FILTER NONE option on a FIXED function will allow you to filter your original data but keep the entire dataset as part of the calculation.
-
Currently the Histogram graph doesn't support this. You could attempt to define your own categories/buckets within a beast mode and use that as your x-axis on a standard bar chart and another beast mode to calculate the overall percentage.
-
Domo doesn't have a Clover connector yet however you can write your own connector using Domo's framework and some javascript. You can read up on how to create your own connector here:
-
Add your DATEDIFF beast mode to your sort section on your card.
-
Likely these demo dashboards are shared with the Default Group that users automatically get added to when they're created. Unshare them with the Default Group and it should solve your issue.
-
You can use the settings on a table card under General > Number of Locked Columns to specify the number of columns on the left you want to freeze.
-
You can use the Date Dimension dataset and join your hours and wages dataset based on the day of the week, then you can use the year and month values in the date dimension dataset to aggregate on a monthly basis.
-
Currently Domo doesn't have an Apache Iceberg connector. It also doesn't appear to support ODBC connection either. You can attempt to write your own connector or utilize Workbench and an ODBC-JDBC 3rd party bridge to convert ODBC to JDBC and use JDBC to connect to Iceberg.
-
Domo functions on a row basis, so you need to have the records in your dataset you need to display. It can't infer values based on a start and end date.
-
You'd likely need to utilize an event on your drop down to store the order in which the values are selected and also handle it when a value is deselected. You could store it in a hidden input type in a form on your DDX brick and then reference it when the event occurs so that you add or remove it out of the csv list you're…
-
That’s what I’m referring to. You see there’s an error where the mapbox token variable is undefined. Have you defined it yet? Also there appears to be an issue with a forEach loop. If you click on the error file name it should show you where the issue is occurring. I’d start looking into both of those errors
-
If you inspect network traffic are there any errors that are being thrown in the console?
-
Whenever I'm doing Period over Period analysis I will structure my data with my own custom date dimension dataset. You can then define how the offsets are and allows you to more easily filter your datasets so that you can look at this quarter but also have records for last quarter. I've done a write up on this approach…
-
DDX Bricks are pre-built with the number of datasets available. You can't modify these. If you're wanting more control over the number of datasets you want to use or their aliases you can leverage a custom app which is similar to a DDX in terms of having an HTML, CSS and JS files but you also get a manifest file to define…
-
Clever @MarkSnodgrass!
-
The Fixed function is returning a single value for each row and you're adding that to an aggregation across your entire dataset so it doesn't know how to handle this. You'd need to aggregate your fixed function again so that you can add the two together. SUM(SUM(DISTINCT Balance) FIXED (BY Client, Item)) + SUM(Received)