Does the data cube use always inner join?
Hi Community! I have many years experience with other BI tools but I’m new in the Sisense’s world. I just built up a basic model and recognise when I tried to create a table or pivot, I saw just those rows where the keys are same. It seems that the cube default use inner join 🤔 Could it be possible? Can I configure somehow the way/direction of the connection (left join, right join, 1-1, 1-many, many-many)? And it could be possible that I did something wrong 🙈 Thanks for all comments! Zoli @datacubeSolved200Views1like3CommentsOracle CPQ to snowflake
I'm looking for some advice on how to extract data from Oracle CPQ to snowflake. I do not have any idea about how Oracle CPQ works and not sure on the data model how the system works. Is there any way we can extract Oracle CPQ transactional data into snowflake? I see rest API's can be used. But I want incremental data loads into snowflake for quotations that are created in Oracle CPQ. Any help with suggestions or best practices to implement the incremental data pipeline from Oracle CPQ(Source) to Snowflake(Target) is greatly appreciated. Thanks!!751Views0likes2CommentsWidget filter for I-frame based integration
I've been actively seeking a solution to integrate filter functionality into our table widget, specifically tailored for customer-specific data. To achieve this, I've explored various avenues. Initially, we considered implementing a filter option solely for customer-specific data using I-frames with Single Sign-On (S SO) capabilities. While this approach showed promise, it became apparent that the implementation was only effective for dashboards, falling short when applied to individual widgets. Subsequently, the team suggested utilizing J A Q L through URLs to filter data, but again, this solution proved effective solely within the context of dashboards, posing limitations for standalone widgets. Recognising the need for enhanced data security measures, we explored the option of setting up customer-specific rules within Si sense. However, the process seemed disproportionately cumbersome for what should be a straightforward filter implementation. Moreover, accommodating customers with large datasets would necessitate upgrading our licensing, adding another layer of complexity to the process. Given these considerations, I'm inclined to question whether configuring data security rules is indeed mandatory for a basic filtering process aimed at rendering table widgets. Is there a simpler, more streamlined approach available that doesn't entail extensive setup or licensing upgrades? Your insights on the matter would be greatly appreciated. If further clarification is required, please don't hesitate to reach out. Additionally, for additional context, please refer to the tickets listed below. Example table widget : Item Id (Customer Id) Name Transaction Amount 10001 customer 1 $100 10002 customer 2 $ 500 10001 customer 1 $ 300 10003 customer 3 $ 400 10002 customer 2 $ 600Solved946Views0likes1Comment