- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-25-2015 02:07 PM
Hello all,
I was playing around on a dev instance and created a Many to Many Definition. However, when I try to delete the entry I created, everything is greyed out. I saw that you have to turn off Access Control (ACL) on the sys_m2m delete function. I go to do that, but I don't have access despite having the admin role. When I look at the script, it says:
gs.hasRole("nobody");
But I cannot assign the role "nobody" to myself. Is this some kind of joke? Why in the heck would m2m, by default, prevent everyone including the admins from deleting a entry they JUST CREATED? Seriously guys, how do I delete this entry? It's messing up my dev stuff.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-25-2015 05:06 PM
Hi Matthew,
Make sure you have provided your account with the Security Admin role as well and elevate your privileges before trying to modify the ACL.
This should resolve your issue and allow you to update the script to remove the check for the "nobody" role.
If this has been helpful, please mark my response as such. Also, if this has answered your question, please remember to mark my response as the correct answer.
Kind Regards,
Mike
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-25-2015 06:55 PM
Hi Mike, great input! It's true the many to many definition would not be deleted, but the created m2m table will be deleted. That's why the created m2m table will appear with a red indicator, since the table does not longer exist. So, for instance, if our m2m table was u_m2m_incidents_users, the result of gs.tableExists(u_m2m_incidents_users) will then be false.
Thanks,
Berny