OMG EXACTLY WHAT I NEEDED!! 🥺I'm preparing for my internship (customer insights analyst) these days and found this channel. Do you have any good advice or study/practice source for someone in this field? thank you Sir!
Thanks! This is the best explanation I've seen so far for this subject. I have a question: I have a dataset that I need to refresh through Tableau Bridge. When I do it with JOIN the update runs perfectly but the calculation values are incorrect, when I do it with Relationship the values are correct but the update fails. Do you know if it is possible to update data set with relationship with Bridge? What could I be doing wrong?
Hey Isabelle, to be honest I've never heard this problem before. Therefore, my approach would be to do some systematic testing. 1. Is Tableau Desktop to blame or Tableau Bridge? You can test this by creating a brand new workbook with a very simple Excel data set. Repeat what you've done and see if the error still occurs. If it still occurs then most likely its Bridge. If it doesn't occur, it's your workbook. 2. Secondly, recreate a simplified version of your workbook from scratch and test that as well. In rare cases, the software does bug out and a single workbook becomes faulty in which case you need to built it again from scratch. However, this has only really happened to Mr a handful of times. Hope this helps
@@jellymaneducation6168 Hello. Thank you for replying. I created a new very simple data source (only two CSV connecting each other with relationship), published it to the Server and tried refreshing it with Bridge - didn't work. I can not attach the error message where but it says "Could not refresh the data source, if the issue persists, contact Tableau Support". When I click to see the details, it opens a box for me to select again the files on my computer - I do so, which really helps when I execute this process on the Data Source made with JOIN, but on this relationship one it doesn't help. Any ideas? Or maybe Bridge is just not supposed to work with DSs that use Relationships. Thank you!
Hi Jed, good day! do you have any videos on tableau data modelling using Azure SQL data source. i am looking for scenarios like created the relationship between One Fact table to multiple dimension tables using primary key and foreign keys. thanks in advance!
Hi, hope you have had a wonderful day so far. I have a question. I’m a freelance data analyst, and I have a client I made a report for him. I would like to know how to add him as a user to see his words on his website. Currently, he does not have a Tableau account. I have a meeting with him tomorrow, and I would like to know in advance
Thank you Jellyman for the explanation! I have a question please: I work at a data analysis consulting agency and we want to start using tableau to build dashboards for our clients, the problem is that when it comes to sharing the dashboard we can't upload it to tableau public because the data is sensitive, if we go with the tableau online option we need to have a creator license (we already have it) but the problem is that the client also needs to pay for a viewer license to view the dashboard, we can't ask our clients to pay for that and we can't pay for it as we work with multiple clients and we need to buy a license for each one of them. Is there a solution please? Thank you!
Unfortunately, theres no way around buying individual viewer licenses. From a security perspective, you really don't want to skimp on Online licenses. It gives you the ability to control permissions and access to ensure clients only see what they need to and can't see other clients work. I guess it also depends on your client structure. If you only ever have 2-3 clients at a time, you could always recycle licenses. One drops off then you give to the next client.
I understood the point about aggregation being done internally (and without any potential error) by tableau when using relationship over joins. But what if i make the different join instead of the ones you made. i think you made left join on those tables that is why the aggregation changed from the actual ones so instead i could do the inner join using colour as key constraint and the aggregation will still be the same as what tableau does using relationships. My point is what is the need of relationships if i can achieve the same results using the appropriate type of joins?
The point of relationships is about Tableaus most common user. Tableau works great when there's a perfect data model set up but a lot of times that's not the case, and business people / project manager types will struggle with the concept of joins. Relationships will solve the problem for them 99% of the time. I'm not super happy about relationships because I just got burned by them myself. In fact I think they will hurt anybody that isn't working with sales data like in this example, because relationships are inner joining behind the scenes which isn't made explicit to us....
Depends on the situation. Generally speaking I would say relationships and the only reason I say that is because the connection occurs when the visualisation is created; not before. Therefore, for specific visualisations where you only use one of the sources, it uses the table directly. That being said, it really depends on the situation. I've seen it go both ways.
I'm not trying to be mean, but I think you explained your message clearly, but this still didn't make sense overall. I like your videos usually, but this one left me scratching my head.
as an experienced tableau dev you explain this very well. love your videos. well done!
Excellent explanation !!! Thanks a lot ! 😊
OMG EXACTLY WHAT I NEEDED!! 🥺I'm preparing for my internship (customer insights analyst) these days and found this channel. Do you have any good advice or study/practice source for someone in this field? thank you Sir!
Thanks! This is the best explanation I've seen so far for this subject.
I have a question: I have a dataset that I need to refresh through Tableau Bridge. When I do it with JOIN the update runs perfectly but the calculation values are incorrect, when I do it with Relationship the values are correct but the update fails. Do you know if it is possible to update data set with relationship with Bridge? What could I be doing wrong?
Currently eating Korean Fried Chicken! Will answer when I get home 😆
@@jellymaneducation6168 Just thought you probably were sleeping right now haha Korean food is great, I can wait :)
Hey Isabelle, to be honest I've never heard this problem before. Therefore, my approach would be to do some systematic testing.
1. Is Tableau Desktop to blame or Tableau Bridge? You can test this by creating a brand new workbook with a very simple Excel data set. Repeat what you've done and see if the error still occurs. If it still occurs then most likely its Bridge. If it doesn't occur, it's your workbook.
2. Secondly, recreate a simplified version of your workbook from scratch and test that as well.
In rare cases, the software does bug out and a single workbook becomes faulty in which case you need to built it again from scratch.
However, this has only really happened to Mr a handful of times.
Hope this helps
@@jellymaneducation6168 Hello. Thank you for replying.
I created a new very simple data source (only two CSV connecting each other with relationship), published it to the Server and tried refreshing it with Bridge - didn't work.
I can not attach the error message where but it says "Could not refresh the data source, if the issue persists, contact Tableau Support".
When I click to see the details, it opens a box for me to select again the files on my computer - I do so, which really helps when I execute this process on the Data Source made with JOIN, but on this relationship one it doesn't help.
Any ideas? Or maybe Bridge is just not supposed to work with DSs that use Relationships.
Thank you!
Are you publishing the data source first prior to the Dashboard?
Super clear explanation, thx!
When to go for Joins and Relationships?
Hi Jed, good day! do you have any videos on tableau data modelling using Azure SQL data source. i am looking for scenarios like created the relationship between One Fact table to multiple dimension tables using primary key and foreign keys. thanks in advance!
Great explanation
Hi, hope you have had a wonderful day so far. I have a question. I’m a freelance data analyst, and I have a client I made a report for him. I would like to know how to add him as a user to see his words on his website. Currently, he does not have a Tableau account. I have a meeting with him tomorrow, and I would like to know in advance
Thank you
THANK YOU
Thank you sir
Thank you Jellyman for the explanation!
I have a question please: I work at a data analysis consulting agency and we want to start using tableau to build dashboards for our clients, the problem is that when it comes to sharing the dashboard we can't upload it to tableau public because the data is sensitive, if we go with the tableau online option we need to have a creator license (we already have it) but the problem is that the client also needs to pay for a viewer license to view the dashboard, we can't ask our clients to pay for that and we can't pay for it as we work with multiple clients and we need to buy a license for each one of them. Is there a solution please?
Thank you!
Unfortunately, theres no way around buying individual viewer licenses. From a security perspective, you really don't want to skimp on Online licenses. It gives you the ability to control permissions and access to ensure clients only see what they need to and can't see other clients work.
I guess it also depends on your client structure. If you only ever have 2-3 clients at a time, you could always recycle licenses. One drops off then you give to the next client.
@@jellymaneducation6168 Thank you so much for your answer, recycling licenses seems like a good approach!
Great explanation! and I loved your Guitar Collection! :)
I understood the point about aggregation being done internally (and without any potential error) by tableau when using relationship over joins. But what if i make the different join instead of the ones you made. i think you made left join on those tables that is why the aggregation changed from the actual ones so instead i could do the inner join using colour as key constraint and the aggregation will still be the same as what tableau does using relationships. My point is what is the need of relationships if i can achieve the same results using the appropriate type of joins?
The point of relationships is about Tableaus most common user. Tableau works great when there's a perfect data model set up but a lot of times that's not the case, and business people / project manager types will struggle with the concept of joins. Relationships will solve the problem for them 99% of the time.
I'm not super happy about relationships because I just got burned by them myself. In fact I think they will hurt anybody that isn't working with sales data like in this example, because relationships are inner joining behind the scenes which isn't made explicit to us....
Great! Very good explanation 🥰
Which has more performance ? Joins or Relationships?
Depends on the situation. Generally speaking I would say relationships and the only reason I say that is because the connection occurs when the visualisation is created; not before. Therefore, for specific visualisations where you only use one of the sources, it uses the table directly.
That being said, it really depends on the situation. I've seen it go both ways.
I'm not trying to be mean, but I think you explained your message clearly, but this still didn't make sense overall. I like your videos usually, but this one left me scratching my head.
mixed relationships with blends
@@valeryliamtsau5135 ?????