cjakerle
Cloud Apps
Joined 4 years ago
User Profile
User Widgets
Contributions
Date Filter - Improve Calendar selector user experience
In addition to not being able type in dates with the Calendar item in the date filter (I submitted that as a separate idea to be able to type in dates), the general date selecting user experience is quite cumbersome. It's hard to write this out and much easier to show. But the short story is that it is difficult to select the dates on the first try. A pretty typical interaction with the calendar component goes something like this: Open the filter Select Calendar Pick the start date Perform however many clicks it takes to get to the date you need (sometimes this can take a few clicks if you are going back a few years/months) At this point you think you have selected the start date Now, move your cursor to go select the end date At this point, the start date loses your initial selection. I think this happens 90% of the time Sometimes the issue is that the start date gets set to the new end date Sometimes it resets before you even get to the start date Sometimes it goes back "Select" like you never picked a date This behavior is quite frustrating. I have experienced it quite a bit myself and customers have complained. I hope there is something that can be done to improve it.350Views4likes1CommentType in calendar date in filter
While using the calendar date range in a filter, you should be able to type in the to and from date. The old style filters allowed that option. We recently switched to the "new" style (I say "new" because they are only new to us ... I think they have been available in the product for a long time). In the new style you have to use your mouse to pick the date on a calendar, you can't type it in.446Views3likes3CommentsRe: Show more than 70 columns in a pivot2 (without changing the global setting)
MikeGre - thanks so much for the quick response! What's interesting about that post is that I think it allows you to add more than "x" columns at design time. So, it enables the "+" sign when normally it would get disabled after "x" columns. In this case, I only have three columns under "Values". It's because I have a "Columns" value that is the dates in a month, sometimes it is more than 70 and sometimes it is not, based on how far into "This month" we are. It is always more than 70 if I filter to past months. So, it is only at run time the number of columns expands beyond 70 and I get a little yellow icon that says The Pivot table is limited to 70 columns. Totals may refer to the complete data if set by the dashboard owner. If available, you can use filters to display fewer rows and columns. To view all your data, download the table to CSV. (This message will be shown to your dashboard users). I did try the script but it doesn't seem to change this particular behavior. I tried looking around in the pivot2 documentation a bit to see if there was another setting I could spot, but didn't see anything. I wonder if anyone has just expanded the max number of columns for the entire server to be more than 70? I suppose setting that to something like 95 will cover me here and it's only 25 more than what's already there. It's still limited so that people don't do 200 columns or something wild. If there are any other suggestions out there, please let me know. Thanks, Chris1.7KViews0likes2CommentsShow more than 70 columns in a pivot2 (without changing the global setting)
Hello, We have a situation where we need to show 3 different values for each day of a month in a pivot (so, up to 93 max columns). I know there is a global setting to expand the number of columns on a pivot2 (default of 70, I assume we could go up to 93 on that, if necessary). Generally, I like the 70 column limit so I'd like this to be a one-off exception rather than increasing for everyone. In the old Windows version, there was a script out on the community that could allow more than x columns to show. Anyone have a script to do this with Pivot2 in Linux? Thanks, ChrisSolved1.9KViews0likes4CommentsRe: How to calculate a cumulative unique count
David, Thanks so much for the thoughts. We do have a fiscal year in the data model. When I attempt to use a version of this query (modified for our data model) in the cube as a custom table, the OVER and PARTITION keywords don't appear to be recognized by Sisense (L2023.11) ... they don't turn purple like the words SELECT, FROM, JOIN, ON, ORDER BY, etc do and it gives a syntax error after the "OVER". I can add this to the database instead of the cube and then pull in a table so it's not essential that this work in the cube, but I wanted to double check if you thought those window function keywords should work in L2023.11 for a custom table? I'm not sure the SQL is quite working for this case, but I think you've confirmed that there's no way to do this in a dashboard and I should try to SQL my way through this. That is actually a sufficient answer so I'll be all set once I know about those window functions being recognized (or not) in the custom tables. Thanks! Chris2.6KViews1like1CommentHow to calculate a cumulative unique count
This is a little tricky to explain. It's not just a running SUM from month to month. What we are trying to do is count the number of patients seen in a month, and show how that accumulates over time. The last tricky part is that we are hoping to have it restart at the beginning of each fiscal year (based on a date dimension, not on the fiscal year in Sisense). Here's some more detail. Let's just look at two patients over three months: Patient 1 - Seen in month one. Not seen again Patient 2 - Seen in month two. Seen again in Month three Patient 3 - Seen in month three. The count we are looking for here is: Month 1 == 1 //because only one person was seen Month 2 == 2 //because we are still including Patient 1, even though they weren't seen again, plus patient 2 Month 3 == 3 //because patient 1 was seen in month one, we continue to include them, patient 2 was seen in month 2 and 3, but it's unique count so we are only counting them once, and we have patient 3 seen for the first time I tried using PREV and got to the point where the first and second months were what I wanted, but it breaks in Month 3 when the PREV month no longer has an entry for the patient. We have full control over the data warehouse, so ultimately I could just use SQL to make a table for this, but I was really hoping there would be a Sisense answer for this so it could be managed in a dashboard rather than in SQL Code. Anyone solved something like this before!? Thanks, ChrisSolved2.6KViews0likes3CommentsProvide User Name in addition to email address in Usage cube
Currently the Usage cube has a dimUsers table that has User Name but it is the email address. It can be tough to know just from an email address, who the person is. It would be nice to have the First name and Last name of the user available. Certainly I could try to make a connector into the mongoDB and lookup the First/Last based on the user id. But a) I don't want to modify the out of the box usage cube and b) that seems like a lot of work for something that could be added as part of the out of the box usage cube. Thanks, Chris720Views4likes1CommentRe: Adding custom messages to the standard Sisense Login Page?
Thanks Tri Anthony! We have already customized that welcome screen (but I have it hidden so didn't even think of it!). I think that's a great suggestion though, we'll see what we can do with that. I appreciate you ruling out any out of the box option for the actual login screen. And the screenshots were very helpful! Thanks again. Thanks, Chris1.1KViews0likes0Comments