{"id":20790,"date":"2020-09-29T11:56:17","date_gmt":"2020-09-29T11:56:17","guid":{"rendered":"http:\/\/www.greytrix.com\/blogs\/sagex3\/?p=20790"},"modified":"2020-09-29T12:40:57","modified_gmt":"2020-09-29T12:40:57","slug":"how-to-solve-formatting-issue-in-v12-using-break-after","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sagex3\/2020\/09\/29\/how-to-solve-formatting-issue-in-v12-using-break-after\/","title":{"rendered":"How to solve formatting issue in V12 using \u201cBreak After\u201d"},"content":{"rendered":"\n

In earlier version of Sage X3<\/a> (before V12), whenever there was any requirement from client to add custom fields on standard transaction\/master screen, developer has to select the position and block in which it will be displayed and has to place those fields by giving specific numbering to it. But most of the time, developer faced issues while displaying the fields in blocks even after assigning the correct sequence to the fields. To overcome this issue, Sage X3 V12 has given the feature of breaking the line so that fields will get displayed properly and as expected. This feature has been added in V12 as it was not there in previous versions of Sage X3.<\/p>\n\n\n\n

As the name implies, \u201cBreak After\u201d is applied on the field so that next fields gets placed on the next line within the block or any tab on the screen.<\/p>\n\n\n\n

New Stuff:<\/strong> Restriction on WO Close unless Quality Transaction is clear<\/a><\/p>\n\n\n\n

\"[Sales<\/a><\/center>\n
[Sales Invoice screen]<\/center><\/font>\n\n\n\n

In the above screenshot, we have added few custom fields in the Sales invoice screen under the Management tab of the Project block, as they are scattered and are not displaying in proper sequence. So we will be displaying the fields in proper format using the break feature given in Version 12 in Sage X3.<\/p>\n\n\n\n

For this, we will navigate into Development -> Script Dictionary -> Windows (OSIH) -> Screen (SIH1).<\/p>\n\n\n\n

\"[Screen<\/a><\/center>\n
[Screen dictionary for SIH1]<\/center><\/font>\n\n\n\n

As shown in the above screenshot, the \u201cBreak after\u201d column is present on the screen with the drop-down option as \u201cYes\u201d or \u201cNo\u201d in it. So for the BOE number, we will be selecting \u201cYes\u201d so that the GST number will be displaying on the next line. Also, we will select \u201cYes\u201d for Port Number so that Original invoice no and Original invoice date will be displaying in the next line. Further, save the changes and do Global validation of the window and also validate it from the Setup so that changes will be reflected on the Sales invoice screen.<\/p>\n\n\n\n

\"[Sales<\/a><\/center>\n
[Sales Invoice screen after modification]<\/center><\/font>\n\n\n\n

In the above screenshot, you can see the Sales invoice screen after the changes are done and the fields are now displaying properly on the screen. As you can see after applying the \u201cBreak after\u201d feature, fields in Project block are properly formatted in that section and are placed rightly on the screen. So this new feature has solved most of our formatting issues 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 earlier version of Sage X3 (before V12), whenever there was any requirement from client to add custom fields on standard transaction\/master screen, developer has to select the position and block in which it will be displayed and has to place those fields by giving specific numbering to it. But most of the time, developer\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":[13,8],"tags":[3102,1822,2538,3101,2349,2768],"class_list":["post-20790","post","type-post","status-publish","format-standard","hentry","category-integration","category-sage-erp-x3","tag-break-after","tag-sage-x3","tag-sales-invoice","tag-v12","tag-validate","tag-version"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/20790","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=20790"}],"version-history":[{"count":5,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/20790\/revisions"}],"predecessor-version":[{"id":20806,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/20790\/revisions\/20806"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/media?parent=20790"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/categories?post=20790"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/tags?post=20790"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}