As the title suggests, I have created a custom m2m relationship between an OOTB table and a custom one.
While in the classic ServiceNow form I can see "New" and "Edit...",
when going into the workspace the only UI action that appears is a "New" button with a different behaviour from the classic UI one.
How can I have the Edit UI action in the workspace too? Since both the m2m relationship and one of the tables are custom, did I forget to configure something? Is this behaviour expected?
PS: List control works fine on classic UI but it's not affecting the workspace
Hello
I recently had a similar issue for an custom table (although my action was only displayed on selected records different from your usecase), after investigating I identified that the OOB edit declarative action had a flag called "Requires Write Access" set to true, and because I had some ACLs that prevented the users from writing on all the fields, this caused the security evaluation of the declarative action to fail.
What I personally do to try and debug these issues is to just edit the oob one, but not set any condition / security flags, to see if it is a access problem, then I revert back to oob version. I also use the access-analyzer to try and debug the overall access conditions.
Another situation could be that the table could also be part of the exclusion list of the declarative action itself
It could also be that the Action is only displayed if at least 1 entry being clicked on (I don't have VR to validate).
You can also have a look at this article which goes into it in more detail : SOLVED: Workaround for "Edit ..." buttons on Relat... - ServiceNow Community
Hope it helps.
