How to troubleshoot / fix truncation of data with IntegrationHub Import from App Engine Studio (AES)Issue In Application Engine Studio, you have the ability to import data from an Excel sheet, for example. This uses the IntegrationHub Import functionality. As with any import, you might see truncation issues related to the import set staging table. This article will guide you through the troubleshooting steps to find and fix the staging table setup.SymptomsWhile your import target table has the field sized appropriately, you still see truncated Data when importing data from the Data segment in the Application Engine Studio (AES).ReleaseSan Diego and higherCauseThese truncations are caused by fields in the import set staging table that are too small for the intended dataResolutionSince the AES is using integrationhub imports for loading the data, you will follow the integration hub path to find the staging table. You will find a subflow execution that runs the import data load and triggers the transform. You will also find a data source that is in your AES application (search for your application name in the data source application field) You can find the robust transformer either from that data source, or by searching for a robust transform ETL Definition that belongs to your application (search for your application name in the data source application field) From the robust transform etl definition, check the defined ETL entities. One will be the source (import set table) entity, one will be the target (target table) entity and you will also find a temp entity that is virtual only. To fix the truncation issue, go to the source table with .LIST from the filter navigator. Then right click on the list header and choose Configure>Dictionary. Find the truncated field and increase the length to a length value that will fit your largest incoming data for that field. Save the dictionary record and future imports should no longer truncate the data.