Question on 'New' button on the 'Table' Form

cc11
Tera Contributor

Could somebody please help me figure how the 'New' button in the screenshot below was created & how its visibility is set?

I tried to look up 'Table' form's UI policies, Client Scripts, but I was unable to figure it out.

find_real_file.png

Fyi -

When I view my custom table, it shows the 'New' button.

However, when I view a table from a Global application — for example 'Embed Object' table , the button disappears.

Any help would be appreciated,

Regards,

Yogesh

1 ACCEPTED SOLUTION

antin_s
ServiceNow Employee
ServiceNow Employee

Hi Yogesh,



It comes from the OOB UI Macro -   'table_col_embedded_function'



Turn off the following property to false to hide the button.



ListProperties.setHasTopNavActionButtons(false);



Hope this helps. Mark the answer as correct/helpful based on impact.



Thanks


Antin


View solution in original post

17 REPLIES 17

antin_s
ServiceNow Employee
ServiceNow Employee

Hi Yogesh,



OOB or custom doesnt matter for this. I tried on an OOB instance. It works fine on both OOB and custom tables. Can you double check? Have you done any customizations?



Thanks


Antin


cc11
Tera Contributor

Hi Antin,



You are right. I think i may have changed some OOB objects unknowingly.


If its working for you, it must work for me as well.


Thanks for confirming that.



I will close the thread and will try to debug what I changed that caused it to break on my instance.



Thank you again,


Yogesh


cc11
Tera Contributor

Hi Antin,



Can you please share the screenshot below from your instance?


I want to check if the 'New' button appears for you for 'Embed Object' Table.



find_real_file.png


antin_s
ServiceNow Employee
ServiceNow Employee

Yes, Yogesh. I see it.



find_real_file.png




Do you have ACLs on it?



Thanks


Antin


cc11
Tera Contributor

Thanks Antin,



Please forgive my extreme lack of knowledge but I have no idea how to check ACLs.


If you could let me know, I would check it and update you.



Thank you again,


Yogesh