Beast Mode Calculations missing on subscriber instance
Hello ,
I have a few bm calculations created on my end and published into a subscriber instance. When I go to look at the charts though I get an error that the calculations are missing although they are there on the source. I have to pull in the field again for every chart - any thoughts?
Answers
-
@jgospel if you think this is a bug, submit a support ticket.
information that may be of interest: was this a beast mode built on a dataset view or directly on the dataset, did you share the beast mode to the dataset or just create it at the card level?
Jae Wilson
Check out my 🎥 Domo Training YouTube Channel 👨💻
**Say "Thanks" by clicking the ❤️ in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"0 -
Hi Jae, It seems like a bug.
The bm field was created at the card level and published into the dataset (checked the box to share with dataset). The shared field also exists in the subscriber's instance - just does not auto recognize the field as the ID seems to be missed?
I deleted the subscription and tried again, still running into the same issue.
0 -
Hi @jaeW_at_Onyx Thank you for your response btw
0 -
support is best equipped to confirm and fix bugs. The Dojo community can give how-to / hacks and workaround, but we can't fix product! Good luck!
Jae Wilson
Check out my 🎥 Domo Training YouTube Channel 👨💻
**Say "Thanks" by clicking the ❤️ in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"1 -
@jgospel I use publish as well and have had various issues with things not showing up properly in the subscriber instance. I had to open up a support ticket to get them to fix it. Support didn't provide details, but there was nothing wrong with my beast mode. Seems to be just issues with the publish process.
**Check out my Domo Tips & Tricks Videos
**Make sure to any users posts that helped you.
**Please mark as accepted the ones who solved your issue.1 -
@MarkSnodgrass Thank you. Had a zoom call with support today and they are looking into it, def seems like a bug in the process.
0 -
Update: Turned out to be an issue tier 2 support had to resolve.
1
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.6K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 2.9K Transform
- 102 SQL DataFlows
- 626 Datasets
- 2.2K Magic ETL
- 3.9K Visualize
- 2.5K Charting
- 753 Beast Mode
- 61 App Studio
- 41 Variables
- 692 Automate
- 177 Apps
- 456 APIs & Domo Developer
- 49 Workflows
- 10 DomoAI
- 38 Predict
- 16 Jupyter Workspaces
- 22 R & Python Tiles
- 398 Distribute
- 115 Domo Everywhere
- 276 Scheduled Reports
- 7 Software Integrations
- 130 Manage
- 127 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 11 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 110 Community Announcements
- 4.8K Archive