{"id":30617,"date":"2025-01-30T11:16:34","date_gmt":"2025-01-30T11:16:34","guid":{"rendered":"https:\/\/www.greytrix.com\/blogs\/sagex3\/?p=30617"},"modified":"2025-01-30T11:18:25","modified_gmt":"2025-01-30T11:18:25","slug":"how-to-hide-the-button-in-line-level-of-grid-in-sage-x3","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sagex3\/2025\/01\/30\/how-to-hide-the-button-in-line-level-of-grid-in-sage-x3\/","title":{"rendered":"How to hide the button in line level of grid in sage X3"},"content":{"rendered":"\n<p>In <a href=\"https:\/\/www.greytrix.com\/sage-x3-erp\/development-services\/\" data-type=\"link\" data-id=\"https:\/\/www.greytrix.com\/sage-x3-erp\/development-services\/\">Sage X3<\/a>, we came across a situation where we need to hide a button at the line level within a grid. This functionality can be achieved by following the steps given below.<\/p>\n\n\n\n<p>In our example, the user wants to hide the &#8220;Change of Receipt&#8221; button at the line level (as shown in Figure 1) for a specific transaction type, i.e RET (Return GRN) as shown in Figure 2.<\/p>\n\n\n\n<p><strong>New Stuff:<\/strong> <a href=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/2025\/01\/30\/how-to-print-comments-data-longer-than-250-characters-on-crystal-reports-at-once-in-sage-x3\/\" data-type=\"link\" data-id=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/2025\/01\/30\/how-to-print-comments-data-longer-than-250-characters-on-crystal-reports-at-once-in-sage-x3\/\">How to print comments data longer than 250 characters on Crystal Reports at once in Sage X3<\/a><\/p>\n\n\n\n<center><a href=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-content\/uploads\/2025\/01\/Receit-Screen.jpg\" target=\"_blank\" rel=\"noreferrer noopener\"><img decoding=\"async\" class=\"size-full\" style=\"border: 1px solid #A9A9A9; padding: 2px; margin: 2px; align: center;\" src=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-content\/uploads\/2025\/01\/Receit-Screen.jpg\" alt=\"Receipt Screen\"><\/a><\/center>\n<font size=\"2\"><center>Receipt Screen<\/center><\/font>\n\n\n\n<center><a href=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-content\/uploads\/2025\/01\/Transaction-List.jpg\" target=\"_blank\" rel=\"noreferrer noopener\"><img decoding=\"async\" class=\"size-full\" style=\"border: 1px solid #A9A9A9; padding: 2px; margin: 2px; align: center;\" src=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-content\/uploads\/2025\/01\/Transaction-List.jpg\" alt=\"Transaction List\"><\/a><\/center>\n<font size=\"2\"><center>Transaction List<\/center><\/font>\n\n\n\n<p>To remove the button, we need to follow mentioned steps:<\/p>\n\n\n\n<p>Navigate to Windows(OPTH)->Screens(PTH1).<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Add an &#8220;Init Button&#8221; field action to the NBLIG field as shown in Figure 3.<\/li>\n\n\n\n<li>Add a specific action (SPE) so that it is applied to the relevant script (SPEPTH).<\/li>\n\n\n\n<li>Implement the code as shown in Figure 4.<\/li>\n<\/ol>\n\n\n\n<center><a href=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-content\/uploads\/2025\/01\/screen-1024x488.jpg\" target=\"_blank\" rel=\"noreferrer noopener\"><img decoding=\"async\" class=\"size-full\" style=\"border: 1px solid #A9A9A9; padding: 2px; margin: 2px; align: center;\" src=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-content\/uploads\/2025\/01\/screen-1024x488.jpg\" alt=\"screen\"><\/a><\/center>\n<font size=\"2\"><center>screen<\/center><\/font>\n\n\n\n<center><a href=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-content\/uploads\/2025\/01\/Scipt-code.jpg\" target=\"_blank\" rel=\"noreferrer noopener\"><img decoding=\"async\" class=\"size-full\" style=\"border: 1px solid #A9A9A9; padding: 2px; margin: 2px; align: center;\" src=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-content\/uploads\/2025\/01\/Scipt-code.jpg\" alt=\"Script code\"><\/a><\/center>\n<font size=\"2\"><center>Script code<\/center><\/font>\n\n\n\n<p>Here<br>Within this action,<br>[V]GBOUTX, where GBOUT is the keyword used for button and X represents the button number<br>(i.e 5 \u2013 (Change of Receipt) in our case ).<\/p>\n\n\n\n<center><a href=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-content\/uploads\/2025\/01\/Receipt-Screen-Without-Button.jpg\" target=\"_blank\" rel=\"noreferrer noopener\"><img decoding=\"async\" class=\"size-full\" style=\"border: 1px solid #A9A9A9; padding: 2px; margin: 2px; align: center;\" src=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-content\/uploads\/2025\/01\/Receipt-Screen-Without-Button.jpg\" alt=\"Receipt Screen Without Button\"><\/a><\/center>\n<font size=\"2\"><center>Receipt Screen Without Button<\/center><\/font>\n\n\n\n<p>As shown in above Figure 5 we have hide the button on Receipt screen for return transaction.<\/p>\n\n\n[about_us_blog_common]\n","protected":false},"excerpt":{"rendered":"<p>In Sage X3, we came across a situation where we need to hide a button at the line level within a grid. This functionality can be achieved by following the steps given below. In our example, the user wants to hide the &#8220;Change of Receipt&#8221; button at the line level (as shown in Figure 1)\u2026 <span class=\"read-more\"><a href=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/2025\/01\/30\/how-to-hide-the-button-in-line-level-of-grid-in-sage-x3\/\">Read More &raquo;<\/a><\/span><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8,13],"tags":[239,933,1161,1822,2020],"class_list":["post-30617","post","type-post","status-publish","format-standard","hentry","category-sage-erp-x3","category-integration","tag-button","tag-grid","tag-lines","tag-sage-x3","tag-screen"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/30617","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/comments?post=30617"}],"version-history":[{"count":9,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/30617\/revisions"}],"predecessor-version":[{"id":30628,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/30617\/revisions\/30628"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/media?parent=30617"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/categories?post=30617"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/tags?post=30617"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}