Difference between revisions of "Writing Data"

850 bytes added ,  22:04, 14 November 2016
no edit summary
 
(3 intermediate revisions by the same user not shown)
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'''.
Line 45: 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 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 ==
* [[Get Data]]
1,344

edits