Best Of
Data Export an Embedded App Question
Hello,
I had a question about the DOMO App Studio. Traditionally we have embedded DOMO dashboards into our customer facing app. We have always used public embed on the dashboard and relied on our company app for user authentication and login. We also do not use and PDP or row level filters in our DOMO dashboards. This allowed our customers to export the underlying data.
I rebuilt our customer facing dashboard in app studio and I embedded it within our company app, exactly like our previous DOMO dashboard. My issue is that when accessing the new dashboard as a customer, I am unable to export data behind any visualizations even when the App is embedded as public. Inside the app within my domo instance I can select a card and embed it as public, but that still does not work, and within the "public embed" option there is a warning stating "Making this Card public will allow anyone on the web to view it and the displayed data. It also gives Domo permission to publish the Card as part of a public Card newsfeed. Do not choose "make public" for any Card that contains confidential or personally identifiable information" which makes this option a non starter, even if it worked.
Is the only way to embed an App, having the same functionality of a traditional dashboard, assigning security protocols through the DOMO admin center?
Any help on this would be greatly appreciated.
pshull
Re: Sharepoint Connector - Error rectifying Excel File
Yes, the error indicates there may be an issue with processing the Excel file. If you are sure on the location, name, tab names, and such…you might check formulas, file size (too large?), corrupt file, permissions, etc.
Can you test with the copy of the file without formulas? Copy the Excel file contents and paste back down with Paste Special > Values. And then see if that works to indicate whether formulas are the issue?
Re: Data Export an Embedded App Question
@LeeJo I was browsing the slack channel and came across this https://github.com/clearsquare-dev/open-source-domo/tree/main/ddx-bricks/export-btn
Provided by @MattTheGuru
Here is a link to the slack thread. It’s not a perfect solution for my use case, but we would have implemented it if I had this data 2 months ago.
pshull
Re: Making geojson and display it on Google Maps on Domo?
there are several mapping JavaScript libraries you can leverage inside of a Domo Brick. If you search the App Store for Domo Brick and map box there are ones you can modify. I’ve leverage map box as it allowed me to upload my geojson dataset to mapbos to store and then reference and display it within the brick.
Re: Using beast mode to compare strings
@Mark Puddephatt - just to second what @Sean_Tully is saying, it's part of my standard practice to wrap text strings in UPPER() before comparing. It just helps to minimize any chance of variability.
String != string != STRING
Re: String Operations
@damen It sounds like the LPAD function in the formula tile is what you're looking for. In your case you would want LEN = 10 and PADSTR = '0'
Re: Export on cards with embedded Domo Everywhere App Studio
I hear this the most from client's switching to app studio.
Definitely would be a very useful feature that I know 4 clients are waiting on to switch to App Studio over dashboards.
Loom video of what's requested:
https://www.loom.com/share/cb08e5db4acd4f42b8632e6b04cfc108?sid=7c6b98ca-b479-4618-a833-2bfe1300e778
I also attached an image
Re: Multiple Level of Detail Tables From One Dataset
@jmmc To add to @ArborRose's suggestion, note that you do not need to aggregate dimension fields like in your MAX(address) example. Table cards and pivot table cards will automatically aggregate the entire cards as long as every Metric (numeric) field is aggregated. You also do not need to create beast modes for simple aggregations like sums and averages, instead you can select an aggregation in the drop-down for the field, like below.
Re: Choose What Cards to move to a new dataset
YES PLEASE! This is another one I keep meaning to add as an idea!
@JoshMillheim - This comes up a lot. Here are a couple scenarios I can think of off the top of my head, but there are certainly more. I have spent hours flipping individual cards and chasing beast mode errors.
Scenario #1 - Sometimes you need to switch to using a new dataset. Rather than taking absolutely everything with you to that new dataset and perpetuating the mess, you want to switch some, makes sure you have what you need, and then deleted the old dataset (which also takes out the trash).
Scenario #2 - You want the same cards for another dataset, so you duplicate all of those cards, and then need to switch them over to the new dataset. You only want to switch over the duplicates.
In addition, the warnings when you do flip cards from one dataset to another are so broad and often incorrect that you have to either not do it that way or cross your fingers and hope. This gets especially rough when a mismatched field name is a filter or a sort on the card, since these just get dropped, rather than prompted like the chart fields do.
