Error with size field on SQL
Dear friends,
I am uning the Jira conector to get details about Issues openend. A few days ago was necessary to execute a migration on Jira and with this action the custom fields received the sufix (migrated).
After this process a facing to use the Dataset on SQL process.
The system has return the folowing error message:
""Identifier name must be 64 characters or less: 'DOD.6. Segurança e Negócio: Foram verificados os itens abaixo? (migrated 2)'."
Someone has a idea how to deal whit this problem.
Regards Genival Junior
Best Answer
-
Hi @user025461
This is because MySQL 5.6 (version Domo is built off of) doesn't support column names longer than 64 characters. You have a few options to work around this issue.
1) Use a Dataset view (or a magic ETL) to rename your column to something less than 64 characters and then use that dataset inside your MySQL dataflow
2) (Better Option) Convert your dataflow to a
MySQLMagic ETL 2.0 dataflow which will be much more performant and support the longer column names.**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**2
Answers
-
Is that error referencing a column name, or the data in a particular column?
**Check out my Domo Tips & Tricks Videos
**Make sure to any users posts that helped you.
**Please mark as accepted the ones who solved your issue.1 -
Hi @user025461
This is because MySQL 5.6 (version Domo is built off of) doesn't support column names longer than 64 characters. You have a few options to work around this issue.
1) Use a Dataset view (or a magic ETL) to rename your column to something less than 64 characters and then use that dataset inside your MySQL dataflow
2) (Better Option) Convert your dataflow to a
MySQLMagic ETL 2.0 dataflow which will be much more performant and support the longer column names.**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**2 -
Hi Grant,
How does it work to convert the Dataflow to MySQL 2.0 ?
I already solve my problem treating the field name in ETL, but this action could help me in another situations.
Best Regards,
Genival Junior
0 -
Apologies, I had MySQL on the brain but mean to state Magic ETL 2.0.
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**2
Categories
- All Categories
- 1.4K Product Ideas
- 1.4K Ideas Exchange
- 1.4K Connect
- 1.1K Connectors
- 282 Workbench
- 3 Cloud Amplifier
- 4 Federated
- 2.8K Transform
- 86 SQL DataFlows
- 548 Datasets
- 2.2K Magic ETL
- 3.2K Visualize
- 2.3K Charting
- 544 Beast Mode
- App Studio
- 26 Variables
- 566 Automate
- 134 Apps
- 411 APIs & Domo Developer
- 21 Workflows
- DomoAI
- 28 Predict
- 12 Jupyter Workspaces
- 16 R & Python Tiles
- 345 Distribute
- 87 Domo Everywhere
- 257 Scheduled Reports
- 1 Software Integrations
- 85 Manage
- 84 Governance & Security
- 9 Product Release Questions
- Community Forums
- 41 Getting Started
- 27 Community Member Introductions
- 81 Community Announcements
- 4.8K Archive