commentBlock = $("#comment_post_33098").find('.comment-blocks'); commentBlock.find('.loading').hide(); commentBlock.find('.see-all-comments').hide(); commentBlock.html("
<\/a>
\"it_user8760<\/a>
it_user8760<\/a>Product Manager with 201-500 employees<\/span><\/div>
<\/span>Vendor<\/span><\/div>
<\/i><\/div>
<\/i>Report as inappropriate<\/a><\/div><\/div><\/div>

Hi there,<\/p>\n\n

As Director of Product Management of Sisense I would love to shed some light on the inner join issue you mentioned. In general I will say that there are two ways to address it:<\/p>\n\n

1. You can still always create an inner join with the custom SQL feature, if it\'s absolutely necessary.<\/p>\n\n

2. It\'s true that the ElastiCube Manager (visual data modeling environment) doesn\'t show inner joins as a configuration option. However, it\'s quite possible that if you find yourself looking to do inner joins, you\'re not utilizing the full power of the product: <\/p>\n\n

Most solutions rely heavily on joins in the data prep phase to create a single view. \n
What\'s unique about Sisense is that you don\'t *need* to flatten the data during the data preparation stage. Sisense only performs joins when it needs to answer a query, such as when a new visualization is created. The joins are performed ad-hoc and the system automatically detects which type of join is most effective for that particular data scenario. So 99% of the time, you shouldn\'t be dealing with these join headaches in the first place.<\/p><\/div>