{"id":3988,"date":"2013-10-28T07:02:24","date_gmt":"2013-10-28T07:02:24","guid":{"rendered":"http:\/\/www.greytrix.com\/blogs\/sagex3\/?p=3988"},"modified":"2024-11-25T08:57:50","modified_gmt":"2024-11-25T08:57:50","slug":"how-to-filter-local-menu","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sagex3\/2013\/10\/28\/how-to-filter-local-menu\/","title":{"rendered":"How to filter Local Menu in Sage X3"},"content":{"rendered":"

In X3, we developer may come across with the requirement where we need to filter the local menu values for the fields. There are simple techniques available in X3 to filter the local menu values.<\/p>\n

Follow the below steps to filter the local menu field records:<\/p>\n

    \n
  1. The M data type of local menu is non-modifiable however in X3 there is alternate data type is available i.e. MM whose values we can modify at the runtime. Therefore use the MM data type for the local menu which you want to filter run time as shown in the below screenshot.<\/li>\n
  2. Add Before entry field action on that field.<\/li>\n<\/ol>\n

    \"LocalMenu1\"<\/a><\/p>\n

      \n
    1. The GMENLOC global variable can be used to filter the local menu values. We just need to set the GMENLOC(i) variable to 1 to deactivate the local menu values. It will be more preferable to set the values to GMENLOC variable in the Before Entry field action as it gets called before get focus to the field. Refer to the below snippet of code in which for the transmittal type field I have deactivated the 3rd<\/sup>, 4th<\/sup> and 5th<\/sup> value.<\/li>\n<\/ol>\n

      \"LocalMenu2\"<\/a><\/p>\n

        \n
      1. In the above example for the transmittal field we have deactivated the 3rd<\/sup>, 4th<\/sup> and 5th<\/sup> values and thus it is only showing the first 2 values.<\/li>\n<\/ol>\n

        \"LocalMenu3\"<\/a><\/p>\n

        Hope this helps!<\/p>\n

        About Us<\/strong><\/span>
        \n        Greytrix<\/a> \u2013 a globally recognized Premier Sage Gold Development Partner is a one-stop solution provider for Sage ERP and Sage CRM needs. Being recognized and rewarded for multi-man years of experience, we bring complete end-to-end assistance for your technical consultations, product customizations, data migration, system integrations, third-party add-on development and implementation expertise.<\/p>\n

        Greytrix<\/a>\u00a0caters to a wide range of Sage Enterprise Management (Sage X3) offerings \u2013 a Sage Business Cloud Solution. Our\u00a0unique GUMU™ integrations include Sage Enterprise Management (Sage X3) for Sage CRM<\/a>,\u00a0Salesforce.com<\/a> and\u00a0Magento eCommerce<\/a>\u00a0along with Implementation and Technical Support worldwide for Sage Enterprise Management (Sage X3)<\/a>. Currently we are Sage Enterprise Management Implementation Partner<\/a> in East Africa, Middles East, Australia, Asia.\u00a0We also offer best-in-class\u00a0Sage X3 customization and development services<\/a>,\u00a0integrated applications such as POS<\/a> | WMS<\/a> | Payment Gateway<\/a> | Shipping System<\/a> | Business Intelligence<\/a> | eCommerce<\/a> and have developed add-ons such as Catch \u2013 Weight <\/a>\u00a0and Letter of Credit<\/a> for Sage Enterprise Management to Sage business partners, end users and Sage PSG worldwide.<\/p>\n

        Greytrix is a recognized Sage Rockstar ISV Partner<\/a> for GUMU™ Sage Enterprise Management \u2013 Sage CRM integration also listed on Sage Marketplace<\/a>; GUMU™ integration for Sage Enterprise Management \u2013 Salesforce is a 5-star app listed on Salesforce AppExchange<\/a>.<\/p>\n

        For more information on Sage X3 Integration and Services, please contact us at\u00a0x3@greytrix.com<\/a>. We will be glad to assist you.<\/p>\n","protected":false},"excerpt":{"rendered":"

        In X3, we developer may come across with the requirement where we need to filter the local menu values for the fields. There are simple techniques available in X3 to filter the local menu values. Follow the below steps to filter the local menu field records: The M data type of local menu is non-modifiable\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[812,907,1177],"class_list":["post-3988","post","type-post","status-publish","format-standard","hentry","category-configuration","tag-filter","tag-gmenloc","tag-local-menu"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/3988","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\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/comments?post=3988"}],"version-history":[{"count":2,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/3988\/revisions"}],"predecessor-version":[{"id":30224,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/3988\/revisions\/30224"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/media?parent=3988"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/categories?post=3988"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/tags?post=3988"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}