Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Fields size monitoring and harmonization

naxis alx
Tera Contributor

I have encounter this issue with CMDB

 

The intune table definition sets the IMEI field size a 255. Of fact, the IMEI discover by Intune is very long. For example the mobile devices with 2 SIMs have a very long string as IMEI

356796117431794,CTSubscriptionSlotTwo:356796117353238

The CMDB Handheld Computing Device table that is supposed to hold the this information in the IMEI field has a field size that is set to 40.

 

Why this is not harmonized at OOTB level and monitored?

1 REPLY 1

Mateus Oliveira
Tera Guru

Hello @naxis alx ,

 

From my experience I have not encountered this issue yet. We have been using this class with the OOTB 40 length string without any issue. But you do seem to have a good use case which I believe should be reported to ServiceNow via a HI ticket so they can harmonize it for future releases. I don't think it has been as of now.

 

In the meanwhile, you can change the length of this attribute as a workaround even that being an OOTB table without much issue.