Comments
-
Whoops, sorry @AndreaLovesData I have my terminology incorrect, I mean "include all columns." Often changing one of the inputs for an append will switch it back to "only include columns from Dataset 1." Or I'll append a couple things together, run it, only to find it included some of the columns.
-
CONGRATS @MarkSnodgrass !!!
-
Holy snap this is amazing @AndreaLovesData!!
-
100% agree with @marcel_luthi, this would be a great thing to add to a dataflow. Do a group by by Job, add it back to the job as a "Job Total" hours and then you could even add in the classification to the job level as well. Well worth it to spend 30 seconds in a dataflow vs. trying to create a crazy beast mode.
-
Hmm, I feel like that's an oversight and should be on there. Maybe ask Domo support? I don't think there's a way to change that setting.
-
Yup, @GrantSmith is correct. The bundle is used with the TBA connector to pull saved searches. If you have SuiteAnalytics Connect, you can use that and just write queries in the connector - that's my preferred methodology from both a performance and usability viewpoint. I've connected Netsuite to Domo about 30 times for…
-
It was me speculating - but usually systems that require MFA have an "app password" you generate. Is there another way to authenticate to TradeDesk?
-
I don't have experience with Trade desk specifically, but most connectors don't support MFA and you have to create an app password or use an account that doesn't have MFA.
-
This is extremely cool, great work @Jonathan53891!
-
You might be able to use the API or use an alert to hit team's JSON, but definitely not a simple task. Could you use PDP and email the report?
-
Ah good callout, I would use DISTINCT there.
-
I know when doing it on a card you need to the ` to the fields like pfilters[{%22column%22:%22JobNum%22,%22dataType%22:%22STRING%22,%22operand%22:%22IN%22,%22values%22: [%22',`JobNum`,'%22]}]">',JobNum,'</a>') but not 100% certain if you have to do it in embed.
-
In the dataflow you can convert it to a decimal, or in an beast mode on the card you can do "column * 1" that will convert it. Does it have dollar signs or commas in? You might need to remove those first.
-
My go-to troubleshooting method for this is to put a static value in for your field, to determine where it's erroring out. Can you rename the column (or try another column) temporarily and see if that helps? I could see the period causing issues
-
Depending on your data, you could a beast mode that's like case when count(product) = 1 then 'Show' else 'Hide' end and then filter the card to "show" and it should only show data when 1 product is selected.
-
Without more detail, our standard practice is in the dataflow to copy the rows of data, roll them forward a year and mark them "Prior year" and the original "Current year." This way on the card you can set it to "Current Month" and then use the "prior year" vs. "current year" flags to determine the difference but the card…
-
"Unique" metrics have to be pulled in the date grain you want, since if you have 3 unique users each week of the month, when you try to SUM the month it will give you 12. However if you pull that report for the month, it might only return 3.
-
Are your date dimensions the same? The GA4 connector aggregates it based on the date grain you select, so if in the connector you're pulling daily and trying to aggregate it in Domo, it might not match. Trying pulling at the same grain as the GA4 report and see if it matches.
-
On standard dashboards, no. But App Studio has some theming/branding options that can accomplish that once that drops.
-
If you turn off segments on the dashboard does that remove it?
-
Do you mean like the link to the Domo everywhere page? I believe it stays consistent unless you publish/unpublish it. Even then it might persist.
-
I believe it does, or will eventually mentions OpenAI, HuggingFace, Bard, SageMaker, AutoML and Jupyter.
-
What happens if you try a different browser?
-
If you switch it to a table card, do you see employees? Otherwise the issue might be with your aggregations, I don't think you need them if each employee has those columns on them.
-
Natively, no. But you can build a dataflow using the Domostats/Domo governance datasets that links the page to the card and then the card to the dataset.
-
Based on the error, it looks like "set_manual_login" isn't a valid object in DomoDeveloperAuth. Have you tried the "url_manual_login" like it suggests?
-
I think you could do that in the metadata, if writeback connectors appear in the dataflow tables.
-
Have you tried sharing the dashboard as a slideshow? I have clients using that on TVs. The "Publish as a Slideshow" option
-
The other thing I've done is in a dataflow just appended a date dimension so there's a "row" for each date, even if there's no "actual" data. Only caveat is you need to make sure your blank date rows match your card filters otherwise they won't help.
-
DDX Brick is the way!