Home » Categories » Solutions by Business Process » E-Business » XML |
XML Transaction Definition |
Article Number: 1789 | Rating: Unrated | Last Updated: Thu, Jun 22, 2023 at 10:19 PM
|
Datafile Software XML Transaction Definition XML transactions, whether simple export or import options, or application transaction options, are driven by definitions held in a single folder. This folder generally lives in the root Datafile folder, and its location is defined via the General Configuration option. Up to 99 XML transactions can be defined, and the definitions for each transaction are held in sub-folders within the XML folder, named 0001 for the first XML transaction, 0002 for the next XML, and so on. Within each of these folders are two active files, one of which is a file called XML.INI holding configuration data for the transaction concerned, and the other a file called XML.XML, which is the XML template for the transaction. In fact the XML template can reside elsewhere in the system, but there is a benefit to keeping it within its transactional folder. If you look in these folders, you may also see other files, such as XML.~INI, and XML.~XML; these are backup copies created by the definition process when you make any changes. In fact these backup copies are left in place should you delete an XML option, which allows you to recover if you deleted the option by accident. The XML.INI file is entirely managed by the XML definition process, and should not normally be changed except via that process. The long-term objective is for the XML.XML file also to be edited via the definition process. At present, though, you’ll need to use a word processor such as Microsoft’s NotePad or WordPad programs if you wish to change templates. In the case of the single database XML options, the definition process creates the XML template according to some simple rules. You may still wish to edit it; for example, if you wish to change XML file element names or add extra processing facilities. In the case of the XML application transactions, you’ll need to create a template outside the Datafile definition process. The notes below explain the two parts to the definition process: first the Datafile screens that amend the XML configuration; and then how to create the working template. |
Attachments
![]() There are no attachments for this article.
|
save
Viewed 1359 times since Mon, Jul 9, 2012
XML Error Files
Viewed 1425 times since Mon, Jul 9, 2012
Change Forward Order Status
Viewed 1750 times since Tue, Jul 3, 2012
Sales Ledger Accounts (SLA)
Viewed 3647 times since Tue, Jul 10, 2012
Order Responses
Viewed 1394 times since Mon, Jul 9, 2012
Sales Order Headers (SOH)
Viewed 2454 times since Tue, Jul 10, 2012
copy
Viewed 1397 times since Mon, Jul 9, 2012
Typical XML Purchase Order Cycle
Viewed 1377 times since Mon, Jul 9, 2012
Purchase Order Header (POH)
Viewed 3544 times since Tue, Jul 10, 2012
Comments
Viewed 1465 times since Mon, Jul 9, 2012
|