Copying from shared to personal folder best practices?

Question

Hi All,

Some of the user base is seeking to become more involved in light development ... possibly even creating some of their own dashboards. Currently, all of the dashboards are owned by IT, and as such are read/execute only. One of the suggestions was to copy a dashboard over to the personal folder (from the shared folder), so that it could be used to learn from, without changing the original. However, while testing, there were some errors when trying to make edits to the dashboard, even when it is in the personal folder (along with the analysis objects). We saw errors saying that the changes couldn't be saved, as it was still referring to/trying to write to the shared_folder location. We found that if you take the individual analyses (and other components ... prompts, etc.) and swap them out with copies from the personal folder, it will allow the changes to be made and saved locally.

Is there another/better way to accomplish this?

Regards,

Charles

Charles M · Answer

Thanks Christian. We'll take a look at the "Sample" folder idea. I think that makes sense as an approach to this.

[Deleted User] · Answer

Hi Charles,

In terms of people learning things have them start in their own personal folder AND maybe consider a playground area in the shared folder.

In order to teach them to think in terms of objects - let's face it, they HAVE to understand how the tools works as you can't make it work differently - give them not just "a dashboard" to copy, but rather prepare a folder directly under /shared like "Sample". Inside that main folder you put the objects by type into subfolders. E.g.:

Sample

->00 - Dashboards

->01 - Analyses

->02 - Prompts

->etc

YES they will still have the problem of references if they copy that whole folder including subfolders and objects. That's something you can not circumvent due to how the references work technically.

DV Projects handle this differently by packaging all into hte project (so the a.dva archive) which removes all reference issues but also eliminates any notion of re-usable objects.

tl;dr - education, education, education. Make people understand how things work and why.