Suryakant
Cloud Apps
Joined 3 years ago
User Profile
User Widgets
Contributions
Multi Factor Authentication
Hi Team, We would like to have MFA (Multi-Factor Authentication) feature to be brought into Sisense On-premise version as soon as possible. Background: With current data breach happened at Sisense, it's high time that Sisense should think of Customer's data security in every aspect We understand with SSO security layer is present but not all customers will use SSO for every scenario. Still there will be situations where credential based access will be used by some customers For such situation Multi-factor authentication is really important Use Case: In our case we will use combination of SSO and Credential based access. i.e Few customers will use SSO and few customers who don't have SSO will use credential based access but will have MFA. If for any user we are selecting password based access, then there should be one flag to enable MFA for that user (via SMS or via any authenticator application) Sample thought: Waiting to hear from Sisense to see this feature in their next release.1.7KViews5likes0CommentsElastic Cube on Top of S3 data- Build Failures
Hi Everyone, I have my data in S3 buckets and this data refreshes once in a day. So, For me Live connection datamodel under Sisense doesn't make sense because unnecessarily for every dashboard load-- query will run (either in Athena or Redshift) which will cost us more. So, I went ahead with below approach: S3 Data ---> Elastic Cube in Sisense on top of S3 data using Athena --->Build of this Elastic Cube is scheduled for once in a day---> Dashboards connected to this Elastic Cube ---> Dashboards run from data stored in FSX storage (which is faster as well as cost effective) With above approach, I see Elastic Cube build is successful, if I have less data (approx. 1 M records ~ 2GB). The moment data is more, I start getting build failures with below mentioned reason: The build failed due to an exception encountered during the task "Build Table sales". The specific error message indicates that the base table "sales" was not completed as expected. The failure occurred during the reading of row 579744, with the underlying cause being an Amazon Athena ETL session failure. Additionally, there was an out-of-memory error (GC overhead limit exceeded) during the data writing process for the session ID 'tq_lOlCozh6N'. Mainly the failure is happening during writing process. I am attaching the logs also. Any help will be highly appreciated.1.1KViews0likes1Commentshared formulas while exporting dashboards
Sisense currently supports Shared formulas to be moved as a part of data Models only. However not all Designers have access to edit/view data models So, they can't move shared formulas from one environment to another via data models Shared Formulas should be exported along-with Dashboards also619Views1like1CommentAbility to Export shared formulas together with dashboards
We are using Shared Formulas on Sisense and we would like to know how do we move our dashboards along-with Shared Formulas from one environment to another environment. This is my situation: 1. I have a dashboard in DEV, where I created the shared formulas and used them in some widgets 2. The dashboard was exported from DEV and imported on PROD, but I had to manually recreate all the shared formulas and also edit widget by widget to change the formula, because the formulaRef changed. We want shared formulas to be moved from Dev to prod along-with Dashboards itself. Note: We cannot use Exporting data-models along-with shared formulas from one environment to another because data models will be different. Thanks a lot Suryakant835Views0likes1CommentNumber Formatting Support for Japanese Users
Background and customer pain points Currently Sisense is capable of showing numeric figures in abbreviated format, but only in the American/European short scale form: thousand (k), million (M), billion (B), trillion (T). In east Asian countries, there is a different scale form, so viewing information in these k/M/B/T is very difficult to understand. Non-abbreviated Standard abbreviation (US/Europe) Indian abbreviation East Asian abbreviation 1,000 1 k (thousand) 1,000 1 千 10,000 10 k 10,000 1 万 100,000 100 k 1 lakh 10 万 1,000,000 1 M (Million) 10 lakh 100 万 10,000,000 10 M 1 crore 1000 万 100,000,000 100 M 10 crore 1 億 1,000,000,000 1 B (Billion) 1 arab 10 億 10,000,000,000 10 B 10 arab 100 億 100,000,000,000 100 B 1 kharab 1000 億 1,000,000,000,000 1 T (Trillion) 10 kharab 1 兆 Business case description/value To be able to select the scale form for number abbreviations for different APAC regions as well. Use case A user in Europe is creating a dashboard in Insights with an indicator to show total profit in an Indicator form. Let's suppose that the total profit to display is 1,610,000. 2. Europe user formats the content to abbreviate the display in the short scale form. User will see "1.61 M". 3. A user in Japan is creating the exact same dashboard on the same data. 4. Japan user formats the content to abbreviate the display in Asian scale form. User will see "161 万". 5. A user in India is creating the exact same dashboard on the same data. 6. India user formats the content to abbreviate the display in the India scale form. User will see "16.1 Lakh".1.3KViews2likes3Comments