Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Error on asset import from asset discovery

f.krupp November 19, 2024

I sometimes get the error on asset import from discovery: "Value cannot be empty"

I have already checked the cardinality of the appropriate type (PCs) and all attributes have a minimum cardinality of 0. As the label, I use the "name" field, which gets filled on the import with the FQDN field of the discovery scan. As the ID, I use the host hash.

I have no idea what field it could be, can I see that somewhere?

I can fix the issue by deleting the problematic objects and reimporting them, but this should not be the solution.

1 answer

0 votes
Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 19, 2024

Hi @f.krupp 

Check the import section on the schema and the view history button.

Check the object type mapping, might there be options set there in relation there.

f.krupp November 19, 2024

I don't see anything wrong in the object type mapping. It works for most of the objects, as it only shows errors for a few of them. Most are updated (89 updated, with 7 that throw errors).

Under the view history button, there is not much useful information, only the objects that are problematic and the "Value can not be empty" message.

Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 19, 2024

Hi @f.krupp 

So what kind of attributes are used on the object type, only options based on text or also other options based on "Default" type?

f.krupp November 19, 2024

The object type uses many different attributes: text, date and time, numerical, status, object.

For your information, I have now also raised a support ticket with the Atlassian support.

Like Marc - Devoteam likes this
Alan Bruce
Contributor
January 6, 2025

Was this ever resolved? I am getting the same errors on our import?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events