Best Of
Re: Count Attribute Instances instead of Projects
@PJG What does your data look like? Do you have one row of data per project? Or one row per go live date? When you summarize your data, are you using Count? or Count Distinct?
Re: Feedback Survey data from Hubspot into Domo
Hi @JoshBethers
It appears that access and the APIs for the feedback survey data are in Beta only so it's likely Domo doesn't have access to this endpoint yet. You could attempt to join the beta and pull the data yourself and upload it to Domo with a custom connector or the Domo APIs.
You can find more information on these HubSpot APIs here:
Re: Can I combine columns to create one column for a pie chart/bar graph visual?
You can use a dataflow / magic Etl to pivot your dataset so that you have the columns member and event and signed up and then filter for signed up = TRUE
You can then use that output dataset in your pie chart with the event as the series and do a count of the members
Re: Dashboard Page Filter bar - limit the filterable columns
Hi @Seth ,
One thing you can do is just make a card as a filter and then take out Admissions_email as an option in dashboard 2.
I made you a video to show you:
Re: Cleaning data off an appending dataset
You could use the Java CLI tool to do this, but it would likely be a manual approach. I know you want avoid creating an ETL, but creating a simple Magic ETL with a filter tile that looks at the current date and the date field in your dataset would be an easy and dynamic way to filter out the older data.
Re: Cleaning data off an appending dataset
Have you thought about using a Magic ETL dataflow to have your dataset as an input and then filter the data so you don't have historical then output it to another dataset making it update on a daily schedule? Once that's in place you may be able to extract the dataflow definition with the Java CLI, change the ID of the output dataset to be your input dataset in the definition, and then upload the new definition to your dataset.
This isn't really officially supported but may let you remove the historical data from your dataset on a schedule.
Re: Not getting GA4 data to reflect accurately in Domo
Google restricts the amount of data it will pull in the APIs due to performance reasons. If you limit your request to a small enough dataset it will return everything, otherwise GA will return a sample of your data. You may need to pull data for a specific day to reduce the size and have GA return the entirety of your data.
Re: How can I get vertical scroll bars on charts?
@PJG I don't think this is possible using a Gantt chart. If you want to make such a large Gantt chart more readable, I'd suggest setting up quick filters with certain values pre-selected so that the card defaults to the most relevant view (i.e. Task Status, Current Project Phase, Task Assignees, etc.)
Understanding PDP, DataSets, and DataFlows
I've finally had a look at PDP as I need to retrofit a page with dozens of cards to filter the data on display for specific users and user groups. When I'm learning something new, I usually read the docs, try it out, and make junky little sketches. If I can't make a sketch, I definitely don't understand what I'm looking at. On the other, just because I can make a sketch it doesn't mean that the sketch is right. I figured this would be a good time to ask a few conceptual questions about PDP, DataSets and DataFlows and, hopefully, deepen my understanding of how Domo functions internally.
First up a Terrible Little Diagram for a DataSet with one filtering PDP policy:
As I understand it, PDP policies apply to a specific DataSet, so they can really be thought of as a property of the DataSet. I illustrated it as above as 1) it makes more sense for a policy to stand on its own and 2) we'll end up making redundant policies as a matter of course as Domo doesn't support policy sharing.
What I'm not sure I've gotten at all right is the box labelled "Virtual Filtered DataSet." Is that about right? I have the impression that a DataSet is rendered/indexed/stored within Domo and that a PDP filter is a runtime/dynamic operation. I got this idea after trying to map out the DataFlow behavior:
According to the docs, a DataSet with a PDP policy cannot be used as an input to a DataFlow, but an output DataSet can have PDP policies attached. If DataFlow outputs are fully rendered DataSets that are saved and indexed, and PDP policies are only applied dynamically at runtime based on a specific user context, then this all kind of makes sense. Hence the "Virtual Filtered DataSet" in the diagram.
But I could have it all wrong, I have no idea. Does anyone know about these points:
- Are DataSets parsed, stored, and indexed during import?
- Are DataFlow output DataSets parsed, stored, and indexed during DataFlow run/update?
- Are PDP filters only applied at runtime? Meaning there's no serialized version stored in advanced?
If anyone's got some info or insight, I'd love to hear about it. I'm not sure that I can claim that the information will do me any specific good right now, but getting a more fully developed mental model of how Domo works will definitely help me going forward.
Thanks
Re: Beast Mode Calc for URL Won't Activate Intranet Links
Hi @user028768
Try wrapping your values in double quotes:
CONCAT('<a href="', `Link to Additional Info`, '" target="_blank">Click to see additional info</a>')
Also, what type of card are you using? Hyperlinks will only work in table cards.