Tim
Data Integration
Joined 11-17-2021
User Profile
User Widgets
Contributions
Disable email for owner change
When I change ownership of a dashboard, the new owner gets an email. Can I prevent that? My reason: Usually, I'll discuss with the new owner and let them know. Sometimes, a user becomes owner to make a change, then returns the dashboard to the original owner. In both cases, the email is often just clutter.13Views0likes0CommentsBug: Co-ownership via AD group fails
Details below. I'd like to know: (a) Can we get a fix in a future version of Sisense? (b) Do other users and Sisense tech get the same issue? (c) Any advice other than my workaround? Try the following: 1. Co-Authoring enabled. Sisense version L2025.2.0.510 2. UserU1 from Active Directory (via LDAP). Within Active Directory, UserU1 is a member of GroupG1. Within Sisense, UserU1 has the Admin role (I haven't checked if role matters). 3. UserU1 creates DashboardD1. 4. UserU1 makes the Sisense Sysadmin and GroupG1 co-owners of DashboardD1, and removes themselves from the list of shares. Expected behaviour: This should result in UserU1 still having co-owner access to DashboardD1 because they are a member of GroupG1. Actual behaviour (bug): UserU1 does not see the Private/Shared toggle button. UserU1 does not see the Share/Republish button. UserU1 can edit widgets on the dashboard (as expected). When another user edits and republishes the dashboard, it overwrites UserU1's changes. (Also, a colleague reported a scenario where maybe UserU1's dashboard failed to get the updates when the dashboard was republished except when they manually clicked restore dashboard; if so, that's probably related to this.) So, when you have co-owner access to a dashboard via an AD group, that seems to behave more like "Designer" access, or like you have only the "Private" version of the dashboard and can't toggle to the "Shared" version. Using non-AD group: I tried the same except that I created GroupG1 in Sisense instead of via AD. Co-ownership worked. Workaround: Do not grant co-ownership to AD groups. Either use Sisense groups or grant co-ownership directly to users.What does an ElastiCube put in RAM
I heard "An Elasticube, once built and set to the Querying state, is designed to keep its data in memory for fast query access." But I noticed that my cube is 90GB on disk, only 8GB in RAM after I refreshed one dashboard, and the RAM use goes jumped to 21GB when I opened a dashboard that queries a larger quantity of the cube's values. So what's in RAM and what remains on disk? Cached query results? Indexes? Just the rows that have been used since the last build? I'm curious because RAM use of large cubes is sometimes an issue; sometimes we redesign the cube to be smaller and sometimes we get more RAM. The more I understand, the better we can discuss and estimate.86Views0likes1CommentDoes build failure leave orphaned queries?
My ElastiCube build failed. It was querying a SQL Server database at the time. I looked on that database after the failure: the build still had a query open. Is that normal? Does Sisense attempt to cancel queries as part of a build failure?102Views1like2CommentsFeature request: Let me connect a livemodel to a source with different table names
Let me connect a livemodel to a source with different table names The problem: I want to change my livemodel's connection to a different database. The new database has the same tables, but they belong to a different schema or have different names. As a result, I get a message "select a different database which includes all tables under one schema". So, I cannot change to the new database. Feature request: When I change the source database in an elasticube, I get an interface where I can map my datamodel's tables to the new names. I'd like the same interface for livemodels. Better yet, let me switch to the invalid connection, and then show the error only when I try to publish the model. Workarounds: A) In the old database, I could create the new table names. Then I can point my livemodel to the new names before switching connection. B) I could edit the .smodel file. C) Tech support suggested this: Use the REST API 2.0 PATCH /datamodels/{datamodelId}/schema/datasets/{datasetId}. I used it with the fillowing request body, then I could change the database. == { "database": "c00845810new", "schemaName": "dbo", "type": "live", "connection": { "oid": "99380074-a2bb-4cd7-8bc3-7a5d20152b82" }, "liveQuerySettings": { "timeout": 60000, "autoRefresh": false, "refreshRate": 30000, "resultLimit": 5000 } } Related discussion in support case 500Pk00000s1fVCIAY.57Views0likes1Comment