ihoryokhym
Sisense Employee
Joined 4 years ago
User Profile
User Widgets
Contributions
Dashboard dates display incorrect years due to fiscal year settings [Linux]
Step-by-Step Guide Check your Elasticube fiscal year start month Open Sisense Admin or Elasticube Manager. Navigate to the Elasticube used by the affected dashboard. Locate the Fiscal Year Settings section. 2. Review the fiscal year start month Verify the month configured as the Fiscal Year Start Month. If set incorrectly (e.g., April instead of January), Sisense shifts dates into the next fiscal year, causing dashboards to display dates one year ahead. 3. Adjust the fiscal year start month If the setting is incorrect, change it to the correct start month (typically January, unless your organization uses a non-standard fiscal year). Save your changes. Conclusion Incorrect dashboard dates often result from misconfigured fiscal year settings in the Elasticube. By reviewing and updating the fiscal year start month and rebuilding the model, you can quickly restore accurate date displays across your dashboards. References/Related Content Sisense Documentation: Fiscal Year Settings: https://docs.sisense.com/main/SisenseLinux/fiscal-years.htmResolving model export limitations in Sisense [Linux]
As Snowflake transitions to requiring Key Pair authentication, there is uncertainty regarding the compatibility of v2 generated key pairs with Sisense. Sisense documentation currently recommends using v1 key pairs, while Snowflake suggests v2 keys. This article clarifies the compatibility of v2 keys with Sisense and provides guidance on transitioning to these key pairs.Resolving model export limitations in Sisense [Linux]
When trying to export a data model from the Data page, if the model exceeds 2 GB in size, the export process fails. Users typically see a generic error message, and the model is not exported successfully. By default, Sisense limits the maximum size of the data export stream. When a model exceeds this threshold (2 GB), the export operation cannot proceed.Troubleshooting 500 internal server error on REST API PATCH: updating connection parameters
This article addresses the resolution of a 500 Internal Server Error encountered when attempting to change connections using the PATCH method on Sisense REST API v2 for updating data model schema datasets. If you are experiencing issues following recent upgrades or changes in Connection Manager features, this guide may provide the solution.
