jwilson Member

This original question was posed 4 years ago. Is there a more modern way to accomplish this without creating a unknowable number of beast-mode calculations?

The "just look at it and you will know if it's working" is fine in a test environment or a small shop. As customers push Domo Everywhere out to broader audiences it's entirely possible that users will see errors that administrators simply wont -- different browsers, different networks, different embeded cards, different…

Confirmed! Finally. This looks so much better for our 3x3. Thanks - Jackson

Unfortunately no. No one was ever able to do that for us. Users aren't complaining any more but the embeded visualizations are so small because so much area is taken up with branding that I don't think anyone's getting value out of the embeded Domo visualizations. We may just replace them with some other visualization…

Our CSM defaulted to our sales rep who says this isn't in the product yet. As a work-around he provided us with a bit of hacky code that tries to wrap the iFrame in a div and then simply hide the bottom portion of the iframe content that includes the branding. That's never going to work on a responsive website. In looking…

How can remove the large "Powered By" graphics from each embeded card?

They seem to have made it worse ... we are still looking for a way to remove the "powered by" logos. They currently take up approximately 1/3 of the area for each visualization. This causes each visualization to scale oddly and in many instances (like gauges) renders them entirely useless.

To be clear, the magnitude of our change was simply changing the name of a folder in AD that contained Groups used in Domo SSO. The name change resulted in the full DN of the group changing (because a parent OU changed). From that point forward, Domo read the group names of the groups under the re-named folder as if they…

I've had a couple people DM me so I've decided to put the instructions here for everyone. We started by setting up SSO to Domo's documented standard. Everything worked fine EXCEPT nested groups weren't decomposed. To "fix" nested groups we modified the standard Relying Party Trust and initial set of Claim Rules as follows:…

We "fixed" the issue with Domo by reverting our OU name change. Not ideal as we made that change in the first place for a reason. This did clear up the issues with PDP but the larger issue remains that using Domo and PDP basically freezes your OU structure forever.

We solved this ourselves. It involves writing two custom claims rules and substituting one for the generic "Group" claim included in Domo's documentation. If anyone would like more detail, please feel free to DM me.

We use ADFS and iOS SSO is working perfectly for us.

Unfortunately no. We still have no way to remove the obtrusive branding from the embeded cards.

Is anyone else encountering this same issue?