---
title: "DataShed4 - Field too small error when loading assays - fnLoadBufferCSVBatchHeader"
canonical: "https://servicedesk.maxgeo.com/space/MAXGEO/1052868609/DataShed4%20-%20Field%20too%20small%20error%20when%20loading%20assays%20-%20fnLoadBufferCSVBatchHeader"
format: markdown
---
**Issue**: When loading assay files get an error -

*The field is too small to accept the amount of data you attempted to add. Try inserting or pasting less data.*

**Reason**: The Dispatch Number in the assay file being loaded is longer than 20 characters.

Note: Dispatch_No in tblSYSImportMaskField set at 20 but the destination Dispatch_No in tblSYSAssBatch is nvarchar(50)

**Solution**: TRun attached script to update field sizes - note resets 3 other fields at the same time.

```sql
IF ((Select SUBSTRING(Param1,1,3) From tblSYSParam Where CodeGroup = 'BACKEND' and Code = 'VERSION') = '4.6')
BEGIN
Update tblSYSImportMaskField set Field_Size = 50 Where Field_Name = 'Dispatch_No'
Update tblSYSImportMaskField set Field_Size = 25 Where Field_Name = 'LabElement'
Update tblSYSImportMaskField set Field_Size = 25 Where Field_Name = 'OrigMethod'
Update tblSYSImportMaskField set Field_Size = 25 Where Field_Name = 'UnitCode'
END
```

![image](media://28407024-d42b-44d2-963f-5c1f0fd7167d)

> ⚠️ DB Modification
> ⚠️ 
> ⚠️ Before any change is made to a user database (or system), maxgeo recommends competent staff should follow all standard database change management practices and never make untested changes to a production database.  
> ⚠️ Change, test and document all modifications on a test copy of your database to ensure results are as expected before implementing them on your live database. Always ensure a full backup is available in case rollback is required and follow all company change management procedures and practices.