You can automate this process by setting up a scheduled task in doc-link Event Manager.
You can configure doc-link to use a custom table, but you must use SQL to first create the custom table in the doc-link database. Once the table is created you can configure cache tables through this screen.
Note: if you have installed the distribution stamp Smart Form all the required cache tables and lookups have been pre-configured and you just need to apply user filtering if you so desire.
Name – Allows you to name the cache table.
Data Source – This is the source to use when updating information in this table. The default "doc-link" data source is created at installation when the Distribution Stamp is installed and should be used if the custom tables reside in the doclink2 database. If you are accessing cached tables in another database you will need to create a data source to this external database.
Cache Table Name – This is the name of the cache table as it appears in the doclink2 database.
Update SQL – This section contains the SQL query or name of the stored procedure to be used to refresh the cache table. Parameters of the procedure can also be included here. (eg - <@Reload = 1 /> can be used to drop all data in a table before refreshing them)
Execute as Stored Procedure – This is an option given to choose whether or not the SQL above should be executed as a stored procedure or not.
The Update Now button is used to manually execute the update query with changes to the source table. For example if new GL Account Codes are created in your accounting application, the cache tables will not show this new data until the GLAccounts table has been updated.
|
You can automate this process by setting up a scheduled task in doc-link Event Manager. |
If successful, the update will prompt with a list of items for each cache table the linking stored procedures returned.
Getting Data from Accounting Package
