Yes, you can absolutely perform a `GlideRecord` query against a database view. A database view in ServiceNow is essentially a read-only table, a dynamic join of other tables, that can be queried just like any standard table. You can instantiate `GlideRecord` with the name of the database view as the parameter. Once you have the `GlideRecord` object populated with data from the view, you can iterate through the results and use the retrieved values to populate and insert new records into your target custom table. This is a common and valid integration pattern for data syndication or transformation within the platform.
Regarding your second query, Access Control Lists (ACLs) can indeed be applied to database views. When you create an ACL, you specify the object it applies to, which can be a table or a database view. You can create `read` ACLs on the database view's name (e.g., `u_my_database_view`) to control which roles or conditions permit a user to see the records within that view. The system will evaluate these ACLs at runtime whenever a query is made against the view, enforcing the security constraints you've defined. This allows for granular control over the visibility of the joined data presented by the view, without altering the permissions on the underlying source tables.
If my response helped, kindly mark it as helpful & Accept it as Solution 🙂
Regards
Sumit
Technical Consultant
