Support & frequently asked questions

Quote line variables does not, as far as I can tell, contain a unit price after discount. A customer (online) want the following on a quote line: Unit number, unit name, quantity, unit list price, unit price after discount, and a sum total (Quantity * price after discount. In working with merged fields in Word , i.e: = { MERGEFIELD "line/unitListPrice" } * (1-{ MERGEFIELD "line/discountPercent" }/100) \# "#,##0.00" and variations over that, I am getting a syntax error after a Crtl+F9, I am told by Bing that: W ord formula fields work with real Word merge fields , while your document appears to use a separate quote-template merge engine, so mixing MERGEFIELD with «line/... » placeholders is probably what is causing the syntax error. Any suggestions as to how this can be solved ?    

Hi Samuel, very weird syntax that it does not include the '.', but indeed it works with , only not when using it in a url of a custom object record in the right click context menu, then it uses the value from the last record you actually 'opened', instead of the row that is active, propably it uses the record that is in your currents.  How supported is this? since this is not documented anywhere (so far i can find)

Hi Bas, Our tickets in CS are not only for our service & support but also Billing monthly sent to our Customer. Closing a ticket requires filling in several mandatory fields shown in bold in Tieckt Header; otherwise, it’s IDs will display in a red row to user, this ensures that no tickets being skipped to bill to our customer.   The associated lists of cost center in extra table and project are two of them. We have thousands of projects; For enabling users to quickly and easily find and select his correct project in TicketEdit, we need a filtered project-list with status neither closed nor cancelled, sorted by project start date, includes specific display fields. The Solution in Screen with Simple Value works exactly on our demand. In contrast, triggered dialogs require a step more   to ask user in dialog to confirm the Project Status -- The process lacks conciseness. Similar to the linked cost center list, which includes a "Disable" field in extra table, in TicketEdit should display only active cost centers, the Triggered dialogs require the user to confirm the display of active cost centers via an additional prompt -- an unnecessary step for the user.  In short, triggered dialogs is general good but not ideal for our this application. The ideal approach would be to implement the necessary conditions beforehand -- like simple value in Screen or conditions in Archive of ScreenDesigner.