Expert
ProfessorThat is close to what I do also. Although I might just directly temp rename it in sandbox before exporting the json as I'm not really worried about breaking our sandbox instance temporarily.
I guess you can also copy the script code from the diff page, convert the /t and /n stuff, edit the existing DataSource, paste in the new script, and just use the Test Script button, making sure not to save.
Most of the time I'm able to review the code via diff (although I copy it to winmerge after converting /t and /n) and most past changes have been minor. So I normally only go thru this full process when the results are hard to determine or too many changes to the code.
I just realized that My Modules doesn't appear to offer a Clone option anymore like the old DataSources UI did. Is that something that was removed or am I just not looking at the right place?
I see the clone option when editing a DS. One thing that's different is that when you clone something it saves it right away. That way the clone is one entry in the changelog and your modifications are a different entry (as far as i can guess). So if you hit the clone button, then navigate away, there will be an orphaned clone in your environment. Compound this with the fact that there's no warning that you'll lose unsaved changes if you navigate away from a DS you were in the middle of modifying.
ExpertYeah, having to edit to clone is frustrating. I think you also have to edit to export. Urgh.
Seriously LM: get rid of the details pane and just use the editor. Most people who would view the details pane are looking for functionality that's only on the editor. RBAC shouldn't be an issue since you were already doing RBAC on UIv3 which only had an editor and no details pane.
