IHub ETL getting REQUIRED_ATTRIBUTE_EMPTY when field is there

wingetc
Tera Contributor

 

When doing the Test and Rollback Integration Results in IHub ETL am getting the following:  

   Missing mandatory field "sys_class_name" in table "u_cmdb_ci_appl_ibm_iib".

The field is in the mapping and is mapping to target field "Class" and source field is "u_cmdb_ci_appl_ibm_iib".

First, why is it asking for class in the first place since I'm mapping to that class

Second,  what is the error actually saying?

1 ACCEPTED SOLUTION

Ashok Sasidhara
Tera Sage
Tera Sage

Ideally the mentioned error should not occur if you are filling the Class correctly for mapping. Did you check whether the name of Class from the source matches the actual Class name present in ServiceNow for the target Class for all entries? 

 

Also check whether the information given in the following kb article is helpful:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0723079

View solution in original post

5 REPLIES 5

Amarjeet Pal
Kilo Sage
Kilo Sage

Hello @wingetc ,

The error message is indicating that the `u_cmdb_ci_appl_ibm_iib` table in ServiceNow has a mandatory field named `sys_class_name`, which is not being mapped from your source data during the integration. The system is expecting this field to be included in the data being inserted or updated, but it's missing.

Regarding your first question, it appears that you are correctly mapping the `Class` target field to the `u_cmdb_ci_appl_ibm_iib` table in ServiceNow. However, there may be other mandatory fields in that table (such as `sys_class_name`) that also need to be mapped.

To resolve this issue, you will need to add a mapping for the missing `sys_class_name` field to your integration configuration so that it is included when inserting or updating records. You can check the schema of the target table in ServiceNow to determine which fields are mandatory and ensure they are all properly mapped.

Once you have made these changes, you can re-run your Test and Rollback Integration Results job to verify that the integration is now successful.

Thanks

Amarjeet Pal

but class is sys_class_name and I am filling it out

Ashok Sasidhara
Tera Sage
Tera Sage

Ideally the mentioned error should not occur if you are filling the Class correctly for mapping. Did you check whether the name of Class from the source matches the actual Class name present in ServiceNow for the target Class for all entries? 

 

Also check whether the information given in the following kb article is helpful:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0723079

wingetc
Tera Contributor

yep set that puppy to false and it works now