ellibot Domo Employee

@b_rad you can also set the dataset column width to be much wider for these kinds of datasets using the Java CLI. I made a video on this if you're interested: https://www.loom.com/share/bae9e2cf25a7479398d1c6d49e38747b

@verytiredgirl I normally will just select all to delete every column, then choose the 25 I want to add back:

https://us.v-cdn.net/6032830/uploads/0UKBDEWE520O/duplicateuser.txt @Abby Brinks this is a JavaScript code engine. Let me know if you encounter any issues!

@Abby Brinks one current workaround is to create a workflow that is responsible for triggering the refresh of the DomoStats connector. The timer trigger allows you to run the workflow only on weekdays:

@Abby Brinks I actually just created a custom code engine function to duplicate a user I'd be happy to share with you. It looks at the user you selected and then creates a new user with identical permissions (same role, same access to pages/cards).

@jpotter I think there is a command in the Java CLI that lets you adjust the character limit for a specific column. Set-dataset-column-width

@Data_Devon do you have Domo projects and tasks enabled in your instance? I think Domo built this feature to solve your exact problem. https://domo-support.domo.com/s/topic/0TO5w000000Zao5GAC/projects-and-tasks?language=en_US

@brentsickmiller @ARosser @AsimBaig @CBrowne Apologies if you've already tried this, but have you tried to manually sync the collection using the API? I have a code engine function that does this, and I just tried it and it synced the collection to the dataset successfully. Could be worth a try? const codeengine =…

@ARosser have you looked at AppDB admin to make sure the sync is turned on? https://domo-support.domo.com/s/article/9221297758615?language=en_US

@SharonB_CF I believe Google Analytics actually samples the data if you pull using their reports api (which the domo connector uses): https://docs.cloud.google.com/looker/docs/studio/google-analytics-4-sampling To prevent sampling, you'll need to export your GA4 data to BigQuery:…

@JimChan I believe you can already accomplish this today using chart properties. Go to Grid lines > Zero line color and width.

@MackenzieConner when you say export, are you just wanting the visualization of the app component? Or the underlying data? Have you already tried the new report builder in app studio? I was able to get it to send me an app studio with an app component on it, but it was just the visualization.

@KandiKraner have you tried adjusting the app studio layout's mobile view? The mobile layout can be independent of the desktop layout. Here's a KB article on how to do this: https://www.domo.com/docs/s/article/1500010172542

@zacpolin as you've expertly outlined, there are a TON of ways to distribute data via Domo to external clients. If you don't already have your own web app/portal, the easiest way (in my humble opinion) is to create subscriber instances and publish the required data using a publication (here's a KB article on how to do…

@Sailaja_Lokasani if you're wanting to call an external API such as Grok, you'll need to use a Code Engine function as a proxy in order to avoid the CORS error. Here is documentation on building a code engine function: https://www.domo.com/docs/portal/Automate-Actions/Code-Engine/overview

@verytiredgirl I believe unioning is possible in dataset views, have you tried this route yet? It could require the advanced SQL editor. Full disclosure: I have not tried this but have heard others have been successful with it.

@mariobutler here's another discussion showing how to do this in app studio: https://community-forums.domo.com/main/discussion/66868/get-rid-of-filter-icons-in-app-studio-apps It definitely is a bit confusing since the interface is different from traditional dashboards.

@jamesj I believe this is actually already possible today using the Java CLI. This video walks through how you can do that: https://youtu.be/kHSeSbSFS1Q?si=UulS3Ct0MWAi97UC

This would be super helpful! Definitely agree there are many times where I would like the legend to be hidden on the app studio, but still showing if the user maximizes the card.

I also wish I lived in Chicago 😔

@verytiredgirl Flex tables can be tricky to configure, but once you have the formatting down, they are incredibly powerful! I think we have a few working examples of how to configure them in our community instance: https://domo-community.domo.com/page/96678585/kpis/details/2095209419 Feel free to send me a message if you…

Nicely done @GrantSmith! You continue to teach us thing year after year!

@Jbrorby you can actually run DomoStats connectors more frequently than daily. The easiest for me personally is to set up a quick workflow that has a timer trigger (for example hourly) and a single action called "Run Connector" which is a native Domo function.

@hayashida definitely agree that having an UPSERT connector would be great. Have you looked at leveraging NSAW for your use case? Using Domo's new cloud amplifier connection for NSAW, you can query live data from your NetSuite instance and it's extremely performant.

@KristinDavis BQ supports using wildcards in their SQL, so you can create a view on the BQ side that unions all the tables together. The SQL would look something like this: SELECT PARSE_DATE('%Y%m%d', event_date) AS date, COUNT(DISTINCT user_pseudo_id) AS total_users, COUNTIF(event_name = 'user_engagement') AS…

@James_Lord as far as I'm aware, you can only suppress public embed as a global setting in your instance.

https://us.v-cdn.net/6032830/uploads/Z5T4H1KOK63J/codeengine.txt @Martin_deLeón take a look at this markdown file. My understanding is that you alias the code engine function in the app manifest.

I will make sure to find you during one of the days, gotta make sure I meet the legendary @Data_Devon in person!

@SayyedHussain you can absolutely rank based on another column in the dataset, you would just adjust the order by clause. Rank needs a column to determine the ranking. In your screenshot, you could order by one of the value columns you have in the dataset.