Dataflow loads in preview, but not in actual dataset?

MB_Dem
MB_Dem Member
in Magic ETL

Any troubleshooting tips for us? Our data flow's outputs:

  • Work when we run a preview
image.png


  • When we run it, the datasets give us an "Unable to load this DataSet" error. (The second dataset is my "test" output where I kept moving it around the flow, trying to identify if a specific part of the dataflow was breaking the final output.)
image.png


Best Answer

  • MB_Dem
    MB_Dem Member
    Answer ✓

    FYI Turns out it was a glitch in the matrix. After the person recreated the dataflow, using the EXACT SAME datasets/tiles/joins/etc, worked. ¯\_(ツ)_/¯

Answers

  • GrantSmith
    GrantSmith Coach

    does the user you’re logged in as have permissions to those output datasets?

    **Was this post helpful? Click Agree or Like below**
    **Did this solve your problem? Accept it as a solution!**
  • MB_Dem
    MB_Dem Member

    Yes. Myself and the person who created them both have Author roles, and full permissions to all the datasets referenced.

  • MichelleH
    MichelleH Coach

    @MB_Dem By default any dataflow output datasets are owned by the user who owns the dataflow, even if both users have access to all the input datasets. The owner of the dataflow will need to share both output datasets with you.

  • MB_Dem
    MB_Dem Member

    To clarify, the dataflow was created by the same person who also gets the "Unable to load dataset error."

    I've directed them to create a brand new dataflow, recreate the work inside the original, and see if that resolves the problem. (I'm pretty sure we experienced this glitch before, and mysteriously a new dataflow worked out the kinks. ¯\_(ツ)_/¯ )

    I'll provide an update if the new dataflow solves the problem.

  • MB_Dem
    MB_Dem Member
    Answer ✓

    FYI Turns out it was a glitch in the matrix. After the person recreated the dataflow, using the EXACT SAME datasets/tiles/joins/etc, worked. ¯\_(ツ)_/¯

  • McSQL
    McSQL Domo Employee

    @MB_Dem I'm glad you have a way to resolve the issue. if the original dataflow is still in existence, I would suggest sending to the support team as it may help fix the bug. Would be nice to have the root cause fixed so that you and others don't run into this in the future.

    **Say “Thanks" by clicking the thumbs up in the post that helped you.
    **Please mark the post that solves your problem by clicking on "Accept as Solution"

Categories