Adding background image to embedded cards
Hey all,
I'm having a bit of trouble trying to figure out how to add a background image to a card that is powered primarily by beast mode calcuations. I've endlessly searched the forums and have not yet been able to come up with a solution. What I have is a matrix with 4 quadrants that need to be color-coded and labeled. Here is what I've tried so far and why these options are insufficient:
1. App Design Studio - This card displays correlation coefficients which can only be calculated via beast mode. As far as I have researched, the Design Studio will not allow table caclulations to be the main source for the colums.
2. Custom svg files - I pretty much run into the same issue as the point made above.
3. Adding html code into the beast mode - Doing this would effectively take away our correlation coefficients, so this option is out.
Anybody have a solution or experience with handling something like this?
EDIT: I'm also adding that this card needs to be embdedded, which elimates the option of adding a background image to a story board.
Best Answer
-
For anybody who may have been following this topic,
I've figured out how to calculate the Pearsons correlation coefficient within the SQL dataflow. It was quite simple actually. All I had to do was select all attributes and add in this calculation I originally had in BeastMode:(((count(`ratingid`) * SUM((`x` * `y`))) - (SUM(`x`) * SUM(`y`))) / POWER((((count(`ratingid`) * sum((`x` * `x`))) - POWER(sum(`x`),2)) * ((count(`ratingid`) * sum((`y` * `y`))) - POWER(sum(`y`),2))),0.5)) AS "Correlation"
It worked out for me and I got the same exact results as when I ran the calculation within beastmode. With "Correlation" as a table column, we should now be able to create a card within the design studio that does not require a table calculation.
Feel free to message me if you come accross this and need more of an explanation.
0
Answers
-
Could you attach some screenshots of what you currently have and where you are trying to get to?
“There is a superhero in all of us, we just need the courage to put on the cape.” -Superman1 -
Thanks for your reply. I've attached some screenshots and provided a bit of explanation into what we're trying to do.
This is what we currently have, however we want to assign each quadrant a separate filled color. This helps our users understand a little better what each quadrant means.
^^ Here is the layout for our card axis settings. The correlation coefficient (at our current stage) can only be calculated via beast mode since we have thousands upon thousands of segments for this data. As far as I know, this is incompatible with cards created in design studio.
This is the underlaying formula for our correlation coefficient. I've searched the Dojo for ways to accomplish this in ETL but haven't found anything that would satisfy our needs.
0 -
For anybody who may have been following this topic,
I've figured out how to calculate the Pearsons correlation coefficient within the SQL dataflow. It was quite simple actually. All I had to do was select all attributes and add in this calculation I originally had in BeastMode:(((count(`ratingid`) * SUM((`x` * `y`))) - (SUM(`x`) * SUM(`y`))) / POWER((((count(`ratingid`) * sum((`x` * `x`))) - POWER(sum(`x`),2)) * ((count(`ratingid`) * sum((`y` * `y`))) - POWER(sum(`y`),2))),0.5)) AS "Correlation"
It worked out for me and I got the same exact results as when I ran the calculation within beastmode. With "Correlation" as a table column, we should now be able to create a card within the design studio that does not require a table calculation.
Feel free to message me if you come accross this and need more of an explanation.
0 -
Just be careful, when you calculate this within the dataflow, it will no longer respond to any filters you are applying to the card. For example, if you calculate the corelation of two events occuring in the same calendar year in a dataflow. Then the corelation number will not recalculate if you change your card to look at a 2 year period.
“There is a superhero in all of us, we just need the courage to put on the cape.” -Superman0 -
This was one of the tradeoffs we were willing to deal with until Domo adds support for table calculations within cards created via design studio. It seems like a pretty basic function to me though. Hopefully the feature will be added soon.
0
Categories
- All Categories
- 1.7K Product Ideas
- 1.7K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 295 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.8K Transform
- 97 SQL DataFlows
- 608 Datasets
- 2.1K Magic ETL
- 3.8K Visualize
- 2.4K Charting
- 710 Beast Mode
- 50 App Studio
- 39 Variables
- 668 Automate
- 170 Apps
- 446 APIs & Domo Developer
- 45 Workflows
- 7 DomoAI
- 33 Predict
- 13 Jupyter Workspaces
- 20 R & Python Tiles
- 391 Distribute
- 111 Domo Everywhere
- 274 Scheduled Reports
- 6 Software Integrations
- 116 Manage
- 113 Governance & Security
- Domo Community Gallery
- 31 Product Releases
- 9 Domo University
- 5.3K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 103 Community Announcements
- 4.8K Archive