Making a sn_wsd_core_space inactive is being blocked?

Travis Michigan
Mega Sage

Kind of curious if I'm following something wrong or maybe if someone could help me to understand why something works the way it does with wsd spaces and indoor mapping.  

 

When a location needed to be temporarily disabled, I thought that we would just need to go to the sn_map_core_place  and relevant sn_map_core_space and mark them inactive.  However with the sn_map_core_space the Active box is read only for me.  Which I thought was really weird because I can delete it, why can I not make it inactive?  I tried to just uncouple the two and still could not make it inactive.  I ended up being able to accomplish the same thing by just changing the wsd_status to empty and that made the sn_map_core_space also inactive.  

 

I tried to follow the security for it and if I'm following it right (entirely possible that I am way off here) it seems like it requires security_admin to be able to set that to inactive by clicking the Active box.  But that doesn't make sense to me as I can delete it so why would I be restricted from making it only inactive?  If anyone can shed some light on this I would greatly appreciate it!  

TravisMichigan_0-1747251742896.png

 

 

1 REPLY 1

Raj_Esh
Kilo Sage
Kilo Sage

Hi @Travis Michigan 

 

If you want the space to be blocked for certain time period, you can use the "Block Location" UI Action in sn_wsd_core_space table. 

 

or You can simple uncheck "Is Reservable" on same table.

 

Hope it helps.

 

--Raj