ellibot Contributor

@Data_Devon maybe try one of these styles and see if it renders

@joebenz it looks like it might be an error with the Hubspot user you're using to connect the Hubspot writeback connector. Is the user an admin in Hubspot? I'm guessing you'll need to be an admin in the instance.

@b_rad here is the code engine block I wrote to update the default date of the variable. This can be called in the workflow. You will pass the variableid as a parameter.

@andyhicken here is a help article that explains dynamic PDP using key attribute of the subscriber instance:

@MasonW you can also use the CLI to export the JSON definition of the dataflow using the 'list-dataflow' command. This could be automated through scripting if needed.

@sjh Hey there! While there isn't out of the box functionality to achieve this right now, you can accomplish this using a Domo brick with a bit of custom code. I'm actually currently working on a video tutorial demonstrating how you can do this. If you want to keep it simple, I like your idea on creating a separate…

@Malvika_Chauhan09 I believe that data also resides in the JSON that is returned. Here's a screenshot I took from the video showing the specific warehouse:

@kylemcmahon I don't think there's a connector for Google reviews, but it looks like you can pull reviews via Google's API:

@thaddeusbudde A current workaround for this would be to use the JSON no-code connector to create your own DomoStats report to show who all is subscribed to an alert. If interested, you can hit this endpoint GET https://domo-community.domo.com/api/social/v4/alerts?all=true&fields=all&limit=15&offset=0

@art_in_sky looks like it's currently not available for public embed

@STEVE T you may be able to update the variable automatically using a workflow like so:

@Malvika_Chauhan09 a current workaround for this is to create your own Domostats report like so:

@Kunal @dnewc @EhubMcCoy @JasonAltenburg @BryantCafferty take a look at this tutorial video:

@manojshipwire @jimsteph it looks like you can get the query that powers the domo dataset by hitting this API: GET https://{{instance}}.domo.com/api/data/v1/streams/{{streamId}} The Stream Id for connectors can be found in the DomoStats Dataset History report.

@AO3 there should be a control button that you can add to the app in the top-right corner:

@froghunter for most Domo connectors, you are able to pull in 1 table from the source system per connector. So if there are 5 ServiceNow tables that you need to pull you, you would create 5 separate connectors for each table.

I've also used Portable's Workato connector since Domo doesn't currently have one:

@Larry_Goodwin I have used the JSON No Code connector to pull Workato data from their admin. Their API docs are super helpful: . Authentication is super easy, just need to generate an API key.

@ColemenWilson There is a command in the Java CLI called 'restore-card' that lets you add a card to any page in Domo. You can probably script it to find new pages created and then add the card legal wants

@sebastian_galindo since this is a product API (not a public API), you will need to authenticate with either a session token or developer token. Here’s a tutorial video on how to do that:

@sebastian_galindo take a look at this product API:

@akeating as a workaround, it looks like there is a product API you can hit that will return a list of your subscriber organizations: GET https://{{instanceName}}.domo.com/api/publish/v2/controlcenter/subscribers?limit=200&offset=0

@ColemenWilson it looks like the Activity Log API might provide information about proxy logins, so you could theoretically create your own DomoStats for this info:

@Mwatson do you know if Clickup can generate an iFrame for the form? I feel like most project management platforms have a shareable link for the form. If so, you can use the iFrame Domo Brick to embed it into a dashboard: . You'll just need to change the URL of the iFrame in the HTML tab to the one Clickup provides.

@GrantSmith any creative workarounds for this?

@luoqianhe this video might also be helpful too:

@DomoDork did you fill out this section where the client id is the username and secret is the password?

@trafalger