Database view not showing specific fields

[MJL_]

Hi all,

I've created a database view and im seeing some strange behaviour maybe someone here knows whats going on. The database view is actually working fine but its not showing data in two fields that do have data on the acutal record.

The view consists out of three tables metric_instance/alm_hardware/sys_user . the metric is a duration metric on the assigned to field of the asset and the database view ties the tables together based on the metric ID and value / field_value.

From the alm_hardware table I want to see the display_name / install_state / substate / asset_tag and serial_number. The first 3 are showing just fine but the serial_number and asset_tag are blank in the database view.

Some extra info:

- the fields have been added to the view fields.

- i'm admin so I have the correct permisions.

- no issues with fields from the other tables or the other fields from the alm_hardware table.

- the actual records do containt data in those fields.

- i've tried removing and adding the fields etc.

The goal is that our IT staff can see what assets have been assigned to a user in the past and to what user an asset has been assigned to in the past.

Regards,

Matthijs

[katherine_s]

Thank you so much!  It was indeed an ACL issue : )   There are two OOB READ ACLs on the Asset table that only allows read of Serial number & Asset tag if Quantity is 1.  What is odd though is that all the assets have the default value of 1 and still they are not showing..!

[Alex Lawson]

Can I ask how you were able to resolve this issue? We're seeing the exact same problem with the asset and serial number fields in a DB view-based report.

[KatherineSh]

Apologies for the delayed response, I just saw this message!

We also had a case open with ServiceNow Support and ultimately resolved the issue by creating two new ACLs for the database view. These ACLs grant read access to the alm_asset_tag and alm_serial_number fields. This allowed us to maintain the integrity of the OOB ACLs while ensuring our users can still access those fields through the view.

Hope this helps!