I noticed this a year ago, and I am surprised it hasn’t been addressed yet.
When you open a LookML dashboard then go to copy it, you get the modal that says “The copied dashboard will not be a LookML dashboard.” and then has a section for Title and for Folder. Regardless of what you put in the Title box (which is required), it will always save it as whatever the original title was.
It does not do this when you copy a UDD to another UDD. It only does it when you copy a LookML to UDD. I have tried this on multiple browsers, devices, and accounts.
To recreate:
go to a LookML dashboard (cannot be UDD)
hit the 3 dots at the top right, click Copy LookML dashboard (not Copy dashboard nor Get LookML)
type anything different in the title box
hit copy
the confirmation modal will say [original name] was successfully copied into [folder].
go to that dashboard and it has the LookML dashboard name and not the new one
Sometimes it will do the courtesy of appending “(imported)” to the end of the original title when another dashboard exists with that same original name in that folder already, but it still ignores any changes I made to the title.
Thanks for reporting this! I was able to successfully reproduce the issue.
I’ll report this to the engineering team. Can you tell me more about the impact of this issue? It’s definitely incorrect behavior, but it seems like there’s an easy workaround (renaming the dashboard post-copy), right?
Thank you. The issue is it adds several additional steps to the process of
duplicating a dashboard.
For example, if I want to recreate an existing dashboard, it is designed
for the following flow:
Click menu
Click duplicate
Type new name
Select location
Click save
Actual flow:
Click menu
Click duplicate
Type new name
Select location
Click Save
Navigate to new dashboard and open
Click edit
Type new name
Click save
You are right you can work around this issue, and this issue does not have
any critical impacts. However the flow is takes twice as many steps /
clicks / page loadings and even more than that in time. I hope that your
team can address this quickly because it is a simple feature that isn’t
working as its designed, intended, or shown.