Reconnecting Disconnected Output DataSets and Cards
We are developing under several accounts (e.g. Dev1 and Dev2).
In order to organize the ownership, I have changed the ownership of some pages and cards to one account (Dev2 > Dev1).
Then the connection between the DataSet and the card got disconnected and the card is no longer visible.
For the card with a direct connection to the DataSet, I was able to recover by re-assigning the DataSet.
However, for the output DataSet that was processed by DataFlow, I cannot find a way to connect it to the card and it is still not visible.
It may be best to rebuild the card, but does anyone know how to connect it?
Best Answer
-
Have you changed the ownership of the DataFlow generating your dataflow dataset to Dev1? What about any input datasets for that dataflow? Have you made Dev1 the owner of those? Another option would be to make Dev2 a co-owner assuming you want both dev1 and dev2 to be able to edit your cards and dataflows?
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**1
Answers
-
Have you changed the ownership of the DataFlow generating your dataflow dataset to Dev1? What about any input datasets for that dataflow? Have you made Dev1 the owner of those? Another option would be to make Dev2 a co-owner assuming you want both dev1 and dev2 to be able to edit your cards and dataflows?
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**1 -
Thank you @amehdad and @GrantSmith for your answers. Sorry for the late confirmation. I was on holiday.
I have solved this problem, though not completely.
Dev1 and Dev2 had exactly the same Security Role, so I don't know why the connection between the card and the DataSet was broken. However, I was able to reconnect the DataSet and recover, albeit with some problems.
It was a problem with the filter that prevented the data from being visible.
When I checked the card on 1 November, it only had data up to 31 October, but the default date range was This Month. This was the cause of the problem.
I apologise for the pointlessness of this question.
0 -
@Tow solving it yourself is always good and either way you've made @GrantSmith a happy man :P
10
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.9K Transform
- 100 SQL DataFlows
- 616 Datasets
- 2.2K Magic ETL
- 3.8K Visualize
- 2.5K Charting
- 737 Beast Mode
- 56 App Studio
- 40 Variables
- 684 Automate
- 176 Apps
- 452 APIs & Domo Developer
- 46 Workflows
- 10 DomoAI
- 35 Predict
- 14 Jupyter Workspaces
- 21 R & Python Tiles
- 394 Distribute
- 113 Domo Everywhere
- 275 Scheduled Reports
- 6 Software Integrations
- 123 Manage
- 120 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 10 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 108 Community Announcements
- 4.8K Archive