0:00Hey, it's Tim here. Today, I was going to
0:01download a new version of Tableau. And I
0:03realized that Tableau have changed the
0:05known issues page from sitting on the Table
0:07au website to the Salesforce web page. So I
0:10thought, why not explain to everyone what
0:12the known issues page is for and why it's a
0:15good thing to check from time to time. As
0:17ever, let's get stuck in.
0:18Okay, so when you go to download a version
0:21of Tableau, you might often see a notice in
0:23this sort of gray section here. Sometimes
0:26this is a good way for Tableau to
0:27communicate status updates in this
0:29particular setup, what they've done is they
0:31've actually highlighted the move of the
0:34issues page that used to be for Tableau,
0:37moving from the Tableau websites to the
0:39Salesforce website. So if we go ahead and
0:41click on that, it actually takes us
0:43straight to the known issues page.
0:45And the interesting thing here is this is
0:47it this issues page is actually for all
0:48Salesforce products. But here what this
0:51specifically done is filtered it to just
0:53Tableau. So you can see all the Tableau
0:55related issues. Now, the known issues page
0:57is a really good thing to be just just
0:59aware of because sometimes in Tableau, you
1:01come across a bug, and you don't understand
1:03why something's behaving the way it is. And
1:05actually, when you go to this page, you
1:06immediately find out that it's a known bug,
1:08it's a known issue, and it's being explored
1:10. Or you're sitting on an older version of
1:13Tableau, you've just come across the bug.
1:15Maybe six, seven months after upgrading.
1:17And you actually go to this page to
1:18validate the version you're on is the one
1:20with the issue. And so it's a really good
1:22way of knowing these things. It doesn't
1:24always sort of come up as the case that
1:25every single bug is listed here. But
1:27typically, most known issues do find their
1:29way here. And then there are some issues
1:31that don't find their way here, but are
1:32known issues. And so that gets a little bit
1:34confusing. I'm hoping with this change, it
1:36gets a little bit better. Anyway, how does
1:38this page work? So across at the top, you
1:40've obviously got the ability to choose all
1:42the different Salesforce products.
1:45In this particular setup, all they've done
1:46is sort of filtered it down to Tableau, I
1:48believe that's right there. So there's 222
1:51Tableau known issues. And so when you
1:53filter down to that category, it gives us
1:55this list. The next thing we have is the
1:57status. So you can actually see the issues
1:59that are in review, the issues that have
2:01been fixed, scheduled, deployed, and
2:03working as expected, or whatever. So this
2:05is an interesting breakdown, because I've
2:07actually never seen this as detailed as
2:09this working as expected, I assume is where
2:12people are reporting something as a bug.
2:15And actually Tableau change the default
2:16behavior. So it's actually working as
2:18expected. Go ahead and click on that, we'll
2:21see hopefully the nine issues in there. So
2:23it's kind of interesting, because you can
2:25kind of sometimes kind of come from maybe
2:27server expecting something to work, and
2:29then you go to cloud, and it doesn't work
2:31as expected. So this is a nice category to
2:33see. But it's going to be interesting to
2:34see what's actually in that list. Anyway,
2:36the ones in review are tend to be the ones
2:39that are currently open, but they're being
2:41analyzed, trying to understand what is this
2:43actual bug?
2:44What's causing it? And how can it be fixed?
2:46Once there is a known solution, it then
2:48moves up the tree. So solution in progress
2:51is the next logical one, I've actually
2:52think they've actually done this in in a
2:54logical order. So solution in progress is
2:56the next one. So these are things that are
2:58being worked on now they know how to fix it
3:00. And they're sort of rolling them out or
3:01fixing them. Solution scheduled means that
3:04there's a release day available. So this is
3:06likely to be in a patch, one of the monthly
3:08patches to a release of Tableau, or a
3:11version release of Tableau later down the
3:13line.
3:13And then of course, deployed is there once
3:15something's actually been shipped, and it's
3:17been put inside of a version of a product
3:19that you can actually download and use
3:20today. In the case of Tableau cloud, it's
3:23almost instantaneous. So depending on your
3:25Tableau cloud pod, you should get it pretty
3:27much straight away.
3:28And then of course, we've got closed, which
3:31I think is just the items that, you know,
3:33have been reviewed, but maybe didn't hit
3:35any of the other statuses and have been
3:37closed or something that's been deployed.
3:39And then eventually gets closed later down
3:41the line. And so you get a nice little sort
3:43of breakdown. And what's nice about this is
3:45they've also got the number of reports, if
3:47I sort of move my face here to the right,
3:48you can see the number of reports. So if I
3:51go down here to let's say, let's untick
3:53that and let's get solutions in progress.
3:55You can see that for example, this one has
3:57had 16 reports of that particular issue. So
4:00I'm also curious, where does that 16 come
4:02from? Is this customer support tickets?
4:04Because to me for some of these issues,
4:06that's a fairly low number given the
4:07install base of Tableau.
4:08So I'd be interested to know that 16
4:10reports, but Tableau must have telemetry
4:13that tells them how many people are
4:15affected, they should be able to tell us
4:17that would be a great number. Of course, it
4:19never put it public. But nonetheless, that
4:21would be a great number to understand.
4:23And so there you go, that's pretty much the
4:25solutions page. Now, I find this pretty
4:27handy, because you can also filter this
4:30based on the release. Now, this is where I
4:32think this kind of goes a little bit off,
4:34because what they've done here is they've
4:36labeled it using the Salesforce releases.
4:38But of course, if you're coming from the
4:40Tableau world, what you want to know is
4:42version numbers. And of course, Tableau
4:43have just changed the release schedule,
4:45check out my previous video to see more
4:47about that instead of getting four releases
4:49a year, we're only going to be getting
4:51three.
4:51So this sort of seasonal alignment might
4:53actually sit nicely with this particular
4:56release cadence. So we've got spring here.
4:58I don't know if sorry, summer, I don't know
5:00if the previous ones that is spring and the
5:02final one is autumn. I don't know if that's
5:05how the Salesforce issues work.
5:07In fact, we can find that out quickly. Let
5:08's just quickly go ahead, remove Tableau and
5:11just see. So we do get spring, winter,
5:13summer, spring, winter, summer. So that
5:16change from Tableau to align itself with
5:18Salesforce is pretty much confirmed here.
5:21So spring, summer, winter is probably the
5:23cadence. And so we should be able to see
5:25everything sort of line up with this. So
5:28the whole Salesforce org will be in one
5:30nice setup. So maybe that's useful context
5:33for why the change was made just to get
5:35everything internally under the same under
5:39the same banner.
5:39So I think I've selected Tableau. No, that
5:42's not working. Is it possible to just
5:45select all of Tableau? Do I have to select?
5:47How do they create that parameter? How do I
5:50go in here and just select Tableau? If I
5:52type Tableau, it has Tableau API, Tableau
5:55server, it just has all the Tableau. So I'm
5:57just gonna go in here and tick everything.
6:00I guess it is nice that you do have the
6:01ability to actually just choose a product.
6:04So you can go and see those bugs working
6:06straight away. And then you get basically
6:08the same list. But yeah, that's pretty much
6:10the main issues in a nutshell. And what is
6:13useful to do sometimes with this page is
6:15just to be aware of it.
6:16If you're a server admin, if you're a cloud
6:18administrator, or if you're using desktop
6:20heavily, and you're part of a COE, it's
6:22just useful to be aware of these. There are
6:24some newsletters out there that share some
6:26of this information, these fixes and
6:28patches, as well. So be sure to check those
6:31out as well. I'll try and put a link to
6:32some of them in the description below.
6:34I don't think this page has an RSS feed.
6:36RSS feeds are a bit archaic, but I still
6:39find them the best way to reliably get
6:41information from any any particular service
6:44. So it might it might be that we just have
6:47to scrape this page and some find some sort
6:49of way of getting these out there. If I go
6:51into specific one, let's go into this
6:53specific issue Tableau desktop Mac OS
6:56virtual connections, you can see the layout
6:58of a specific report, you're actually able
7:01to share it, which is kind of nice.
7:03You can also hit report to say, yeah, this
7:05is affecting me and maybe you get a status
7:08update as well. But there's no RSS feed. It
7:10's just me being old, I guess. But I would
7:13love an RSS feed of this. I know we get
7:16them for the Tableau. If we go to status
7:18actually, I shouldn't have to do this, we
7:20can just go to the bottom and it should be
7:22available. So where is this? Where is this?
7:26Where is this trust? Here we go. So trust.
7:29salesforce.com. Then we go to Tableau, open
7:33on my face, go to status here. We go in
7:35there. Yeah, now we are cool. So trust.
7:38tableau.com has the ability to subscribe to
7:41updates. If I click on that, what does it
7:45show me? Yeah, it shows me RSS. So you see
7:47email, text, I don't know who's using that.
7:50And that's useful for systems, I guess that
7:51are automated, you might have an inbox that
7:53catches the text. RSS feed. This is what I
7:55was actually looking for. So we do have RSS
7:57feeds for
7:58Tableau, online, Tableau Cloud, all these
8:00services. And it's quite, it's quite robust
8:02. I like it's pretty thorough as to when
8:04they update it as well. And it gives you
8:06sort of the granular information about when
8:08there's issues. And if you're scraping that
8:11, which I have been for the last three years
8:13, then you're able to collect a history of
8:15these issues and sort of just create a
8:17library. So maybe I'll do a separate video
8:18on that. But that's it. Not much more to
8:21share. But beyond that, so pretty, pretty
8:23dry topic. Problems are never fun. But hey,
8:26if you've got clarity on what they are,
8:27and when they're going to get fixed, that's
8:28going to help you out. Thanks for watching,
8:30and I'll see you in the next one.
8:31And I'll see you in the next one.
8:32Transcribed by https://otter.ai
8:42[ Silence ]