moneyworks - MoneyWorks command line modes
moneyworks [options] [file-or-url]
On Mac OS X, the short form (moneyworks) is a symbolic link to the actual executable (/Applications/MoneyWorks\ Gold.app/Contents/MacOS/MoneyWorks\ Gold). On Windows, a separate command line client, moneyworks.exe is installed in C:\Program Files\ MoneyWorks Datacentre\. See notes for caveats on symbolic link usage.
On Mac OS X, MoneyWorks Gold can be executed from the command line in either normal GUI mode with an optional file or URL parameter, or as a non-GUI command line tool. In the latter case, it is useful for automated access to local or remote MoneyWorks Gold databases.
On Windows, moneyworks.exe is a command-line-only tool (vs MoneyWorks Gold.exe which is GUI-only due to Windows subsystem limitations).
If executed with the -i switch, MoneyWorks will enter interactive mode, reading commands from stdin, and writing results to stdout. Any errors will be written to stderr. Diagnostics may also be written to stderr, and will precede the error message. The quit command will end the interactive session, as will (on OS X) closing stdin by sending an EOT (ctrl-D). Any open network connection or document will be cleanly closed first.
If executed with the -e command line switch and a supplied command, the command will be executed and the tool will exit after completion, writing any output to stdout. Multiple -e command terms may be passed. They will be executed from left to right. The command in the -e term should be quoted to protect it from shell expansion, especially if it contains spaces. A URL or file may be supplied as the final parameter. MoneyWorks will open the file/url before executing the commands. Errors are reported as for the -i case.
-h and -x can be used with -i or -e (if neither of these is specified, -i is implied). These output format modes are intended to make the interactive output more reliably machine-parsable.
The -f option is useful only on managed Citrix desktops, where you can control the launch environment of the app to restrict users to their own subfolder. It should be used in conjunction with Datacentre server login for server-side enforcement of folder views. It is helpful in that it removes the requirement for the user to manually log in to the server.
Long form options are only available in the Mac version.
Run in interactive mode, reading commands from stdin, writing output to stdout and errors to stderr, until command is quit. In verbose mode, success notifications may be appear on stdout for some commands that do not otherwise have output (e.g. "Connect Succeeded")
Execute the supplied command and exit.
Output results as xml to stdout (use with -i or -e).
There is always an xml header line; root tag is <commandstream>; each command (including any implicit open) outputs a <command> result tag; there is always a <status> tag with 'OK' or 'Fail'; If status is OK, there will be a <result> tag (may be empty). If status is Fail, there will be an <error> tag and may be a <diagnostic> tag with additional information. Do not rely on the contents of the diagnostic tag. Contents of the result tag are utf-8 and entity-encoded and may be CDATA if it can't be entity-encoded. Stderr may be ignored, although it may contain additional error messages (such as import error logging).
Note: the <commandstream> wrapper is new in version 6, as is the result from the implicit open.
Output results in http-header style to stdout (use with -i or -e).
Each header line consists of the header name (which does not contain spaces), a colon, a space, a value which may contain spaces, and a return+newline. The final header is followed by an additional return+newline (i.e. a blank line). There is always a 'Status' header with value 'OK' or 'Fail'; If Status is Fail there will be an 'Error' header and may be a Diagnostic header (as for xml). If Status is OK and there is output following the headers, there will be a Content-Length header whose value is the number of bytes of content. Stderr may be ignored, although it may contain additional error messages (such as import error logging).
Quiet. No initial greeting or success notifications on stdout in -i mode (-x and -h imply -q). Also no chatter on stderr (log to system.log and MoneyWorks_Gold.log only).
Verbose mode. Provide more status feedback on stdout in -i mode.
Download plugins from server (if they need refreshing) when logging in.
Open document read-only.
Use registration number. If you are executing as user www or similar and wish to connect to a Gold server or open a local file, MoneyWorks does not have access to a preferences file to obtain a registration number; in this case you would need to supply one on the command line. Usually, you don't need a registration number to connect to a DC server, although you might like to connect using a full Gold serial to avoid any possibility of all concurrent connections being exhausted.
When opening a password-protected local file on command line, use the given username and password.
Come to front on launch (GUI mode)
Don't allow use of manual connections (Windows GUI mode)
Connect only to named subfolder on Datacentre (Windows)
On Windows, the older, Windows-style switches are also supported (although use of this style of switch is deprecated):
The commands you can issue are analogous to the Applescript and COM commands.
Commands are given in the form
The parameter delimiter can be pretty much any character you like except for whitespace or =.
Returns the MoneyWorks Gold version
$ moneyworks -e version 6.1 $ moneyworks -xe version <?xml version="1.0"?> <commandstream> <command name="version"> <status>OK</status> <result>6.1</result> </command> </commandstream>
Evaluates the expression and returns the result. You can also abbreviate this to =expression.
$ moneyworks -e "evaluate expr='DateToText(Today(), -7)'" 20111216000000
Open the file at the given path or connect to the url (which should follow the moneyworks:// scheme). The MoneyWorks URL scheme is documented here http://www.cognito.co.nz/support/?developer&art=url
If connecting to a URL of a document that requires login, you may include the login information in the URL, as per the URL scheme. However it is recommended to use the separate user, pass, docuser, and docpass parameters. You can also pass login="user:pass" but this is deprecated since it does not allow user names containing colons (likewise this problem applies to passing credentials in the url).
If logging in to a Gold server, use user and pass only. If logging in to a Datacentre server, use docuser and docpass for the document login and, if required, use user and pass for the Datacentre subfolder and password.
Close the current file or connection, if any
Exits interactive mode
Import data. If plugins are available, the map name can be given, otherwise a full path should be given. Likewise if importing from a file, the full path to the file must be given.
There is no metacharacter expansion in the data parameter, so you can't use \t, \n etc.. If you have multiple lines to import, write your data to a temp file and use the file parameter.
Output is a report of number of records created and updated (except for User, Contact and Build files, which will always report zero).
Additional arguments may be:
filename='Account | User | Build | Memo' Import into fixed format file (no import map)
update='true' seqnum='num' [discard='true'] Transactions only. Recall the identified invoice. Optionally discard imported invoice (i.e. just delete or cancel invoice being recalled)
return_seq='true' Output will be sequence number of newly imported record
post='true' Transactions only. Post the imported transactions
The data parameter may contain xml or the file parameter may identify an xml file (in this case, the map parameter should be omitted or be "xml"). The xml should be marked up in the same manner as the xml export format (see below). fields or records with the attribute "system" will be ignored.
Post the transaction identified by sequence number
Export data from the given file ("table") in MoneyWorks. If there is no search parameter, you will get all records, otherwise only those matching the search expression.
Using "=" as the search expression will export a single "record" containing just the field names for the file. The table name may include a sort specifier (e.g. "Name.Code-"). To export with a particular format, use the format parameter. Everything in the format string is returned verbatim except for anything inside [...] which is treated as an expression which can reference the fields of the file being exported. Thus if you want tab-delimited, then put tabs between the expressions. You can use metacharacters \t \r \n \xHH (hex) or \\. e.g. "[Code],[Phone]\n"
If the output parameter is not supplied, the data is sent to stdout, otherwise a file is created using the full path supplied and the data is written there. If you supply an output parameter and no format parameter, you will get the format equivalent to a manual export, otherwise you get all fields. Using a format parameter is strongly recommended, since default export formats are subject to change.
As a special case, an output path of "tmp" will create a temp file for you and return the path of that file.
You can also export xml by specifying "xml" as the format. By default, the xml will be terse (also specifiable by "xml-terse" as format) in that any blank or zero fields will be omitted, as will system detail lines for transactions and system (no-importable) fields. To get all fields, specify "xml-verbose" as the format. In verbose format, system detail line records and non-importable fields will include a "system" attribute in their opening tag.
Executes the report and writes output to stdout or to the given output file. Since there is no plugins folder in command line mode, the full path to the report must be given. If outputting to stdout, the format is tab-delimited. If a path is given and the filename ends with ".html" then the output will be in HTML. Otherwise you can explicitly specify the format.
All parameters are inserted into the name table and are available to the report. Thus you can pass values for custom controls defined for a report.
If format is pdf, html, or xml, and output not supplied or is the magic name "tmp", then MoneyWorks will generate a temp file for the output and tell you the path. It is up to you to delete this temp file. If the -x option has been specified, then the tag for the temp file path is <output> and there will also be a <mimetype> tag.
Renders the form to a pdf file. For form types other than .rept a search expression must be provided to select the record(s) to use. If multiple records are selected, all output still goes to the same PDF. Output path is optional--if it is not supplied, a file will be created in the temp directory. The return value on stdout is the path to the generated pdf. The only supported format at present is "pdf". For forms that use variables supplied by the form printing dialog (such as Message, Print_Copy etc) you may provide values for those variables by passing them as parameters e.g. Message="Hello" Print_Copy="0" Include_Remit="0" for typical invoice forms; Stmt_Date="1/1/2010" for statements.
Runs file-system and integrity diagnostics for the currently-open file
List plugin files in the custom or standard plugins folder. Output is xml.
Downloads a transaction or product image to a temporary file. Output is the file path.
Uploads a transaction or product image.
Uploads the local custom plugins folder (or a single matching file therein) to the server.
-x and -h modes return a 'status' tag/header indicating success or failure. In the default mode (without -x or -h) errors are written to stderr. Typically one or more errors tagged with "[ERROR]" followed by a failure notice tagged with "[FAIL]". In -x or -h mode, the final [ERROR] is included in the output to stdout tagged as 'diagnostic', and the failure notice tagged as 'error'.
Note that connecting to the server is relatively expensive. This will of course be much longer if the server has to open the document from scratch. In command line mode, no plugins are downloaded from the server unless you specify the -p switch.
In most circumstances, a short-lived connection to the server with command(s) passed using the -e option will be the easiest mode of use. This is because the calling code can read all of the output to the end of file. In interactive mode you need to know how many bytes of output to read before sending the next command (hence the -x and -h options). If you need a number of results that require some complex processing, consider writing a custom report and executing that using doreport, thus obtaining all the results at once. For highest performance for many requests, you would need to stay connected in -i mode.
If using the -i option, avoid keeping connections open indefinitely, Datacentre should be allowed to close documents overnight for housekeeping purposes. In fact, if you do attempt to stay connected for more than 5 minutes without doing anything, the Datacentre server will treat you as a stale connection and disconnect you. You would need to be pinging the server with some kind of database request, such as an export, to keep the connection alive.
(note that these examples are for Mac OS X)
Connect to a DC document and get the output from the given report for the period range.
moneyworks -e "doreport report='/Users/rowan/My Balance Sheet' \ from='20100201' to='20100331'" \ "moneyworks://zaphod.local.:6699?doc=Acme.mwd6"
Interactive mode (verbose, unformatted output)
moneyworks -iv MoneyWorks Gold 6.0 interactive mode. Type 'quit' or ctrl-D to exit. open file="/Users/rowan/Documents/Acme Widgets.mwd5" Open succeeded =name Acme Widgets Ltd close Close succeeded quit
Piping commands in from a file (such as multiple exports)
moneyworks -i < ~/mycommands > ~/output.txt ~/Acme\ Widgets.mwd5
Launching in GUI mode from the symlink at /usr/bin/moneyworks will actually relaunch using the full path. The relaunch via
system(3) will quote your arguments using double quotes. Arguments that include double quotes will break.
MoneyWorks command line mode first appeared in MoneyWorks Gold 5.0.8
Cognito Software Ltd <email@example.com>
Copyright 1992-2012 Cognito Software Ltd