{"id":8405,"date":"2016-02-29T11:07:47","date_gmt":"2016-02-29T11:07:47","guid":{"rendered":"http:\/\/www.greytrix.com\/blogs\/sagex3\/?p=8405"},"modified":"2021-08-04T06:58:12","modified_gmt":"2021-08-04T06:58:12","slug":"handling-the-customized-fields-using-entry-transaction-in-sage-x3","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sagex3\/2016\/02\/29\/handling-the-customized-fields-using-entry-transaction-in-sage-x3\/","title":{"rendered":"Handling the Customized Fields Using Entry Transaction in Sage X3"},"content":{"rendered":"

In Sage X3, whenever we do any change on transaction screens like order, shipment, receipts or any other screens, we need to validate Entry Transaction. But, we may come across a scenario where user wants the modifications to behave differently depending on the transaction selections.<\/p>\n

For e.g., A customized field on Sales Order is to be enterable<\/em> in transaction ALL<\/em> but, to be displayed<\/em> in another transaction ZALL<\/em>. If we do so and later, user wants the Customer field input set to be as displayed<\/em> in ALL<\/em> transaction then performing the modifications on SO screen again, takes significant time. We can avoid these steps by using entry transaction screen.<\/p>\n

Perform following steps to achieve the same:<\/p>\n

Steps:<\/strong><\/p>\n

    \n
  1. Navigate to:<\/strong> Setup > Sales > Entry Transactions > Order<\/li>\n
  2. Navigate to:<\/strong> Development > Processing dictionary > Screens > Screens<\/li>\n
  3. Add field on Entry Transaction screen. Refer the screenshot below for the same:<\/li>\n<\/ol>\n

    \"Add<\/a>4. Set the values of Input (Entry\/Displayed\/Hidden)<\/em> and Mode (Form\/Table\/Form & Table)<\/em> as per requirement.<\/p>\n

    Refer the below screenshot for the same.<\/p>\n

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

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

    5. Refer following snippet of code to make this functionality work:<\/p>\n

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

    6.Perform Entry Transaction validation.<\/p>\n\n\n

    About Us<\/strong><\/h2>\n\n\n\n

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

    Greytrix has some unique integration solutions developed for Sage CRM<\/a> with Sage ERPs namely Sage X3<\/a>, Sage Intacct<\/a>, Sage 100<\/a>, Sage 500<\/a>, and Sage 300<\/a>. We also offer best-in-class Sage ERP and Sage CRM customization and development services to Business Partners, End Users, and Sage PSG worldwide. Greytrix helps in the migration of Sage CRM from Salesforce | ACT! | SalesLogix | Goldmine | Sugar CRM | Maximizer. Our Sage CRM Product Suite includes addons like  Greytrix Business Manager, Sage CRM Project Manager, Sage CRM Resource Planner, Sage CRM Contract Manager, Sage CRM Event Manager, Sage CRM Budget Planner, Gmail Integration, Sage CRM Mobile Service Signature, Sage CRM CTI Framework.<\/p>\n\n\n\n

    Greytrix is a recognized Sage Champion Partner for GUMU™ Sage X3 \u2013 Sage CRM integration listed on Sage Marketplace<\/a> and Sage CRM \u2013 Sage Intacct integration listed on Sage Intacct Marketplace<\/a>. The GUMU™ Cloud framework<\/a> by Greytrix forms the backbone of cloud integrations that are managed in real-time for the processing and execution of application programs at the click of a button.<\/p>\n\n\n\n

    For more information on our integration solutions, please contact us at sage@greytrix.com<\/a>. We will be glad to assist you.<\/p>\n","protected":false},"excerpt":{"rendered":"

    In Sage X3, whenever we do any change on transaction screens like order, shipment, receipts or any other screens, we need to validate Entry Transaction. But, we may come across a scenario where user wants the modifications to behave differently depending on the transaction selections. For e.g., A customized field on Sales Order is to\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2,3162,8,10,2796,11],"tags":[734,966,1942,1945,1947],"class_list":["post-8405","post","type-post","status-publish","format-standard","hentry","category-configuration","category-greytrix","category-sage-erp-x3","category-standard","category-technical","category-tips","tag-error-in-sage","tag-handling-the-customized-fields-using-entry-transaction-in-sage-x3","tag-sage-x3-technical-assistance","tag-sage-x3-technical-blogs","tag-sage-x3-technical-issues"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/8405","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=8405"}],"version-history":[{"count":1,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/8405\/revisions"}],"predecessor-version":[{"id":22973,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/8405\/revisions\/22973"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/media?parent=8405"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/categories?post=8405"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/tags?post=8405"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}