{"id":21816,"date":"2021-02-22T11:07:25","date_gmt":"2021-02-22T11:07:25","guid":{"rendered":"http:\/\/www.greytrix.com\/blogs\/sagex3\/?p=21816"},"modified":"2021-02-22T11:07:30","modified_gmt":"2021-02-22T11:07:30","slug":"how-to-make-multiple-selection-of-transaction-in-single-field","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sagex3\/2021\/02\/22\/how-to-make-multiple-selection-of-transaction-in-single-field\/","title":{"rendered":"How to make multiple selection of transaction in single field"},"content":{"rendered":"\n

In Sage X3, there are various types of transactions for different modules such as sales order, purchase order, sales invoice, purchase invoice, customer BP invoice, etc. Sage X3 have feature of selection that is a \u201clookup\u201d button on fields which helps the user to choice a particular selection. Sometimes there may be requirement for particular customized screen where it is required to have multiple selection of various transactions on single field.<\/p>\n\n\n\n

This can be achieved by adding few fields and manipulation of data into those fields. First of all, the datatype of the selection field should be \u201cVCR\u201d and the parameters should be blank.Sage X3 allows to have two types of selections, that is object based selection and non-object based selection. Non-object based selections can be achieved by using SELLINA which requires one action and specific script which possess the code to fetch data from existing tables and display them. It elongates the process and time consumption for filtering the data from tables, hence we will use object based selection. Object based selections basically work on objects of that transaction and field which stores entry transaction number of that transaction. For obtaining multiple selection in single field using object based selection, follow below steps. Consider a test screen which contains fields for selecting different types of transactions such as sales invoice, customer BP invoice, sales order, purchase order, etc.<\/p>\n\n\n\n\n\n

Add action type as \u201cSelection\u201d and action as \u201cSELOBJET\u201d as shown in below figure. SELOBJET is predefined action for selection which requires object code and field which stores entry transaction number. Since object code and field storing transaction number for each transaction is different so will store it in another field, here as \u201cEntry number\u201d field. For example, if its Sales order, then it would be storing \u201cSOHNUM\u201d, if purchase order then \u201cPOHNUM\u201d which will be passed in action parameters of selection field in mask of added field, here \u201cZNUM\u201d. Similarly, for different transactions object code and transaction number fields will be different. As can be seen in below figure in \u201cCODZON\u201d action parameter ZNUM is passed and in OBJET parameter ZOBJECT is passed.<\/p>\n\n\n\n\n\n

Once done with the above changes validate the screen and the globally validate the window associated with that screen. Navigate to the test screen, you will be able to see the below figure.<\/p>\n\n\n\n

\"\"\/
Fig 03: Test screen<\/strong><\/figcaption><\/figure>\n\n\n\n

Select any transaction type from the option and hit on the look up button of the selection field. You will be able to see the selection of invoice as shown in in below figure.<\/p>\n\n\n\n\n\n

Similarly, if selected any other transaction type for example \u201cSales Order\u201d, then selection of sales order will appear in selection.<\/p>\n\n\n\n

\"\"\/
Fig 05: Sales Order selection<\/strong><\/figcaption><\/figure>\n\n\n\n

Thus, we can have multiple selection of multiple transactions in single field.<\/p>\n\n\n\n

This blog helps us to make multiple selection of any transaction in single field.<\/p>\n\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\n\n\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

In Sage X3, there are various types of transactions for different modules such as sales order, purchase order, sales invoice, purchase invoice, customer BP invoice, etc. Sage X3 have feature of selection that is a \u201clookup\u201d button on fields which helps the user to choice a particular selection. Sometimes there may be requirement for particular\u2026 Read More »<\/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":[3162,8,10,2796,11],"tags":[49,1839,1945,2020,3155,2283,2324],"class_list":["post-21816","post","type-post","status-publish","format-standard","hentry","category-greytrix","category-sage-erp-x3","category-standard","category-technical","category-tips","tag-actions","tag-sage-x3-blogs","tag-sage-x3-technical-blogs","tag-screen","tag-selection-screen","tag-transaction","tag-usage"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/21816","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=21816"}],"version-history":[{"count":1,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/21816\/revisions"}],"predecessor-version":[{"id":21849,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/21816\/revisions\/21849"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/media?parent=21816"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/categories?post=21816"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/tags?post=21816"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}