![]() I decided to take the quicker option to manually copy and paste the Data I needed rather than create code to web-scrape the page, though for future versions of my visual, I intend to do the latter to utilise the hotfixes between minor releases. Fortunately, Tableau creates insightful and detailed feature release pages that contain the feature, description, product and version. Once I knew the fields and visuals required, I set about finding the Data I needed to fulfil my needs. It would be pointless and unproductive for me to build something that others wouldn’t see value in (which is a fantastic approach for anything you create to ensure things land correctly the first time). I also needed to verify what I thought my end user might benefit from and what others thought by discussing options and changes with my peers. ![]() This would mean I wouldn’t need to keep going back and changing the data or structure to reduce development time. I needed to understand what I wanted from my dashboard before I put my data together. ![]() ![]() Most front-end users care about the fantastic new features that Tableau launches with their major releases, but not always the differences between their current and intended versions. I took it upon myself to create a dataset of features, both by release and by Tableau product, from which I could then build a visualisation. When I joined the team, I saw an opportunity to provide information to both our clients and the wider community. As part of our ServerCare offering here at InterWorks, we perform Tableau server upgrades for our clients, which allows them to not worry about the backend knowledge or effort required to complete their tasks. ![]()
0 Comments
Leave a Reply. |