Client-Side Status Codes
This is by far the most common HTTP status code you can get. It indicates that the URL you used in your request doesn’t exist on the API server, or origin server. While this is a 4XX error, which usually means something on the client-side is wrong, this can also indicate a server problem. Sometimes API URL paths change after a version update, but sometimes they change because something on the server went wrong. cc943Views0likes1Comment
How do you handle timezone conversions on dashboards?
We store our dates in UTC format and want the ability for dashboard viewers to view the date data in their timezone, or in a timezone they select. Has anyone figured out a way to do this? We have a LOT of date data in our data model.Solved7.2KViews0likes5Comments
Using the /dashboards/admin gives a internal error 500
I am trying to pull data on all of the dashboards that are in sisense. I am using the /dashboards/admin endpoint: https://sisense.dev/reference/rest/v1.html?platform=linux&spec=L2022.3.x#/admin/getAllDashboards But when I call this endpoint I usually get an "Internal Server Error" with status 500. Is this expected behaviour? Is there a strategy I can avoid this error and still get the data?2.7KViews0likes2Comments
Continuous 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!Solved4.9KViews0likes5Comments
