[ARCHIVED] Managing Datasets in Explore | Community
Skip to main content

[ARCHIVED] Managing Datasets in Explore

  • February 27, 2019
  • 3 replies
  • 0 views
B

I've been struggling managing datasets.  Both OOB and Custom (new or cloned).  Maybe Im not understanding the concept but it seems as though I'll be using a dataset to build queries and eventually I start seeing strange attribute names and am told by ZD that it should no longer be used.

It would not be as big of a deal if you could copy all your queries to the new dataset but there are limitations on what will and will not copy over.  I then have to recreate the query in the new dataset and add it back to my dashboards.

I have one dataset that I thought was "safe" and now have 54 queries built from it.  The dataset is now not recommended for use and now trying to figure out how to manage these queries.  I dont want to have to recreate these nor  recreate them and find out the dataset I used becomes invalid in the future.

Anyone else have this issue?

    This topic has been closed for replies.

    3 replies

    Chris21
    • Chris21
    • February 27, 2019

    I've had this same issue multiple times. I would love to be able to clone a query into a new dataset.

    J
    • Jeremy13
    • February 28, 2019

    Ive had to recreate all mine several times now, its a pain.

    It would be better if you could switch the query onto a different data set and adjust it if needed

    The button top left that shows the dataset would be the best way really then when you recreate a dataset you can just swop them to the new one.

    B
    • Bill12
    • Author
    • February 28, 2019

    I was told by ZD support that you can try copying queries from one dataset to another but if there are queries involving tags and such

    "In general, if you have old dataset you can try to copy queries/report to new one if tag reporting or calculated metrics were not used. Please take note, you may need to create new dataset ->not clone it because if you will clone all dataset they will have exactly have the same problems"

    Terms & ConditionsCookie settingsAccessibility statement