<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/da/xch/daxch0135m000" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Export Triggers (daxch0135m000)</Title>
	</Header>
	<HelpTopic xml:lang="en"><AimSection><Paragraph class="Default">
                                 Use this session to create and maintain export triggers.</Paragraph>
		</AimSection>
		<GeneralSection><Paragraph class="Default">These are triggers that will be executed automatically when an export is run for an <Link href="/baanerp/da/glossary/glossary#000003" role="glossary">exchange scheme</Link>. To create an export trigger, you must link an existing trigger to a <Link href="/baanerp/da/glossary/glossary#000032" role="glossary">table relation</Link> (Export) in an Exchange scheme.</Paragraph>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<List><ListItem>When you edit a row, the table and ASCII file from the Table Relation (Export) are displayed.</ListItem>
					<ListItem>A change becomes active the next time an export is done (an already running export process is not changed).</ListItem>
					<ListItem>It is not needed to regenerate the export program.</ListItem>
					<ListItem>An export trigger is deleted automatically when you delete the corresponding export batch line.</ListItem>
				</List>
			</Note>
		</GeneralSection>
		<RelatedTopics><SectionTitle>
                                 Related topics
                              </SectionTitle>
			<RelTopic><Link href="/baanerp/da/onlinemanual/000300" role="manual">Triggering</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/da/onlinemanual/000001" role="manual">Introduction to the Exchange module</Link>
			</RelTopic>
		</RelatedTopics>
	</HelpTopic>
	<Fields><FieldHelp ID="daxch035.cxch"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Exchange Scheme</Title>
			</Header>
			<FuncDesc>The <Link href="/baanerp/da/glossary/glossary#000003" role="glossary">exchange scheme</Link> that contains the table relation to which the export trigger is linked.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="daxch035.cbat"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Batch</Title>
			</Header>
			<FuncDesc>The <Link href="/baanerp/da/glossary/glossary#000002" role="glossary">batch</Link> that contains the table relation to which the export trigger is linked.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="daxch035.batl"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Table Rel.</Title>
			</Header>
			<FuncDesc>The <Link href="/baanerp/da/glossary/glossary#000032" role="glossary">table relation</Link> (export batch line) to which the export trigger is linked.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="daxch035.trow"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Trigger for Each Row</Title>
			</Header>
			<FuncDesc>This field is optional. The trigger specified in this field will be started for each row exported by the exchange scheme: an event will be created for each row being processed by the export batch line and the trigger is invoked for that event.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="daxch035.cfil"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Create ASCII File</Title>
			</Header>
			<FuncDesc>Use this check box to select whether the Exchange export process must write records to the ASCII file that is defined in the Table Relation (Export). If you select this check box, the export process writes each exported record to the ASCII file and also invokes the specified trigger(s). If you clear this check box, the export process only invokes the trigger(s).</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="daxch035.tend"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Trigger for Batch Line End</Title>
			</Header>
			<FuncDesc>This field is optional. The trigger specified in this field will be started after the exchange scheme has processed all rows for the export batch line.</FuncDesc>
		</FieldHelp>
	</Fields>
</Session>
