{"id":26753,"date":"2023-06-29T03:43:18","date_gmt":"2023-06-29T03:43:18","guid":{"rendered":"https:\/\/www.greytrix.com\/blogs\/sagex3\/?p=26753"},"modified":"2024-11-26T10:03:02","modified_gmt":"2024-11-26T10:03:02","slug":"defaulting-screen-mask-fields-in-sage-x3","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sagex3\/2023\/06\/29\/defaulting-screen-mask-fields-in-sage-x3\/","title":{"rendered":"Defaulting Screen\/Mask fields in Sage X3"},"content":{"rendered":"\n

In Sage X3<\/a>, every now and then a requirement requires a defaulting screen\/mask field with a value upon initialization or start of processing. To achieve this requirement, Sage X3 offers several ways such as scripting in the Action script under specific events or through screen dictionaries.
Below we are demonstrating how to default value through screen dictionary in Sage X3:<\/p>\n\n\n\n

We\u2019ll be referencing the following screen from Sage X3 for this:<\/p>\n\n\n\n

Product Master:<\/strong> All > Common Data > Product (GESITM)
Window Management:<\/strong> All > Development > Script dictionary > Windows (GESAWI)
Screen Management:<\/strong> All > Development > Script dictionary > Screens (GESAMK)<\/p>\n\n\n\n

Refer the screenshots for reference:<\/p>\n\n\n\n

-In the below Fig. 1 we can see that the reference product record Description 3 field is initialized as its stored data.<\/p>\n\n\n\n

New Stuff: <\/strong>Workflow in Sales Price List<\/a><\/p>\n\n\n\n

\"Fig.<\/a><\/center>\n
Fig. 1 – Desc. 3 original data<\/center><\/font>\n\n\n\n

-Now we\u2019re gonna show how to initialize this field as well as the Category field of Header from Screen management. For this navigate over to Windows management as shown below in Fig. 2 then jump onto the respective screens.<\/p>\n\n\n\n

\"Fig.<\/a><\/center>\n
Fig. 2 – Screens under OITM window<\/center><\/font>\n\n\n\n

-Under the screens ITM0 & ITM1 we\u2019ll look for the Fields tab and navigate over to the Default value column for our field codes within the grid as shown below in Fig. 3. We are initializing the fields with two ways:
-Normal Defaulting. (Fig. 3)
-Forced Defaulting – By putting an * symbol before the data. (Fig. 4)<\/p>\n\n\n\n

\"Fig.<\/a><\/center>\n
Fig. 3 – Passing a default data for the field<\/center><\/font>\n\n\n\n
\"Fig.<\/a><\/center>\n
Fig. 4 – Setting a default data for forced initialization<\/center><\/font>\n\n\n\n

-After setting the default values, save the screens and validate them and later perform a Window validation to take in effect. Now reopen the transaction screen for verifying the changes. We\u2019ll notice that the two things:
-FORCED DEFAULTING INITIALIZES DATA EVEN FOR CREATED RECORD as shown in Fig. 5.
-NORMAL DEFAULTING INITIALIZES ONLY FOR ENTERED DATA UPON NEW CREATION as shown in Fig. 6<\/strong><\/p>\n\n\n\n

\"Fig.<\/a><\/center>\n
Fig. 5 – Default value is forced initialized on field<\/center><\/font>\n\n\n\n
\"Fig.<\/a><\/center>\n
Fig. 6 – Both defaults working upon new creation<\/center><\/font>\n\n\n\n

This is how we can default data fields in two different ways using Screen defaulting in Sage X3.<\/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","protected":false},"excerpt":{"rendered":"

In Sage X3, every now and then a requirement requires a defaulting screen\/mask field with a value upon initialization or start of processing. To achieve this requirement, Sage X3 offers several ways such as scripting in the Action script under specific events or through screen dictionaries.Below we are demonstrating how to default value through screen\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":[8,13],"tags":[20,2542,3758,497,526,3755,3757,2020],"class_list":["post-26753","post","type-post","status-publish","format-standard","hentry","category-sage-erp-x3","category-integration","tag-4gl","tag-4gl-code","tag-creation","tag-data","tag-default","tag-forced","tag-initialize","tag-screen"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/26753","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=26753"}],"version-history":[{"count":12,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/26753\/revisions"}],"predecessor-version":[{"id":30249,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/26753\/revisions\/30249"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/media?parent=26753"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/categories?post=26753"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/tags?post=26753"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}