bayram-kapti
Cloud Apps
Joined 5 years ago
User Profile
User Widgets
Contributions
Re: filter options displays not in ascending order, Ages <16 displays at the end of the list
Hi there, This is the answer we received from Professional Services when we inquired about this: Instead of adding prefixes like 1, 2, 3 and so on, you can add spaces to those values. For Example, Monday becomes ' Monday' (with 1 space), Tuesday becomes ' Tuesday' (with 2 spaces), Wednesday becomes ' Wednesday' (3 spaces) and so on. Remove the '' marks from the above logic. Sisense removes the trailing spaces in the filter scope but still sorts it using that. Note that we will be shown the spaces if we download the data as csv.4.1KViews2likes1CommentRe: Continuous Deployment on Live Data Models
Thank you for your reply irismaessen . Unfortunately, that's not working as I get this error when I try to switch from DEV schema to PROD schema: ```All tables must belong to the same schema, please select a different database which includes all tables under one schema.```4.9KViews0likes1CommentContinuous Deployment on Live Data Models
Hello Folks, How do you migrate a development data model that reads data from a Development Schema to a production data model that reads data from a Production Schema without actually creating the data model from scratch? Details: We're about to make our initial release of Sisense embedded dashboards. We have a Production and Development Environment in Sisense and we're quite happy to be able to migrate dashboards and data models from one env to another seamlessly. However, here is the problem. We have a very complex data model and we don't want to recreate it from scratch every time we release a new version of the dashboards. In order to not impact the Production Dashboards while working on future versions, our Production Data Model is connected to a Production Schema in Snowflake while our Development Data Model is connected to a Development Schema in Snowflake. When we migrate DEV Dashboards and Data Models to PROD environment on Sisense, everything is good except the DATA SOURCE for our DEV Data Model. It still points to DEV Schema in Snowflake and there is no way to change the schema even though the underlying table names are same in both schemas. And again, we don't want to create the data models from scratch for Production Environment. Has anyone find a solution for this? Thanks!Solved