{"id":28548,"date":"2024-02-27T06:32:59","date_gmt":"2024-02-27T06:32:59","guid":{"rendered":"https:\/\/www.greytrix.com\/blogs\/sagex3\/?p=28548"},"modified":"2024-11-26T10:24:34","modified_gmt":"2024-11-26T10:24:34","slug":"how-to-customize-the-trace-log-file-for-errors-and-success-messages","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sagex3\/2024\/02\/27\/how-to-customize-the-trace-log-file-for-errors-and-success-messages\/","title":{"rendered":"How to customize the trace log file for errors and success messages"},"content":{"rendered":"\n

Trace files are extensively utilized in Sage X3<\/a> software, particularly during lengthy processes like Automatic Invoice Validation or Automatic Work Order Release. When a trace file is displayed, error lines appear in red text, allowing you to navigate through the errors.<\/p>\n\n\n\n

To customize a trace file, follow the below steps:<\/p>\n\n\n\n

Step 1: <\/strong>We need to open the trace file using the ‘OUVRE_TRACE’ function, as shown in the code below.<\/p>\n\n\n\n

New Stuff:<\/strong> How to show comma-separated value for single or multiple fields in Sage X3 reports using crystal report<\/a><\/p>\n\n\n\n

\"[Open_Trace_Log_File_Code]\"<\/a><\/center>\n
[Open_Trace_Log_File_Code]<\/center><\/font>\n\n\n\n

Step 2:<\/strong> After opening the log file, we can insert any messages as per our requirements.<\/p>\n\n\n\n

Note: <\/strong>To customize a trace file, it’s essential to understand the color codes associated with different messages:<\/p>\n\n\n\n

0: Used to display messages in black color.
1: Used to indicate error messages in red color.
-1: Used to present messages in green color.
-2: Used to showcase messages in blue color.<\/p>\n\n\n\n

Step 3:<\/strong> Insert a message line using the ‘ECR_TRACE’ function. This function takes two parameters: the first parameter contains the message, and the second contains the color code, as shown in the code below.<\/p>\n\n\n\n

\"[Inserting_Message_Trace_Log_File_Code]\"<\/a><\/center>\n
[Inserting_Message_Trace_Log_File_Code]<\/center><\/font>\n\n\n\n

Step 4:<\/strong> After inserting messages, we need to close this trace file using the ‘FERME_TRACE’ function.<\/p>\n\n\n\n

\"[Close_Trace_Log_File_Code]\"<\/a><\/center>\n
[Close_Trace_Log_File_Code]<\/center><\/font>\n\n\n\n

Step 5:<\/strong> Now we can display our trace log file using the ‘LEC_TRACE’ function.<\/p>\n\n\n\n

\"[Display_Trace_Log_File_Code]\"<\/a><\/center>\n
[Display_Trace_Log_File_Code]<\/center><\/font>\n\n\n\n

Step 6: <\/strong>If you want to delete this trace file, you can use the ‘SUPP_TRACE’ function.<\/p>\n\n\n\n

\"[Delete_Trace_Log_File_Code]\"<\/a><\/center>\n
[Delete_Trace_Log_File_Code]<\/center><\/font>\n\n\n\n

After executing this script, you can view the log file as depicted in the screenshot below.<\/p>\n\n\n\n

Note:<\/strong> If you added an error message using the code ‘1’ in the ‘ECR_TRACE’ function, you will receive a popup indicating the number of errors before the log file.<\/p>\n\n\n\n

\"[Number_Of_Errors]\"<\/a><\/center>\n
[Number_Of_Errors]<\/center><\/font>\n\n\n\n
\"[Log_Reading_Screen]\"<\/a><\/center>\n
[Log_Reading_Screen]<\/center><\/font>\n\n\n\n

By following the above steps, we can customize the trace log file for errors and success messages.<\/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":"

Trace files are extensively utilized in Sage X3 software, particularly during lengthy processes like Automatic Invoice Validation or Automatic Work Order Release. When a trace file is displayed, error lines appear in red text, allowing you to navigate through the errors. To customize a trace file, follow the below steps: Step 1: We need to\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":[4040,863,1193,4039,4038,4037],"class_list":["post-28548","post","type-post","status-publish","format-standard","hentry","category-sage-erp-x3","category-integration","tag-errors","tag-functions","tag-log","tag-messages","tag-success","tag-trace-log"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/28548","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=28548"}],"version-history":[{"count":10,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/28548\/revisions"}],"predecessor-version":[{"id":30255,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/28548\/revisions\/30255"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/media?parent=28548"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/categories?post=28548"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/tags?post=28548"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}