{"id":5654,"date":"2014-09-23T08:23:16","date_gmt":"2014-09-23T08:23:16","guid":{"rendered":"http:\/\/www.greytrix.com\/blogs\/sagex3\/?p=5654"},"modified":"2018-11-19T10:32:31","modified_gmt":"2018-11-19T10:32:31","slug":"how-to-increase-sage-erp-x3-memory-for-a-particular-user","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sagex3\/2014\/09\/23\/how-to-increase-sage-erp-x3-memory-for-a-particular-user\/","title":{"rendered":"How to Increase Sage ERP X3 memory for a particular User?"},"content":{"rendered":"

You may come across a situation where you want to increase the memory in sage ERP X3 for a particular user in a particular process. That particular process may need a higher memory for a transaction to process. In Sage ERP X3, it can be done with help of the keyword \u201cmaxmem\u201d.<\/p>\n

MAXMEM indicates the amount of memory that Screens<\/strong> can use on the client side. So if you have screens with large number of lines, then you may need to set a larger MAXMEM.<\/p>\n

MAXMEM:<\/em><\/strong> It determines the maximum amount of memory that can be used by the application and modifies this parameter.<\/p>\n

Note:<\/strong> MAXMEM is set in kilobytes and read in bytes. So, you\u2019ll notice in the code supplied below that MAXMEM is set to 65536 (64 MB) but while reading, it must be divide by 1024 to get the same value in return. Do not set MAXMEM to bytes or else you will get an error.<\/p>\n

Refer below snippet for better understanding.<\/p>\n

\"Image-1\"<\/a><\/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>\n

Greytrix<\/a>\u00a0caters to a wide range of Sage Enterprise Management (Sage X3) offerings \u2013 a Sage Business Cloud Solution. Our\u00a0unique GUMU™ integrations include Sage Enterprise Management (Sage X3) for Sage CRM<\/a>,\u00a0Salesforce.com<\/a> and\u00a0Magento eCommerce<\/a>\u00a0along 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.\u00a0We also offer best-in-class\u00a0Sage X3 customization and development services<\/a>,\u00a0integrated 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>\u00a0and 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™ Sage Enterprise Management \u2013 Sage CRM integration also listed on Sage Marketplace<\/a>; GUMU™ 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\u00a0x3@greytrix.com<\/a>. We will be glad to assist you.<\/p>\n","protected":false},"excerpt":{"rendered":"

You may come across a situation where you want to increase the memory in sage ERP X3 for a particular user in a particular process. That particular process may need a higher memory for a transaction to process. In Sage ERP X3, it can be done with help of the keyword \u201cmaxmem\u201d. MAXMEM indicates the\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[1267,1268],"class_list":["post-5654","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-maxmem","tag-memory"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/5654","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=5654"}],"version-history":[{"count":1,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/5654\/revisions"}],"predecessor-version":[{"id":16390,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/5654\/revisions\/16390"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/media?parent=5654"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/categories?post=5654"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/tags?post=5654"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}