Sample export control file

In a Command Line Interface (CLI), FormSync uses an export control file to specify what elements of a configuration are to be exported as SQL or XML data.

This is an example of a control file used to export XML data using FormSync by means of a Command Line Interface (CLI) switch.

This file can be used to generate SQL or XML files. Scope type and scope name are attributes to the Objects node as well as global settings for referenced objects and expanding wild cards. The configuration element defines the source of forms and objects being processed.
Note: This is a sample file only and cannot be used "as is". 
<?xml version="1.0" encoding="utf-8"?>
<ExportInformation Version="010000">
	<Settings>
		<Type>XML</Type>
		<Configuration>CoreDevLocal</Configuration>
		<Path Clean="True">default/ExportTestXML</Path>
		<LockedBy>True</LockedBy>
	</Settings>
	<Objects Scope="Vendor">
		<Forms Licenses="True">
			<Form ExpandWildcard="True" ReferencedObjects="True">a13%</Form>
			<Form ExpandWildCard="True" Licenses="False">upgrade%</Form>
		</Forms>
		<Variables ExpandWildcard="True">
			<Variable>%deletetest%</Variable>
		</Variables>
		<Validators>
			<Validator ExpandWildcard="True">%deletetest%</Validator>
		</Validators>
		<Scripts>
			<Script>aaaaDeleteTest1</Script>
			<Script>aaaaDeleteTest2</Script>
		</Scripts>
		<Strings>
			<String ExpandWildcard="true">aaaaDeleteTest%</String>
			<String ExpandWildcard="True">aa%one</String>
			<String>%B</String>
		</Strings>
		<Menus ExpandWildcard="True">
			<Menu>aaaaDeleteTest%</Menu>
		</Menus>
		<PropertyClassExtensions>
			<PropertyClassExtension>aaaaDeleteTest1</PropertyClassExtension>
			<PropertyClassExtension>aaaaDeleteTest2</PropertyClassExtension>
		</PropertyClassExtensions>
		<ComponentClasses>
			<ComponentClass ExpandWildcard="True">%deletetest%</ComponentClass>
		</ComponentClasses>
		<Images ExpandWildcard="True">
			<Image>aaaaDeleteTest%</Image>
		</Images>
		<Themes/>
		<WebUserControls>
			<WebUserControl>UpgradeTest.dll</WebUserControl>
		</WebUserControls>
		<WebUserControlElements ExpandWildcard="True">
			<WebUserControlElement>myapps/controls/%</WebUserControlElement>
			<WebUserControlElement>myapps/images/%.png</WebUserControlElement>
		</WebUserControlElements>
	</Objects>
</ExportInformation>

The output path can be any of these:

  • An absolute path, if it starts with a drive letter followed by a colon
  • A path relative to the directory where formsync.exe resides
  • A path relative to the default directory.

    This option is used if the Path field starts with default/. That portion of the output path will be replaced with the default output folder normally used by FormSync, which is MyDocuments/Infor if it exists. Otherwise, it is MyDocuments.

Form files can also include the license information. For SQL, this generates a separate license file. For XML output, the license is included in the XML file for the form.

The ReferencedObjects attribute also includes any referenced objects for those objects that can reference other objects.

ExpandWildCard allows wild card SQL characters to be processed as wild cards. These include % and [], as well as others.

These attributes are inherited from parent nodes but can be specified at any level.

Related topics