If it is any help, we have a naming convention for all our workbooks and extracts.
We try to follow the UK Ministry of Defence/ISO naming convention
Data Source/Title/Author/Date in ISO/Status (Draft, WIP, Published)/Caveat (Internal/External/etc)/Update Schedule (Daily, Semester/Monthly/Annual).
Hope that helps.
This is possible, although Tableau itself doesn't provide any native hooks for SCM software to lean on - you'd need to check-in and check-out the twb files (which are nothing more than XML files) from where ever they are saved on your hard drive.
In addition, Tableau doesn't offer an internal "versioning" property that you can change (v1.0, v1.1, v1.2) as the report is revved. You'll want to use whatever functionality YOUR SCM system uses to do this. For example, I manage my reports with Git, and use "Tagging" to do versioning.
FYI, if you're coming to TCC next week, there will be a presentation on this topic...by yours truly
My colleague built a change and version management tool for tableau server, which manage the full reporting lifecycle including report/datasource promotion and version control integration (with SVN or GIT backends)
He plans to release it later in the month, you can try to check that out
Sounds very, very cool.
Any update on this?
@Russell do you have anything you can share from your session, i was not able to attend TCC.
Generally, TCC material can be accessed exclusively by TCC attendees for a certain length of time – one of the perks of attending. Then, some of it often becomes available to the general public. Can’t really help you with the “what / when / how” part, though – that’s above my pay grade ☺
Ditto...same approach. Intuitive. VisualSVNServer(Subversion) and Tortoise SVN client.
Yes, I have update. We are using it now at one customer in production, however, we need to have repository access with write privileges on the server which could break your server support.
The problem is that the information which is inside the twb(x)/tds(x) files are not enough for proper versioning. Unfortunately tableau's metadata handling is not consistent, there are information which are not stored in twb files but needed to perform proper change and version controlling. As you all might know, after you publish a workbook to the Server you can select what tabs should be visible on the web, but this information is stored on repository level and not workbook (twb) level. So if you need to revert back to a previous version you need to know what tabs were visible at that time. Tabcmd and simple web APIs do not support easily to get and store this information as well.
We have reverse engineered back the tableau desktop and the server processes and structures which lead to solution where we publish things directly to the repository which is fine for us (we are hardcore tableau admins, we don't afraid from these stuff) but for wider use we have to find other solutions to make it more standard and less messy for the public.
About GIT integration, it is something what we can add easily, however, I do not see the value here as most of the git functionality (distributing, fast branching) make no advantage here.
Regarding GIT integration this is how we currently doing: Version Control & Point-in-time Recovery of Tableau ServerDataboss
This is more like for Server admins, so the visual diffing will work only on XML level.