-
Indicate in the UI when a dataset ID is being used in an API or writeback EXPORT
Simple idea with a profound impact. Indicate in the datacenter/dataset UI that a specific dataset is being used in an API or writeback EXPORT
-
bricks that can be edited by more than one user
Currently DDX Bricks can only be edited by the creator of the "App" This is by design, and can be found documented in the "Getting Started with Domo Bricks" article. idea: make DDX bricks editable by all owners and admin, and allow the checkbox on card details to restrict access to non-owners.
-
Some content is too tall to export
Trying to export a dashboard with lots of cards to a PDF. The PPT download won't hold dashboard filters when exported. The email scheduled report does not send the entire dashboard only part of it. What are users doing as a workaround for exporting reports to external (non-domo) users. This is all robust financial…
-
Json No Code
Is the Json No Code connector OAuth 1.0 or OAuth 2.) The knowledge base article does not specify.
-
Domo is ready, but Instagram reported an error: This endpoint has been retired
Instagram connector stopped working I have a Instagram dataset connected into a recursive dataflow it runs multiple times a day and appends each row. Today the connection stopped working with the following error code "Domo is ready, but Instagram reported an error: This endpoint has been retired" I am using both reports: *…
-
Error with report | hubspot contact lists with lifecycle stages
I am using the hubspot connector and I'm not able to generate "contact lists with lifecycle stages" Getting an error: "Domo is ready, but Domo received an error requesting the data. (Bad/Malformed Request)." Report Returns contact lists with lifecycle stage field.
