filed length modification is not effective through update set

learn nv
Tera Contributor

Hi All,

I have increase the length of the created by filed in attachment table and captured the change in an update set.

When I deployed to higher instance, the length of the filed is updated but not effective, so the issue our business facing is not resolved.

I manually modified the length of the filed, then the change is effective and not seeing any issues.

Can some one suggest what might be the cause for this behavior? How can I modify the length of the filed using update set effectively.

 

4 REPLIES 4

Valmik Patil1
Kilo Sage

Hello @learn nv ,

 

It might have happened that you missed capturing that change,

But you can export XML and import it to higher instances.

and can move files using XMLS. Try changing again and check if new entry is created or not in update set . if not created then try moving that using XML's

 

Thanks,

Valmik Patil

Change is captured properly in update set and I could see filed length is modified(to 50 from 40).

I think export and import of that record might work. I will check this way.

 

 

ok @learn nv ,

If you found out answer given by me helpful then could you please accept the solution and mark it as help full ðŸ™‚

Thanks in Advance,

Valmik Patil 

Dnyaneshwaree
Mega Sage

Please verify that the required change was captured in the migrated update set correctly or not. The field customizations are captured in the default application scope so, verify that it is not captured in another or default update set.

Please refer below posts:
https://www.servicenow.com/community/developer-forum/field-length-size-increase-from-import-set-didn...
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0745399

Please accept my solution if it works for you and thumps up.

Thank you!!

 

Please accept my solution if it works for you and thumps up to mark it as helpful.
Thank you!!

Dnyaneshwaree Satpute
Tera Guru