Comments
-
I would look into the custom charts option that is available. Here is a video about it as well as some KB articles: https://domo-support.domo.com/s/article/360043428793?language=en_US https://domo-support.domo.com/s/article/360042924454?language=en_US
-
Here's a video on how to split values dynamically when you don't know how many times you will have to split.
-
@trafalger just did this. He may be able to explain how he did it. I believe it required some programming within Code Engine to accomplish it.
-
If you click the wrench and choose Edit Drill Path there is an option to prevent drilling to the raw dataset.
-
Since this is a beta feature, I would recommend providing feedback to the beta team to let them know about this issue. Betafeedback@domo.com.
-
@GrantSmith is the king of API calls and may know if this is possible.
-
Agree with @MichelleH . Here is a video that walks you through it.
-
You can have multiple workbench installations, but having them run the same job would be problematic. I would recommend reviewing this KB article about migrating Workbench to help better understand what to watch out for. https://domo-support.domo.com/s/article/000005219?language=en_US
-
Try this: CONCAT(LEFT(TicketOwnderFirstName,1),TicketOwnerLastName)
-
-
Actually, a fixed function might be easier your region total fixed function would look like this: SUM(SUM(Value)) FIXED(BY Region FILTER DENY Team)
-
Segments would be the easiest to implement since you can base it on region, but you would likely have to create a segment for each region and they will always be showing. I think you will have better luck if you use a variable for your team selection instead of a filter. You can then build a beast mode that is for your…
-
Here is the video that is referenced in the earlier post.
-
After you select the checkbox "save calculation to dataset" you need to then click on Create Calculated Field, which will then change to Save Calculated Field, which I tend to click on as well before clicking on the X to be sure it is properly saved.
-
Did you check to see if the text formatting - only show number tile kept your decimal place? I believe it will remove that as well which will be problematic for you. I would suggest using a formula tile and then using two replace functions (one to remove the dollar sign, and the other to remove the commas) followed by…
-
In your ETL, before joining the two datasets, I would do a group by on dataset B and group by productid, orderid, and customerid. You can just choose count for the aggregate and pick any column. This will give you 1 row per productid, orderid, and customerid. Then do the left join as you already have in place. Also, if you…
-
You would want to talk to your CSM to go over your particular contract, but generally speaking, federated datasets themselves don't use any credits.
-
If you are statically setting the filter and will have to change it each month you should be able to do it dynamically by creating a beast mode that looks something like this: CASE WHEN datefield = MAX(datefield) THEN 'Include' ELSE 'Exclude' END Drag this beast mode into your filters and filter to Include.
-
I would try this: DATE_SUB(datefield, INTERVAL 52 WEEK)
-
The only way that I can think of making that work is by creating rows in your data with a value of 0 for each category/filter combination. You can do this pretty easily in Magic ETL if you are not able to do it directly in your source data.
-
The pull connector needs a username, password and hostname. See this documentation for more details. https://domo-support.domo.com/s/article/360042931894?language=en_US
-
You can do this by first adding a filter tile and filter to where id is not null. Then add a group by tile and group by max id. This should give you one record of 12 and 56. Next, add a join tile and join your original input dataset with the group by tile and join on the customer column. Finally, add a formula tile and use…
-
I would guess that the issue is because you are only aggregating on one part of your case statement. Try putting AVG() around your 'Within SLA' field in your case statement and see if that helps. You could also try it like this: AVG(CASE WHEN PRODUCTIONBY <> 'NPS' AND SLAStatusAverage <> 'Within SLA' THEN DAYS_CUSTOMERVIEW…
-
@joebenz Domo does support SFTP. I used it quite a bit. You can have the vendor push to it, or you can have the Domo connector pull from their SFTP site. Most vendors prefer to push to Domo. The issue tends to be that vendors are used to a PGP key and not a PEM key. PEM keys can be converted to PGP by the vendor. This KB…
-
I don't believe there is a specified limit on how many variables you can use on a card/dashboard, but I doubt much testing was done on having this many variables being used when the functionality was built out. I would suggest logging it as a support ticket.
-
Even though your e-mail has multiple files, you can set up multiple forwarding rules and use the dataset via e-mail connector to handle each file. You can use the attachment name expression field to differentiate which file you want to connect to. Check out the documentation in this KB article.…
-
I use Domo Workbench to directly query a SQL Server. You just need to create an ODBC connection on the computer running Workbench and then use that connection to your SQL Server. https://domo-support.domo.com/s/article/360042932734?language=en_US
-
If it is always between the first and second underscore, you can do this: SPLIT_PART(fieldname,'_',2)
-
Webforms can only be input datasets. They cannot be output datasets. You could use a webform as a second input dataset that could overwrite entries by joining it to your app studio form dataset in Magic ETL, though.
-
You can remove the by Month by editing the dashboard and click on Edit Content on the card and choose Appearance and uncheck Timeframe.