[EasyDNNnews:IfExists:Event]
[EasyDNNnews:IfExists:EventRegistration][EasyDNNnews:EventRegistration:RegisterButton][EasyDNNnews:EndIf:EventRegistration]
[EasyDNNnews:IfExists:Payment]
[EasyDNNnews:Price][EasyDNNnews:EndIf:Payment]
[EasyDNNnewsLocalizedText:Eventdate]:
[EasyDNNnews:EventDate] [EasyDNNnewsLocalizedText:ExportEvent]
[EasyDNNnews:IfExists:EventLocation]
[EasyDNNnewsLocalizedText:EventLocation]: [EasyDNNnews:EventLocation]
[EasyDNNnews:EndIf:EventLocation]
[EasyDNNnews:IfExists:EventRegistration]
- [EasyDNNnewsLocalizedText:NumberOfAttendants]: [EasyDNNnews:EventRegistration:NumberOfAttendants]
- [EasyDNNnewsLocalizedText:MaxNumberOfTickets]: [EasyDNNnews:EventRegistration:MaxNumberOfTickets]
- [EasyDNNnewsLocalizedText:NotUsedTickets]: [EasyDNNnews:EventRegistration:NotUsedTickets]
[EasyDNNnews:IfExists:Payment]- [EasyDNNnewsLocalizedText:Price]: [EasyDNNnews:Price]
[EasyDNNnews:EndIf:Payment]
[EasyDNNnews:EventRegistration:InfoMessage]
[EasyDNNnews:EndIf:EventRegistration]
[EasyDNNnews:IfExists:EventSignUp]
[EasyDNNnewsLocalizedText:AreYouGoing]
[EasyDNNnews:SignUpActionBar]
[EasyDNNnews:EndIf:EventSignUp]
Infor LN & Baan Tips & Tricks for Technology: Using audit files in the Exchange module
The audit server logs all database actions that change the contents of a table in so-called audit files. The Exchange module can use these audit files, which are useful in a multisite environment because the databases on all sites must have identical data. These audit files can also be used in data conversions.
Only the updates in a specific period are exchanged, which leads to an improvement in performance. Specify this period in the Export Data (Non-Regular) (daxch0233m000) and Export Data (on a Regular Basis) (daxch0234m000) sessions. Changes such as insert, update, and delete are processed and written into the ASCII files. Actions such as drop, clear, and create tables are ignored.
Audit control data is added to the resulting ASCII file. This data consists of a batchline ID, transaction ID, sequence ID, and an indicator. The control data is added at the beginning of each line and is formatted like other data fields such as the enclosing and separator characters.
An update writes two lines to the ASCII file. One line contains the key fields and old values of the updated fields. The other line contains the new values of the key fields and updated fields, even if a key field does not change.
The batchline ID is used for recognition when processing the ASCII files. The transaction and sequence IDs are used to ensure that the transactions are replayed in the same order as on the exporting site. The indicator defines the type of action that is executed on the table. Use the letter I to insert; use the letter D to delete; use the letter U to update with old values; and use the letter N to update with new values.