Writing Data - Revision history

Nic at 03:04, 15 November 2016

2016-11-15T03:04:56Z

← Older revision		Revision as of 22:04, 14 November 2016
Line 58:		Line 58:
	A '''WriteData''' macro can also be used and called which behaves exactly as the command centre '''Write Data''' button.		A '''WriteData''' macro can also be used and called which behaves exactly as the command centre '''Write Data''' button.

	Lastly, the '''Write Data''' macro accepts 3 parameters being a'''import table name''', a '''data warehouse name''' and a '''data file name'''. All three parameters can be used independently and allows you to control/refine how the data gets written into MYOB.		Lastly, the '''Write Data''' macro accepts 3 parameters being an '''import table name''', a '''data warehouse name''' and a '''data file name'''. All three parameters can be used independently and allows you to control/refine how the data gets written into MYOB.

	== Related Topics ==		== Related Topics ==

	* [[Get Data]]		* [[Get Data]]

Nic at 00:18, 15 November 2016

2016-11-15T00:18:10Z

← Older revision		Revision as of 19:18, 14 November 2016
Line 58:		Line 58:
	A '''WriteData''' macro can also be used and called which behaves exactly as the command centre '''Write Data''' button.		A '''WriteData''' macro can also be used and called which behaves exactly as the command centre '''Write Data''' button.

	Lastly, the '''Write Data''' macro accepts 3 parameters being a'''import table name''', a '''data warehouse name''' and a '''data file name'''.		Lastly, the '''Write Data''' macro accepts 3 parameters being a'''import table name''', a '''data warehouse name''' and a '''data file name'''. All three parameters can be used independently and allows you to control/refine how the data gets written into MYOB.

			== Related Topics ==

			* [[Get Data]]

Nic at 23:17, 14 November 2016

2016-11-14T23:17:25Z

← Older revision		Revision as of 18:17, 14 November 2016
Line 49:		Line 49:

	All other fields in an import table are used as data field.		All other fields in an import table are used as data field.

			== Writing Data ==

			ODBClink provides multiple means to write data back into your accounting package.

			The command centre includes a '''Write Data''' button. Using this button, ODBClink will iterate through each data warehouse, data file and import table and record the data available.

			A '''WriteData''' macro can also be used and called which behaves exactly as the command centre '''Write Data''' button.

			Lastly, the '''Write Data''' macro accepts 3 parameters being a'''import table name''', a '''data warehouse name''' and a '''data file name'''.

Nic at 23:12, 14 November 2016

2016-11-14T23:12:43Z

← Older revision		Revision as of 18:12, 14 November 2016
Line 33:		Line 33:

	Each import table include specialised fields to provide result information. These fields do depend on the accounting package you are integrating with.		Each import table include specialised fields to provide result information. These fields do depend on the accounting package you are integrating with.

			These fields should be left blank.

			ODBClink will update these fields with information when writing data back to your accounting package.

	* '''RecordedUID''' is used for MYOB AccountRight Live and provides the '''UID''' of the transaction or data recorded. For endpoints that do not have a UID, the field will either contain the words '''Imported''' or '''Not Imported'''.		* '''RecordedUID''' is used for MYOB AccountRight Live and provides the '''UID''' of the transaction or data recorded. For endpoints that do not have a UID, the field will either contain the words '''Imported''' or '''Not Imported'''.

Nic at 23:11, 14 November 2016

2016-11-14T23:11:49Z

← Older revision		Revision as of 18:11, 14 November 2016
Line 11:		Line 11:
	Specialised import tables have been designed in ODBClink to allow you to import data back into your accounting package. These tables are "prefixed" with specialised names (e.g. MYOXIMPORT_ for MYOB AccountRight Live). For a complete list of the import tables, see [[Import Tables]].		Specialised import tables have been designed in ODBClink to allow you to import data back into your accounting package. These tables are "prefixed" with specialised names (e.g. MYOXIMPORT_ for MYOB AccountRight Live). For a complete list of the import tables, see [[Import Tables]].

	To configure ODBClink to write data, you will need to [[~~Edit Data Warehouse~~\|Edit your data warehouse]] and include the appropriate import tables.		To configure ODBClink to write data, you will need to [[Editing a data warehouse\|Edit your data warehouse]] and include the appropriate import tables.

	== Adding records to the write data table ==		== Adding records to the write data table ==

Nic at 23:11, 14 November 2016

2016-11-14T23:11:14Z

← Older revision		Revision as of 18:11, 14 November 2016
Line 11:		Line 11:
	Specialised import tables have been designed in ODBClink to allow you to import data back into your accounting package. These tables are "prefixed" with specialised names (e.g. MYOXIMPORT_ for MYOB AccountRight Live). For a complete list of the import tables, see [[Import Tables]].		Specialised import tables have been designed in ODBClink to allow you to import data back into your accounting package. These tables are "prefixed" with specialised names (e.g. MYOXIMPORT_ for MYOB AccountRight Live). For a complete list of the import tables, see [[Import Tables]].

	To configure ODBClink to write data, you will need to [[Edit your data warehouse~~\|Edit Data Warehouse~~]] and include the appropriate import tables.		To configure ODBClink to write data, you will need to [[Edit Data Warehouse\|Edit your data warehouse]] and include the appropriate import tables.

	== Adding records to the write data table ==		== Adding records to the write data table ==

Nic at 23:10, 14 November 2016

2016-11-14T23:10:53Z

← Older revision		Revision as of 18:10, 14 November 2016
Line 36:		Line 36:
	* '''RecordedUID''' is used for MYOB AccountRight Live and provides the '''UID''' of the transaction or data recorded. For endpoints that do not have a UID, the field will either contain the words '''Imported''' or '''Not Imported'''.		* '''RecordedUID''' is used for MYOB AccountRight Live and provides the '''UID''' of the transaction or data recorded. For endpoints that do not have a UID, the field will either contain the words '''Imported''' or '''Not Imported'''.

	* '''RecordedRowVersion''' is used for MYOB AccountRight Live and provides the '''RowVersion''' of the transaction or data recorded. For endpoints that do not have a RowVersion, the field will either contain the words ''Imported''' or '''Not Imported'''.		* '''RecordedRowVersion''' is used for MYOB AccountRight Live and provides the '''RowVersion''' of the transaction or data recorded. For endpoints that do not have a RowVersion, the field will either contain the words '''Imported''' or '''Not Imported'''.

	* '''RecordedDate''' is used for MYOB AccountRight Live and provides the date when the transaction was recorded. If the import process failed, it will be set to NULL. This fields is also used a control field. ODBClink will only attempt to import records which have a RecordedDate of NULL.		* '''RecordedDate''' is used for MYOB AccountRight Live and provides the date when the transaction was recorded. If the import process failed, it will be set to NULL. This fields is also used a control field. ODBClink will only attempt to import records which have a RecordedDate of NULL.

Nic at 23:10, 14 November 2016

2016-11-14T23:10:38Z

← Older revision		Revision as of 18:10, 14 November 2016
Line 34:		Line 34:
	Each import table include specialised fields to provide result information. These fields do depend on the accounting package you are integrating with.		Each import table include specialised fields to provide result information. These fields do depend on the accounting package you are integrating with.

	* '''RecordedUID''' is used for MYOB AccountRight Live and provides the '''UID''' of the transaction or data recorded. For endpoints that do not have a UID, the field will either contain the words ''Imported''' or '''Not Imported'''.		* '''RecordedUID''' is used for MYOB AccountRight Live and provides the '''UID''' of the transaction or data recorded. For endpoints that do not have a UID, the field will either contain the words '''Imported''' or '''Not Imported'''.

	* '''RecordedRowVersion''' is used for MYOB AccountRight Live and provides the '''RowVersion''' of the transaction or data recorded. For endpoints that do not have a RowVersion, the field will either contain the words ''Imported''' or '''Not Imported'''.		* '''RecordedRowVersion''' is used for MYOB AccountRight Live and provides the '''RowVersion''' of the transaction or data recorded. For endpoints that do not have a RowVersion, the field will either contain the words ''Imported''' or '''Not Imported'''.

Nic at 23:09, 14 November 2016

2016-11-14T23:09:24Z

← Older revision		Revision as of 18:09, 14 November 2016
Line 31:		Line 31:

	=== Fields used to return result information ===		=== Fields used to return result information ===

			Each import table include specialised fields to provide result information. These fields do depend on the accounting package you are integrating with.

			* '''RecordedUID''' is used for MYOB AccountRight Live and provides the '''UID''' of the transaction or data recorded. For endpoints that do not have a UID, the field will either contain the words ''Imported''' or '''Not Imported'''.

			* '''RecordedRowVersion''' is used for MYOB AccountRight Live and provides the '''RowVersion''' of the transaction or data recorded. For endpoints that do not have a RowVersion, the field will either contain the words ''Imported''' or '''Not Imported'''.

			* '''RecordedDate''' is used for MYOB AccountRight Live and provides the date when the transaction was recorded. If the import process failed, it will be set to NULL. This fields is also used a control field. ODBClink will only attempt to import records which have a RecordedDate of NULL.

			* '''RecordedResult''' is a text field used for MYOB AccountRight Live and provides the descriptive result returned by the import process. If the import was successful, it will set to '''Success'''. Any other value is an error and provides the description of the error.

			=== Fields used as data ===

			All other fields in an import table are used as data field.

Nic: Created page with "== Overview == ODBClink allows you to write data into your accounting package. '''Note that this feature is only available in ODBClink Pro Edition'''. ODBClink provides a ..."

2016-11-14T23:03:08Z

Created page with "== Overview == ODBClink allows you to write data into your accounting package. '''Note that this feature is only available in ODBClink Pro Edition'''. ODBClink provides a ..."

New page

== Overview ==

ODBClink allows you to write data into your accounting package.

'''Note that this feature is only available in ODBClink Pro Edition'''.

ODBClink provides a two-stage import process. First, you need to insert records into specialised import tables. Secondly, you can click the '''Write Data''' button from the command centre or use the '''WriteData''' macro to import all data back into your accounting package. Additional fields are included in the import tables to provide feedback information.

== Configuring ODBClink to write data ==

Specialised import tables have been designed in ODBClink to allow you to import data back into your accounting package. These tables are "prefixed" with specialised names (e.g. MYOXIMPORT_ for MYOB AccountRight Live). For a complete list of the import tables, see [[Import Tables]].

To configure ODBClink to write data, you will need to [[Edit your data warehouse|Edit Data Warehouse]] and include the appropriate import tables.

== Adding records to the write data table ==

Once the import tables have been included, you will need to insert records into the import table. The fields of the import table are broken into three groups:
* Fields used to control the import process;
* Fields used to return result information;
* Fields used to provide data.

=== Fields used to control the import process ===

Each import table include three fields used to control the import process.

* '''CompanyRecordID''' is an optional field which allows you to control into which data file the record will be recorded. This fields is only required in a multi-data file environment. It can be left blank in a single-data file environment.

* '''InternalID''' is an optional field which allows you to control how the transaction are group. For instance, if multiple lines of an invoice relate to each other. It also allows you to provide a '''key''' to your own data so you can integrate your system's identifier with that of your accounting package. If left blank, the system will group lines based on a specific rules documented in the relevant import table.

* '''InternalLineIndex''' is an optional field which allows you to control the order of the lines within a transaction.

=== Fields used to return result information ===