Report Manager SFTP Filename Format
When scheduling reports to be delivered to a SFTP through Report Manager, the files deliver however the filename is automatically being generated with a date stamped. As a report scheduling user, I want the ability to define how the filename will output, with or without a date stamp, so that the filename meets the needs of my configured pipeline processes.
User Specific Time Frame filters
The time frame filter on date fields is great, but the values in the list don't always meet the needs. We have needs for things like 31-60 days, 61-90 says, >90 days. whether that is forward looking or backward looking. This is easily done with the Advanced filter, but that is not easy for end users to use. It would be great if we could add these common filters. It would also be great if we could remove filters from the list that are not used in our environment. Finally some of our users would be better served by 0-45 days, 46-90 days vs the 30 day windows described above. This is why it would be good if users could create and reuse their own Time Frames. Note these time frames probably apply across dashboards for that user.
GROWTH function without hard-coded date filter
Add the possibility to use the GROWTH function without having a date filter on a dashboard or a widget level. End users building dashboards should not have to hard-code date filters to use these widgets. This limits our ability to adopt the Analytical Model which Sisense is investing all its efforts into, the Analytical Model behaviour should be consistent with compatibility mode.
Ability to more granularly control editing of Shared Formulas, Attributes, and non-shared Formulas
We embed Sisense into our application and produce pre-built dashboards for customers (which they cannot edit). We allow our users to create their own dashboards as well and with this comes the ability to create their own formulas. We have found that allowing them to edit the name of their formula also allows the editing of our pre-built shared formulas and our attributes. While this only impacts the user locally, it can become a support nightmare, as customers can rename our pre-built items and make it hard to them troubleshoot. We would like the ability to make these edit options more granular so that we can control (1) Shared Formula name edits (2) Attribute name edits and (3) non-shared Formula, local user dashboard, name edits.
Shared formulas
**Please note this idea was migrated to the Product Feedback Forum from older submission areas** Designers cannot save formulas for shared use. This is problematic in two scenarios: 1. End users (our customers’ customers) are Designers 2. Data models are shared across multiple tenants (with row level security) Without this the customer is forced to either manage hundreds of separate data models, which is not sustainable, or to remove all ability to save formulas, which is not acceptable for users. The “Shared Formulas” feature should allow for permissioning; something similar to “limit sharing to users’ own groups” would work.
Allow minimum and maximum aggregation for date fields
Currently, when adding a date field as a value in a pivot table, the only option is the # of years/# of days/etc. We need the option to add a minimum and/or maximum date for the selected rows. The current 'work around' for this is to create an integer date, and then use a script to format the integer to present as a date. However, when exporting the data, the date shows as the integer value in the exported data, which is an unacceptable result. Adding the date as a row value solves the export issue, but displays all date values for the lowest level of detail in the data source, which is also an unacceptable result. If it was possible to add the minimum or maximum of a date field as a value in the pivot tables, this would solve all of the issues we currently have.
It would be helpful to be able to filter by comparing 2 objects in the data model
Being able to filter a widget or dashboard based upon 2 objects returned from the model would allow for targeted results by allowing end consumers, when creating an N:N or 1:N result to return 1:1 results. This would allow for dynamic filtering of results. For example. I may want only those applicants living within the same city as one of my existing office buildings. This could be done by adding another filter option, result object from model. Then the user could select the object. This will enable dynamic filtering based on result sets rather than strictly selected value filtering.Allow changes to be pushed from Private to Shared viewing
This really should already be an option within this feature but the fact that is not is quite maddening. When I am working on my private dashboards, there needs to be a button to push changes from the private view to the shared view to then republish the results. This should already be a feature and know that many of our clients have complained about this feature. Please please make this update sooner rather than later.
