It would be nice if EazyBI would support longer names for customfields defined in Advanced settings. Only 37 characters are support ed at the moment.
Our amount of such custom fields grows and it is better to give them clear names.
Not a big deal though, just nice to have.
Also, it would be nice to know it during saving of Advanced settings and not in import.
This limitation is implemented for Oracle database only. Some Oracle versions have limitations in using long custom field names on some scenarios that lead to import errors.
However, I will add this as a feature request for additional checks in eazyBI advanced settings or support the long field names for newer Oracle database versions.
Daina / support@eazybi.com
Hello, We are actually using PostgreSQL and not Oracle
I was not precise in my answer. The limitations apply to PostgreSQL as well.
Daina / support@eazybi.com
For the workaround, you may rename the custom filed (add a shorter version of its name) in eazyBI advanced settings. The settings might look like this where NNNNN is a custom field id in Jira:
[jira.customfield_NNNNN]
name = "Shorter version for cutomfield name"
There are more details on available parameters for custom fields: Advanced settings for custom fields - eazyBI for Jira
Best,
Zane / support@eazyBI.com