# Managing change in the column definition from source DB **URL:** \ **Category:** Matillion ETL\ **Created:** [September 7, 2023, 5:20am UTC](https://matillioncommunity.discourse.group/t/managing-change-in-the-column-definition-from-source-db/2277 "2023-09-07T05:20:04Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![PG881302](https://avatars.discourse-cdn.com/v4/letter/p/59ef9b/32.png) [@PG881302](https://matillioncommunity.discourse.group/u/PG881302)\ **Post date:** [September 7, 2023, 5:20am UTC](https://matillioncommunity.discourse.group/t/managing-change-in-the-column-definition-from-source-db/2277/1 "2023-09-07T05:20:04Z")
Hello!    We have a custom B2C digital platform with MongoDB as the backend. Recently, after its integration with one of our internal systems, a few tables in the platform's database backend were impacted. In one of the tables, a column, initially configured as type NUMBER(10), now also has character elements. The MongoDB load component recognises this column as Number(10) and defines it accordingly on Snowflake before loading the data. But, during the copy process, Snowflake throws an error because of the mismatch. ``` Numeric value 'XX123456' is not recognized  File 'ac9274f7-03cb-4370-8220-eec8a11deb65/ac9274f7-03cb-4370-8220-eec8a11deb65\_6', line 1, character 63  Row 1, column "TABLE\_NAME"["columnName":11] ```   Posting it here for help and suggestions on how this can be overcome.   Thanks, Prajwal ---
**Author:** ![ASD](https://sea2.discourse-cdn.com/flex002/user_avatar/matillioncommunity.discourse.group/asd/32/1323_2.png) [@ASD](https://matillioncommunity.discourse.group/u/ASD)\ **Post date:** [September 7, 2023, 7:51am UTC](https://matillioncommunity.discourse.group/t/managing-change-in-the-column-definition-from-source-db/2277/2 "2023-09-07T07:51:31Z")
Have you tried using convert type component after mongo db read to make it varchar?