Limitations on Crystal Console

This page is constantly updated. Stay tuned!

Last updated 9 months ago

Was this helpful?

This page is constantly updated. Stay tuned!

As an Admin User, you need to be aware of the many possibilities that Crystal offers as well as of some limitations that you might encounter.

A deep knowledge of Crystal allows you to make the most of the experience!

Let's see an overview of the limitations in the Console's capabilities, broken down by Area and Feature and summarized.

You will also be redirected to the specific Feature page to find out more details!

Stay Tuned!

We are constantly working to improve our product: check out the section of this documentation to learn about most recent fixes and enhancements!

Impacts on Conversation

In order to guarantee an optimal conversational experience for the Member User, a minimum of 5/6 Topics must be configured in Console. With less Topics, Crystal might encounter training problems and not be able to recognize Entities.

At the moment Crystal is not supporting complex fields like:
- “Json objects“ for Postgres
- “LOB“ for Oracle
If such field types are present in a table, Crystal will not be able to use them in the Topic Configuration process, nor to preview the related data

There are some restrictions on the use of special characters and punctuation signs in some fields, and in particular:
- Crystal doesn’t support column names that contain special characters like .(),%$…
  - The presence of a special symbol inside a column name is causing the failure of the Topic retrieval
- Crystal doesn’t support periods inside the schema name
- Crystal doesn’t support column names that include "/" for dynamic filters

As of now, Crystal is not supporting Groups hierarchy (Groups belonging to other Groups)

It is not possible to edit a Topic without unpublishing it first
It is not possible to delete a Topic that is in the statuses of "publishing", "unpublishing" or "published"

It is not possible to select a “number” column in the "group by" field for a table without binning, even if the number is an integer
For Multi-Entity visualizations, it is not possible to use different aggregations or column types on Entities

These are the maximum values available as you configure Topics:

You can’t set a required Filter without a default value
You cannot have more than three mandatory filters (excluding the time filter)
At the moment, the Filter Values are updated only during the publication or depublication of a Topic: there’s no automated way to update the Filter Values without a training action

It’s not possible to perform operations between different fields (es: column A + column B): you can create Custom Entities with aggregations instead

Last updated 9 months ago

Was this helpful?