\nIt is an object action that is called as and when a field is modified. We have defined the action which occurs just before the APRES_MODIF is fired.<\/p>\n
- \n
- After the field AM_<\/strong> (After Change) action.<\/li>\n
- Before the [M]<\/strong> class is updated with the new value.<\/li>\n<\/ul>\n
Following are the available variables with this action:<\/p>\n
COUZON<\/strong>: Name of current field.
\nCZ<\/strong>: Current value of field.
\nCOUIND<\/strong>: Current index (Array fields).<\/strong><\/p>\nThe AM_XXX<\/strong> action:
\nThis action fires After Modification of the screen fields XXX on the screen, but to trace this action user need to define the action type against the respective field.<\/p>\nThe Action type selected is \u2018After Change\u2019 the Screen Dictionary. This action comes with a default parameter \u2018VALUER\u2019. The VALUER contains current field value whereas [M] XXX contains the value before the field was modified.<\/p>\n
Difference between the 2 actions:<\/strong>
\nAPRES_MODIF:
\n<\/strong>APRES_MODIF is an object action. Object actions are global events that are executed when users maintain or navigate through records in an object. Object Actions are triggered any time a user accesses an object, navigates through records, any event triggered using the action buttons, refreshes the screen, changes the left browser, creates, modifies or deletes an object etc.
\nCode View<\/span><\/strong>:<\/strong>
\n####################################################################################<\/em>
\n$ACTION
\nCase ACTION
\nWhen \u2018APRES_MODIF\u2019 : Gosub APRES_MODIF
\nWhen Default
\nEndcase
\nRETURN<\/em>
\n####################################################################################<\/em>
\n####################################################################################<\/em>
\n$APRES_MODIF<\/em>
\nFor I=0 To 2
\nIf evalue(“dim([M:ZPH”+num$(I)+”]DACDIA)>0 & [M:ZPH”+num$(I)+”]DACDIA<>'”+[F:ZPH]DACDIA+”‘”)
\nCase I
\nWhen 0 : [M:ZPH0]DACDIA=[F:ZPH]DACDIA : Affzo [ZPH0]DACDIA
\nWhen 1 : [M:ZPH1]DACDIA=[F:ZPH]DACDIA : Affzo [ZPH1]DACDIA
\nWhen 2 : [M:ZPH2]DACDIA=[F:ZPH]DACDIA : Affzo [ZPH2]DACDIA
\nEndcase
\nBreak
\nEndif
\nNext I
\nRETURN<\/em>
\n####################################################################################<\/em>
\nHere, we are checking three fields on three different screens for change in value and are accordingly enabling it. This way, APRES_MODIF can be used when we need to validate or execute a function on update of any field on the screen (not only one.) <\/strong><\/p>\nAM_XXX:<\/strong>
\nThe AM_XXX is a field action assigned against any specific field of the screen dictionary. Thus the action is fired whenever any change is registered against the specific field.
\n![\"\"](\"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-content\/uploads\/2012\/02\/AM_REGDAT.bmp\")
<\/a>
\nCode View:<\/span><\/strong>
\n####################################################################################<\/em>
\n## Section automatically added (screen XDM0) <\/em>
\n####################################################################################<\/em>
\nSubprog AM_REGDAT (VALUER)<\/em>
\nVariable Date VALUER<\/em>
\nIf VALUER > date$<\/em>
\n Infbox \u201cThe registration date cannot be greater than current date.\u201d <\/em>
\n mkstat = 2 <\/em>
\nEndif <\/em>
\nEnd<\/em>
\n####################################################################################<\/em>
\nThis way, the AM_XXX action can be used for the validation of a specific field or to fire functions specific to that field.<\/strong>
\nHope this clarifies the confusion between the 2 actions.<\/p>\nEnjoy Coding in X3. For some quick help please free to contact us on x3@greytrix.com<\/strong><\/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>\nGreytrix<\/a> caters to a wide range of Sage Enterprise Management (Sage X3) offerings \u2013 a Sage Business Cloud Solution. Our unique GUMU\u2122 integrations include Sage Enterprise Management (Sage X3) for Sage CRM<\/a>, Salesforce.com<\/a> and Magento eCommerce<\/a> along 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. We also offer best-in-class Sage X3 customization and development services<\/a>, integrated 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> and 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\u2122 Sage Enterprise Management \u2013 Sage CRM integration also listed on Sage Marketplace<\/a>; GUMU\u2122 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 x3@greytrix.com<\/a>. We will be glad to assist you.<\/p>\n","protected":false},"excerpt":{"rendered":"
We have come across many technical queries regarding the actions of Sage ERP X3, one of them was \u201cCould anybody tell me what is the major difference between field after the change (AM_XXX) and APRES_MODIF events, and which of them better to use?\u201d It quite true that in X3 with so many events at our\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],"tags":[49,119,2472,131,2471],"class_list":["post-165","post","type-post","status-publish","format-standard","hentry","category-sage-erp-x3","tag-actions","tag-am","tag-am-xxx","tag-apres","tag-apres-modif"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/165","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=165"}],"version-history":[{"count":3,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/165\/revisions"}],"predecessor-version":[{"id":27533,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/165\/revisions\/27533"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/media?parent=165"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/categories?post=165"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/tags?post=165"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- Before the [M]<\/strong> class is updated with the new value.<\/li>\n<\/ul>\n