{"id":8121,"date":"2016-01-04T05:36:24","date_gmt":"2016-01-04T05:36:24","guid":{"rendered":"http:\/\/www.greytrix.com\/blogs\/sagex3\/?p=8121"},"modified":"2021-08-04T06:29:10","modified_gmt":"2021-08-04T06:29:10","slug":"how-to-handle-the-errors-in-sage-x3-with-custom-message","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sagex3\/2016\/01\/04\/how-to-handle-the-errors-in-sage-x3-with-custom-message\/","title":{"rendered":"How to handle the errors in Sage X3 with custom message?"},"content":{"rendered":"

Here, we are going to look for the standard Sage X3 error handling process. It helps to trace error and passes error message to the end-user. Also it will helps to avoid interruption. In other word, it states the error and allow us to continue with the error messages.<\/p>\n

In Sage X3 when a number is divided by zero value it leads to an error \u2018Divide by Zero\u2019. After the error, user cannot continue further. Sage X3 has the feature to handle those errors with the help of \u201conerrgo\u201d.\u00a0 It is used to trace the error and handle it as well.<\/p>\n

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

The above code is to trace the error. \u00a0If no error exists, the catch block will not be called, so user can get the proper output.<\/p>\n

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

If error exists, it will call the catch block and show the custom message \u2018Divide by Zero error\u2019. So user can give proper input.<\/p>\n

Note<\/strong>: Finally, \u201cblock\u201d will be called in both the cases, Hence we can release or reset the variable.<\/p>\n

Hope this helps!<\/strong>
<\/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":"

Here, we are going to look for the standard Sage X3 error handling process. It helps to trace error and passes error message to the end-user. Also it will helps to avoid interruption. In other word, it states the error and allow us to continue with the error messages. In Sage X3 when a number\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,2796],"tags":[735,1946,1947,2263],"class_list":["post-8121","post","type-post","status-publish","format-standard","hentry","category-sage-erp-x3","category-technical","tag-error-in-sage-x3","tag-sage-x3-technical-iss","tag-sage-x3-technical-issues","tag-the-errors-in-sage-x3-with-custom-message"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/8121","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=8121"}],"version-history":[{"count":2,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/8121\/revisions"}],"predecessor-version":[{"id":22944,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/8121\/revisions\/22944"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/media?parent=8121"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/categories?post=8121"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/tags?post=8121"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}