{"id":5201,"date":"2014-05-26T14:48:42","date_gmt":"2014-05-26T14:48:42","guid":{"rendered":"http:\/\/www.greytrix.com\/blogs\/sagex3\/?p=5201"},"modified":"2018-11-19T07:12:56","modified_gmt":"2018-11-19T07:12:56","slug":"how-to-conditionally-restrict-the-import-update","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sagex3\/2014\/05\/26\/how-to-conditionally-restrict-the-import-update\/","title":{"rendered":"How to conditionally restrict the Import update\u2026!"},"content":{"rendered":"

Many a times we use Import\/Export feature to create or update the transaction in Sage ERP X3. As the Import\/Export is performed on the standard code it is too difficult to control the creation or modification of records. In one of our customization’s, we were using the Work Order Operation import function, but we had found one drawback during the process, that it also updates closed<\/b> operations.<\/p>\n

GUMU™ for Sage CRM \u2013 Sage Enterprise Management Integration<\/a>\u00a0~ Real-time, Bi-directional<\/p>\n

After some R & D we have a way to restrict the import function. The AP_IMPORT<\/b> action is called while importing the file. In this action we can write our logic to control the transaction updation.<\/p>\n

E.g.<\/b> To overcome on the above problem we have written the below logic in AP_IMPORT<\/b> action. We just opened the same (Work Order operation) table with another abbreviation and checked the operation status. If the operation status is closed we would just reassign the original values to the main table. Now whenever we import the Work Order operation and if any of operation is closed it will just reassign the previous values and will not update the records.<\/p>\n

Kindly refer the below snippet of code for better clarification.<\/p>\n

\"Import\"<\/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

<\/p>\n

<\/p>\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

Many a times we use Import\/Export feature to create or update the transaction in Sage ERP X3. As the Import\/Export is performed on the standard code it is too difficult to control the creation or modification of records. In one of our customization’s, we were using the Work Order Operation import function, but we had\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":[1],"tags":[132,1048],"class_list":["post-5201","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-ap-import","tag-import-template"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/5201","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=5201"}],"version-history":[{"count":2,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/5201\/revisions"}],"predecessor-version":[{"id":16310,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/5201\/revisions\/16310"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/media?parent=5201"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/categories?post=5201"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/tags?post=5201"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}