Dashboards in Copied Folder Losing Report/Data Source References

Hi Smartsheet Community,

We’ve been using a templated solution where we maintain a folder that includes dashboards linked to reports, which in turn pull from underlying sheets. We copy this template folder programmatically using the API (copyFolder) to create new instances for different clients.

This process worked flawlessly until recently. Now, even though the folder, reports, dashboards, and sheets are all copied, the dashboards lose their data source references — especially widgets that are based on few reports. When we open those widgets in the copied dashboard, they display errors like:

"Unable to display chart – source sheet or report can't be accessed or has been deleted"

It looks like copyFolder no longer updates internal references in widgets, similar to the recent issue where workflows are showing {{INVALID COLUMN}} in custom messages after copying a workspace. (https://community.smartsheet.com/discussion/139916/invalid-columns-in-workflows-when-copying-a-complete-workflow)

My Questions:

  1. Is there any planned fix or workaround to ensure copied dashboard widgets link to the newly created reports instead of the originals?

Thanks in advance,
Sachin

Answers

  • MarceHolzhauzen
    MarceHolzhauzen ✭✭✭✭✭✭

    We seen a similar issue where widgets give us this error once we transfer ownership of the workspace or sheets to someone else.

    After logging a support ticket, we were told that the actual widget is owned by the person who created the dashboard (or made the copy) and this cannot be transferred. So the new owner needs to reselect the data sources.

    It would be great if this could be address

    Marcé Holzhauzen
    Solution and Delivery Consultant with Award Winning Partner
    Want to meet?Check my availability

    Find me on:LinkedIn | YouTube

    www.prodactive.co.uk

    If this helped, help me & the SSC by accepting it and reacting w/💡insightful, ⬆️ Vote Up, and/or ❤️Awesome.

  • @MarceHolzhauzen

    Thanks for the response.

    However, what's confusing is that this exact setup was working fine until just a few days ago. We’ve been using the same templated structure and the same API-based automation (copyFolder) for quite some time, and all dashboard widgets used to correctly point to the newly copied reports without needing any manual intervention — even when ownership was transferred.

    It seems like something has changed recently in how Smartsheet handles internal references during the copy process. If widget ownership is now causing this issue, was there a recent product change that affects this behavior?

    Would appreciate any clarification or updates on whether this is expected going forward or part of the ongoing bug that’s being worked on.

    Thanks!

  • MarceHolzhauzen
    MarceHolzhauzen ✭✭✭✭✭✭

    @Sachin Kumbar
    From what we could figure out, it wasn't a change that caused the widget ownership issue. It apparently has been this way a long time.

    I'm sure one of the Smartsheet employees can shed some light on this for us. Maybe @Jim Hinkey can help us out

    Have you seen the updated API documentation post? https://community.smartsheet.com/discussion/137201/smartsheet-api-docs-site-is-getting-a-major-upgrade

    Marcé Holzhauzen
    Solution and Delivery Consultant with Award Winning Partner
    Want to meet?Check my availability

    Find me on:LinkedIn | YouTube

    www.prodactive.co.uk

    If this helped, help me & the SSC by accepting it and reacting w/💡insightful, ⬆️ Vote Up, and/or ❤️Awesome.

  • Hi @Sachin Kumbar,

    We got a release email a recently that was related to the folder logic and something in that email indicated that anyone using this function with APIs would need to make updates. It looks like I deleted that email with more context.

    But I think your issue may be related to this June 4th release:
    Copy Folder Automation Enhancements now generally available! | Smartsheet

    If I locate the email we received with more context, I will pass along. But you may want to take a look at the updated API documentation that @MarceHolzhauzen shared above to see if there is a tweak you need to make.

    Michelle Watkins, PMP, MBA