Best Of
Re: Smart text not displayed in Powerpoint export
I've had issues in the past with the PPT plugin not pulling smart text properly. I'd recommend logging a ticket with support to have the development team take a look at it for you.
Re: in the Domo workbench, can't separate TransactionDate (date/time format) into 2 pieces
dates and times are still represented as timestamps. If you really just want the text values you’ll need to convert it to a string but will lose the ability to do date operations
Re: prioritize recent data for input datasets in dataflows for preview
I would like to amend this request. Rather than simply prioritizing recent data, as I requested at Domopalooza 2024, I would like the ability to filter the datasets being brought in. Let me hit that 100k row limit based on attributes in the data. This would make dataflows an invaluable tool for tracking down data anomalies and simply understanding the datasets better without having to run the dataflow and check results.
Mandatory Single Select Filter
Hi all,
Is there a way to make Page filter mandatory (so no option to unselect), and only single select? Examples would be if you want to choose the currency to display it in, which target to compare the figures to, etc., but if multiple or none are selected the figures are duplicated.
We've put in a radio button which gets the single select, but it seems bit pointless as it adds the field to the filters bar at the top where they can select multiple options, and doesn't seem like you can make a selection mandatory?
Any suggestions would be greatly appreciated!
Re: URGENT- Please Help: Shopify data connector not working
Has anyone had luck with requesting access to all orders from Shopify?
Re: DomoStats Card Loads dataset - what unit of time is totalDuration?
The totalDuration field in the DomoStats Card Loads dataset represents the total load time in milliseconds for all card loads on a given date. To get the total load time for each card, you need to aggregate this by card ID.
Regarding embedded cards, the DomoStats Card Loads dataset does capture load times for embedded cards. However, this dataset does not include specific URLs from which the cards were accessed. To track which URL the card was accessed from, you would need to implement additional tracking mechanisms, such as custom parameters or analytics tools integrated with your embedded cards.
PRODUCT RELEASE SNEAK: Analyzer Updates
As an active Community member perk, we will be providing insider sneak peeks for the Analyzer features we will be releasing on Monday July 22nd 🥳
Analyzer is where your data visualizations come to life. We understand the value of quickly taking your data and translating it into an easily digestible visual. So, we’ve continued to improve Analyzer with this round of new features.
Context Sensitive Properties: Changing chart properties has never been easier. Now you can simply right-click on the chart itself to change properties like a value on the Y-axis, title, decimal places, min/max, label settings, legend settings, bar chart width settings, and so much more!
Number Input Types: We are helping prevent unintended errors in Analyzer property fields with enhanced input checking and validation for numbers. All numeric fields in Analyzer will no longer accept character entries to save you time and effort trying to identify and fix errors, ensuring clean data inputs.
Quick Chart Re-render: Boost productivity in Analyzer with faster chart rendering when you’ve made a chart property change. Since these changes don’t require fetching of new data, make updates and see them in real time even when connected to very large datasets.
Mega Table Sorting Icons: We are dedicated to making our platform accessible. We are thrilled to share that we’ve made a small, but significant change to our mega table sorting icons. Previously, it was difficult to discern the order of sorting due to the slight difference in the color contrast. Now, the order is clearly displayed with a corresponding number next to a sorting arrow.
Please note these features are subject to change and could lead to a delay in its deployment for an unknown amount of time.
Re: Ability to remove unnecessary columns directly in the input DataSet before loading all its rows
Hi! Just wanted to follow up here. I spoke with our engineering team about this idea, and I learned something new about Magic ETL. Apparently, the reason that the feature does not exist is because it's not needed in Magic ETL. Magic already optimizes which columns are loaded into the DataFlow based on whether or not the columns are used throughout the DataFlow. I'm keeping this idea on my list as something to consider making more apparent in the UI, but for now this is already being solved behind the scenes by our DataFlow optimizer for Magic ETL. Let me know if you have any follow-up questions.
Re: Where is my data going??
In MagicETL you are only previewing 100 rows. I see in the second image that there are 1,737 unique values for the BMI Work Number in your final output data. It appears that the data is there and that there are also null values for that field.




