Field length size increase from import set didn't get promoted to other environment

[Cupcake]

I did a Load data in DEV, and I noticed that one of the fields called Description was very lengthy and was truncating the information. Then I figured out that I had to increase the size of field within the Import Set itself. That resolved the problem.

My issue is after I do the initial load data, then I import the information to the other environments and it does not appear that the field length size of the description increased when I imported the data. So in my other environments the description field is truncated still.

So I am trying to figure out how can I increase that field size in the other environments when I did an import vs. a Load Data.

Please advise when you get a chance.

Karen

[Chuck Tomasi]

Hi Karen,

Are there any other questions/issues I can help answer here?

[Cupcake]

No but thank you. I think you answered my question.

Much appreciated.

Karen

[Chuck Tomasi]

Thanks for responding. Just double checking...

Since I have answered your question, please mark my response as correct so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list.

If you are viewing this from the community inbox you will not see the correct answer button.   If so, please review How to Mark Answers Correct From Inbox View.

Thank you

[Zuned2]

Hi Chuck, 

does this property "com. glide. loader. verify_target_field_size" really helps in  to automatically expand the staging table field length based on incoming data?