<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/da/onlinemanual/000011" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">To use multiline text in an audit procedure</Title>
		<Keyword ContextSensitive="No"><Level1>Exchange text</Level1>
		</Keyword>
		<Keyword ContextSensitive="No"><Level1>Audit procedure</Level1>
		</Keyword>
	</Header>
	<GeneralSection><Paragraph class="Default">Multiline text fields can be used in an exchange based on audit. They are used when new data is inserted or when existing data is updated. Multiline text fields are written during a data export or read during a data import.</Paragraph>
		<List><ListIntro>A multiline text is created in an <Link href="/baanerp/da/glossary/glossary#000001" role="glossary">ASCII file</Link> during a data export based on an <Link href="/baanerp/da/glossary/glossary#000008" role="glossary">audit procedure</Link> if:</ListIntro>
			<ListItem>A record with a text has been inserted .</ListItem>
			<ListItem>A new text is linked to an existing record .</ListItem>
			<ListItem>A text is deleted.</ListItem>
			<ListItem>A text is disconnected from a record.</ListItem>
		</List>
		<GeneralSection><SectionTitle>Limitations:</SectionTitle>
			<List><ListItem>In previous releases a multiline text was not created during a data export if only the contents were changed. In this release, if the contents of a text is changed by means of the text editor, this is logged in the audit trail as two actions: an unlink action (where the old text is unlinked from the row) and a link action (where the new text is linked to the row). This means that when importing based on audit, the old text will be unlinked and a new text will be created and linked to the row.</ListItem>
			</List>
		</GeneralSection>
		<ExampleSection><SectionTitle>
                                 Example
                              </SectionTitle>
			<Paragraph class="Default">If you change an order text, the order record is not changed and the text number in the record is unchanged. This means that the order is not logged in the audit files and exchange is not notified that the text has changed.</Paragraph>
			<List><ListItem>Text that is deleted between the moment it is created and the moment the export is run, is not read by the <GUIRef href="/baanerp/da/xch" role="module">Exchange</GUIRef> module. The text is therefore not exchanged.</ListItem>
			</List>
			<Paragraph class="Default">If a multiline text is deleted in the source database, the text number is set to zero and the following multiline text is written by the <GUIRef href="/baanerp/da/xch" role="module">Exchange</GUIRef> module during a data export:</Paragraph>
			<Formula space-and-orientation="indented-estimated"><Paragraph class="Default">
               {\{ nnnnnnnn0-
               }\}
</Paragraph>
			</Formula>
			<Paragraph class="Default">The dummy language 0 is for compatibility with previous versions. The minus sign (-) indicates that the text is disconnected from the record.</Paragraph>
			<Paragraph class="Default">The text number is set to zero in the target database if the update is imported. The contents of the text is not deleted.</Paragraph>
		</ExampleSection>
		<GeneralSection><SectionTitle>Compatibility problems with older Infor ERP versions</SectionTitle>
			<List><ListItem>If the target is BaanIV c or a later version and the source is an older version Infor ERP there are no major problems, but the same limitations of the older versions apply as far as text deletions are concerned.</ListItem>
				<ListItem>If the source is BaanIV c or a later version and the target is an older version of Infor ERP, an empty text field can be created instead of setting the text number at the target site to zero.</ListItem>
			</List>
		</GeneralSection>
	</GeneralSection>
</ManualTopic>
