How to skip mandatory fields through discovery in Servicenow

[VPN]

Hi All,

We running discovery to discover Linux server. When we run the discovery we are getting Error : CMDB Identification Error: Missing required attribute: u_sox_l1

We understood that this error is because of mandatory custom fields on target table. As these fields are custom fields discovery wont get that CI information.

So to fix the issue we tried to keep default value through CI classifiers, But no luck.

we have several mandatory fields on CI table and we can not make them not mandatory. So could any one tell me how to set the default value for custom fields to avoid the error and create record.

Thanks.

[saprem_d]

Hi,

Do you have any data policy written which is making these fields as mandatory.

[Dave Smith1]

Vikas Pampari narsing wrote:

we have several mandatory fields on CI table and we can not make them not mandatory. So could any one tell me how to set the default value for custom fields to avoid the error and create record.

The point of making them mandatory is so that they contain data required to create the record.

It's possible to add something to the "on classification script" to populate this field, but I wouldn't go ahead and populate it just to create the record.   It's mandatory for a reason - you ought to check policy and determine why this field is so important.

[renancoelhosilv]

Hello Vikas,

Please see the following link:

Properties installed with Identification and Reconciliation

In particular "glide.required.attribute.enabled":

Flag for enforcing required attributes during identification and reconciliation so that attributes cannot be null.

• Type: true | false
• Default value: true
• Location: System Properties [sys_properties] table.

By setting this property to false you will be able to insert Cs via discovery even if the field is mandatory.

Thank you,

Regards,

Renan Coelho

[VaranAwesomenow]

https://hi.service-now.com/kb_view.do?sysparm_article=KB0723079

Set the sys-property "glide.required.attribute.enabled" to false. We already have required attributes as part of identifiers that are used for identification and reconciliation. Having Mandatory attributes on the class that are not brought in by discovery at Identification will result in the error.