Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Unable to make record in 'sn_wsd_core_workplace_location' table inactive

Anita Nardin
Tera Contributor

Hello everyone, I would need to make a record (Building and Area) within the 'sn_wsd_core_workplace_location' table inactive but I'm unable to do so due to an OOB ACL (sn_wsd_core_workplace_location.active) which is preventing me to do so ('Active' field is read only).

 

Looking at the script it requires the role 'sn_wsd_core.location_writer' (which I have) but it looks like it only allows records with class "Site" and "Region" to be made inactive and nothing else - can anyone explain the rationale behind this? Is there another way we can achieve this?

 

I have seen another post on the community which suggested to use the "Block Location" UI Action or uncheck "Is Reservable" however unfortunately these would not satisfy our requirement as we would need to deactivate the records as the ref qualifier for our cat item looks for active records within the table.

 

Thank you!

2 REPLIES 2

Ankur Bawiskar
Tera Patron
Tera Patron

@Anita Nardin 

Do you want this record to be deactivated as part of some requirement or testing purpose?

-> if requirement purpose then ask security_admin user to give you this role so that you can deactivate that field level WRITE ACL in your correct scope update set

-> then ensure you migrate this update set

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

Julie Gordon
Mega Sage

2 thoughts. 

 

1.  I had a somewhat similar issue in that I didn't want a Building to show on specific widgets.  I ended up clearing the Parent field & this removed it from my widget, but still left it active for use on User Records & other places in the platform.

2. Elevate your role to security admin, deactivate the ACL, deactivate your building, then reactivate the ACL.

 

But with either suggestion, test it in a lower environment to verify that action(s) aren't impacting functionality in other parts of the platform.