Comments
-
That's correct. Any time a card is loaded, filtered or modified it's issuing a new query into the database and since you're using a federated connection that's a new query to your database each time. More cards means more queries to your federated database.
-
Due to design decisions by Google the exported data won't align with the exact numbers from the UI. It will show you the same directionality of you data however. Here's some helpful articles on GA4 and sampling:
-
I'd recommend reaching out to Domo Support and logging a ticket if their documentation isn't lining up with the actual steps you need to take to get it configured. PlayVox's API documentation appears to be a bit light on the specifics of API authorization.
-
New values would need to be manually collapsed. I'd recommend adding an idea to the idea exchange to allow a setting so that all groups start collapsed as doing this manually for many different rows can be tedious.
-
You'll want to utilize PDP so that each user can only see their respective data. Here's a helpful KB articles to get you started:
-
It sounds like you want to pivot your data. You can utilize a magic ETL and a pivot column tile to change the structure of your dataset. You can refer to https://domo-support.domo.com/s/article/360044951294?language=en_US
-
If your decimal is the number of seconds you can use the SEC_TO_TIME function or convert your minutes to seconds and then use the function I’ve posted about formatting time differences which may be of benefit to you
-
Thanks everyone!
-
Due to how variables work the variable won’t remember the value you selected for a prior value of the variable column. I’d recommend adding this as an idea in the idea exchange
-
Typically when I'm looking to do something a bit different between with PoP charts I'll create my own date dimension with custom offset information. I've done a write up on this here: This method will allow you to filter for only Q4 and show the differences between the prior quarter.
-
Are all of your dates in ISO format? Did you previously write to the dataframe with the dates still formatted as a string? Have you tried writing to a brand new dataset?
-
@muhammadtalha - This was likely done using either a custom app or extending an HTML Domo Brick that Domo provides. Here's a link to the "HTML Links Dropdown Brick" that Domo provides (replace [YOURDOMAIN] with your domain or search for HTML Links Dropdown Brick in the app store…
-
data_import_from_file only supports CSV files. If your data in a structure other than a non-tabular format? How does the format break?
-
Domo also has a handy graphic on helping to choose different chart types depending on your data. You can reference it here:
-
You can keep the format as xlsx I’m just recommending making a copy of the xlsx as a csv and uploading that copy
-
You can change the aggregation in the field properties of your fields you added to the chart. Here is a KB article for reference https://domo-support.domo.com/s/article/360043429573?language=en_US#totals_subtotals_individual_columns
-
Currently there isn’t an option to have workbench do this do your script is still needed. I’d recommend adding an idea to the idea exchange to add this enhancement to workbench
-
Graphing by week or month would cause duplicate records to display with the window function because the date slice is different than what you’re ordering by.
-
You should be able to set up different alerts filtered to different users and then assign those alerts to those users. Then you can do the same but change the criteria to be two weeks for the Manager version. You could combine all of the individual users for the manager and just check if there are any greater than 2 weeks
-
You can utilize python packages such as pandas to read the excel file and convert it to a csv and then upload it to Domo that way.
-
There isn’t a way that Domo provided to drill into a card programmatically. I’d recommend adding this as an idea to The idea exchange It may be possible to utilize some low level JavaScript and DOM inspection but it’s a very technical route and I haven’t done it myself yet but just an idea
-
Have you tried utilizing <br> instead of \n? Is it actually displaying \n or just not doing a new line?
-
Have you validated the data you're getting back from your SQL query? Is it returning all of the data you're expecting?
-
This sounds like a bug as per the documentation: Workbench creates a log table with the same name as the DataSet name mentioned in the Overview tab. I'd recommend logging a ticket with Domo Support to have them help diagnose your issue.
-
If you're looking to add raw data to your dataset within a table card that isn't possible. You need to use an ETL to transform your data (i.e. adding rows in your case)
-
My favorite vacation was in Bryce Canyon hiking with the family. It was an amazingly beautiful place and a lot of fun to get out and go hiking. Going to Lake Michigan is always a fun weekend retreat to spend some time at the beach.
-
FIXED would allow you to restrict the filtering however ranking isn't possible with a FIXED function because it doesn't allow an ORDER BY clause. Regular window functions are affected by filtering. I'd recommend adding this as an idea to the Idea Exchange
-
Have you tried taking the CASE statement outside of your FILTER ALLOW clause and surround your entire fixed window function in the CASE statement based on the variable?
-
Currently there isn't an option for this however I'd recommend logging an idea in the Idea Exchange for others to vote on it and perhaps have Domo add it.
-
Currently this isn’t possible but may be in the works. There is an idea exchange post requesting this functionality you can upvote here: and also https://community-forums.domo.com/main/discussion/57808/reuse-beast-mode-field-in-another-calcuation#latest