<parameterdatatype="string"min_n_values="1"max_n_values="1"name="BuyerIdSqlExpression"default="cust.company_id"description="SQL expression to calculate the UBL BuyerID field. This expression is inserted into a SQL query in /intranet-ubl/tcl/intranet-ubl-procs.tcl in order to determine the buyer identification. The default value is "cust.company_id", representing the im_company.company_id field of the customer "cust". Assuming a custom DynField im_company.nav_company_nr representing the company's Navision number, a suitable expression could be "coalesce(cust.nav_company_nr, cust.company_id::varchar)" in order to return the Navision number if available, or the ]po[ company_id otherwise."/>
<parameterdatatype="string"min_n_values="1"max_n_values="1"name="SellerSqlExpression"default="prov.company_id"description="Please see BuyerIdSqlExpression for description, replacing "cust" and "Customer" with "prov" and "Provider"."/>
<parameterdatatype="string"min_n_values="1"max_n_values="1"name="UblExportConverterProc"default="im_package_ubl_invoice2ubl"description="What procedure to use for exporting UBL documents? The reason for this parameter is that existing users might want to continue to use "bugy" exports in even if there are newer or better versions available. The reason is that the customer might have created a script on the other side that actually depends on these "bugs"..."/>
<parameterdatatype="string"min_n_values="1"max_n_values="1"name="UblExportPathUnix"default="/web/projop/filestorage/ubl"description="Path to the directory on where to write UBL documents for batch export."/>