This is what forces Tableau Public to refresh your data source daily.
When doing so, I made sure to check the box to "keep my data in sync with the data source and embed my credentials" as shown below. I opened Tableau and connected to this Google Sheet. I created a new Google Sheet and entered "=rand()" into the first cell (this would provide a random number between 0 and 1).
Tableau public issues update#
First, you can't use a live data source and the only way to update an extract is via a Google Sheet, which will update once a day. But Tableau Public doesn't really allow for that. This sort of triggered me to say, wait! Data sources on Tableau Server and Tableau Online are always being updated whether it is a live data source or an extract with a scheduled refresh. I mentioned this to Ethan Hahn at work, and he said, how about grabbing the username.well, that's not available on Tableau Public (it is on Server and Online). It always reflected the second that I published it. This would yield a different number of seconds each time someone accessed the viz. Not really taking time to think, I tried just obtaining the seconds of now - DATEPART('second', NOW()). The four leaf clover was in the same spot every time I opened up the viz. I published it up to Tableau Public and started testing it. I then set my four leaf clover to be equal to that figure. I then multiplied that figure by 25,000 (I have 25,000 clovers) which would give me some value between 0 and 25,000. I created a RANDOM calculation in Tableau to get a value of 0 to 1.
So, I decided I would try to randomize the position of that four leaf clover. Every time you came into the viz, you'd see the four-leaf clover would be in the same position as it was the last time you opened the viz.and the second game would be the same, and the third, etc. So you could, in theory, memorize where the four-leaf clover was located. This was pretty easy, but even though you could play thousands of unique games, the games were, again, played in the exact same order. This always bugged me so I decided to create thousands of variations. Again, the problem is that the game never changed.you play it once and you're done. The object was to find the single four-leaf clover. It contained 25,000 three-leaf clovers and 1 four-leaf clover. I created the original version of this one month into using Tableau (March of 2018). We didn't really push the issue and figured that people wouldn't likely play it enough times to memorize the order.įast forward to early 2022 when I started playing around with my Luck of the Irish viz. I quickly tried a few things, but never really dug in. However, that didn't work when published to Tableau Public. I tried grabbing the seconds of the time figuring that would be fairly random - DATEPART('second', NOW()).
Klaus recommended that we use some sort of randomization to change the cards and the order in which they appear. In theory, players could have memorized that the matching object in the first two cards was the zebra and the matching object in the second two cards was the key and so on. The game is played the same way every aning, the first two cards are the same two cards no matter how many times you play the game. Klaus brought up one issue before we shared the viz with the public. I encourage you to check out the final Spot It vs Dobble viz (note: in Jul 2022, there was some issue with images on Tableau Public, so parts of this viz may look a little odd). The viz turned out great and it was a ton of fun to build. The game itself is a ton of fun and the mathematics behind it are simply mind-blowing. You turn over two cards and players race to find the one and only object that is on both cards. In December 2020, Klaus Schulte and I collaborated on a fun project where we recreated the Spot It (known as Dobble in Europe) card game in Tableau.
0 kommentar(er)
