{"id":2934,"date":"2013-03-21T10:28:40","date_gmt":"2013-03-21T10:28:40","guid":{"rendered":"http:\/\/www.greytrix.com\/blogs\/sagex3\/?p=2934"},"modified":"2018-09-11T12:08:47","modified_gmt":"2018-09-11T12:08:47","slug":"determine-calling-screen-in-sage-x3","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sagex3\/2013\/03\/21\/determine-calling-screen-in-sage-x3\/","title":{"rendered":"Determine Calling Screen in Sage X3"},"content":{"rendered":"

There are several occasions where one screen calls up another screen. For e.g. if we call the Project screen from Task Screen, in this case, the source screen is \u201cTASK\u201d and the destination screen is \u201cPROJECT\u201d.<\/p>\n

Now but when we think of any technical parameter or variable which will be storing this value, we find Sage X3 has a variable called \u201cGFONCTION\u201d and \u201cGFONCTION1\u201d. These are global variables which store the Calling and Called screen function names.<\/p>\n

Also Read:<\/strong><\/em>\u00a0Call Screens through Code in Sage X3<\/a><\/p>\n

Now moving to an example which will give a better picture of this variable requirement: As you may know the PROJECT screen can be called from TASK Screen and APPOINTMENT Screen as well. If we wish to check which is the Calling Screen we just need to monitor the \u201cGFONCTION1\u201d variable.<\/p>\n

Just for your ready reference, we are jotting down the code; which will give you an idea of how the GFONCTION1 is used. The code checks the GFONCTION1 variable is equal to the \u201cGESOPP\u201d and further actions are performed.
\n\"\"<\/a><\/p>\n

About Us<\/strong><\/span>
\nGreytrix<\/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":"

There are several occasions where one screen calls up another screen. For e.g. if we call the Project screen from Task Screen, in this case, the source screen is \u201cTASK\u201d and the destination screen is \u201cPROJECT\u201d. Now but when we think of any technical parameter or variable which will be storing this value, we find\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":[8,11],"tags":[2020],"class_list":["post-2934","post","type-post","status-publish","format-standard","hentry","category-sage-erp-x3","category-tips","tag-screen"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/2934","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=2934"}],"version-history":[{"count":2,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/2934\/revisions"}],"predecessor-version":[{"id":15774,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/2934\/revisions\/15774"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/media?parent=2934"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/categories?post=2934"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/tags?post=2934"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}