Analytics Studio — Troubleshooting
These are some error messages and situations that may occur during the configuration of the components used by theAnalytics Studio. Here's how to solve them:

Situation
When accessing thereport database management screen, one of the following error messages appears:
Nonexistent report database
Bank of failed reports
Cause
The reporting database base has not been created or is out of date.
Solution
On the reporting database management screen, clickUpdate database. When you click this button, the system will synchronize the data again so that it can be displayed.

Situation
When accessing aPage or Landing Page containing information configured by Analytics Studio, the following error message is displayed:
The dataset for this analytic appears to be unavailable at the moment
Cause
The dataset used to generate the widget does not have all the necessary permissions.
Solution
Solution: Make sure the following permissions are configured correctly:
- Opaper of the user trying to view the Page or Landing Page must have permission on them/dataset:platform/dataset :
- The Page or Landing Page in question must be available to the role associated with the user trying to view the information.
- Youwidgets that must be viewed must be part of the Page or Landing Page that was made available to the user.

Situation
When configuring adataset, it returns the maximum number of 1000 records.
Cause
The query configured for the dataset returned many records, exceeding the limit of results that can be presented (1000 records).
Solution
These are some possible solutions:
- Configure the dataset to return only the totalization of query results, using groupings and functions with
count
,sum
, etc. - If using the SQL Editor, add a limit of 999 records to the query (
limit 999
).

Situation
When trying to view the results of a query in the data sample view, an error occurs when validating the query and the following message is displayed:
Error validating the query, check the errors reported: Error executing the dataset
Cause
These are some possible causes:
- The name of the schema used was entered incorrectly.
- The name of the table used was entered incorrectly or does not exist.
- The reporting database base is out of date.
Solution
These are some possible solutions:
- If you are using the SQL Editor, make sure you typed the schema and table name correctly and are using the following format:"schema-name".table
Example:
For the schemahcm-report and the tablev_employee, this is the correct way:
"hcm-report".v_employee
Example command in SQL Editor:
select count(1)from "hcm-report".v_employee
- Make sure the table you entered exists and is available. You can use the buttonConsult tables to see the list of tables that are available.
- Update the reporting database. To do this, go toreport database management screen and clickUpdate database.

Situation
When trying to view the results of a query in the data sample view, an error occurs when validating the query and the following message is displayed:
Unsupported operation or function: Schema Name
Cause
The schema name was not entered correctly in the SQL Editor.
Solution
When using the SQL Editor to configure a dataset, you must enter the schema name before the table name, in the following format:"schema-name".table

For the schemahcm-report and the tablev_employee, this is the correct way:"hcm-report".v_employee
Example command in SQL Editor:
select count(1)from "hcm-report".v_employee |

Situation
When selecting tables during configuration of adataset, the following error message appears:
Timeout was reached when executing the dataset
Cause
The selection of tables carried out in the dataset configuration was cumbersome, resulting in the time limit for query execution being reached.
Solution
These are some possible solutions:
- Check the type of join made between the tables selected for the dataset.
- Use other fields to filter, such as identifier (id) or enumeration (enum) fields.

Situation
By informing theattributes of an analytic of the graphic type, no series suggestions are displayed:
Cause
At thedataset there is no item of the type compatible with the selected analytic series. Chart-type analytics (stack, bar, columns, etc.) allow any information in its category, but series information needs to be of the typeWhole orDecimal so that you can plot the graph correctly.
Solution
Here is a solution for this kind of problem:
Convert supported columns to typeWhole orDecimal;
To use numeric BPM form fields in analytic series, it is necessary to convert the types previously in the dataset, available only for the SQL editor.
Data conversion example:
select
CAST(t."decimal_field"as DOUBLE) as"cast_decimal_alias",
CAST(t."integer_field"as INTEGER) as"cast_integer_alias"
from
"platform-workflow"."bpm_process_name" t