Changes

Jump to: navigation, search

How Calculated Custom Fields Work

79 bytes added, 17:46, 24 June 2013
no edit summary
'''==[[Custom Field Type: Special – Calculated Value|Special - Calculated Value]]'''==
* Expressions entered into this field type are evaluated as '''[[JavaScript''' ]] functions.
* These functions are added to associated page and executed in the client [[Browser|browser]].
* You can enter any valid JavaScript construct into these expressions.
* The major limitation of this expression type is that it can only use values that are within the current page.
* The expression cannot be used to manipulate values stored on other [[tabs ]] or aggregate data from related [[Entity|entities]].
'''==[[Custom Field Type: Special – Browser Script|Special - Browser Script''']]==
* If you need to add a '''[[JavaScript''' ]] to a page that does not manifest on the page then you can use the [[Custom Field Type: Special – Browser Script|Special - Browser Script]] field type.
* Generally, this field type is used to specify validation routines.
* Functions defined in these scripts can be referenced in other calculated [[Custom Field|custom field]].
* You can control when the script is executed by using any valid '''JavaScript''' event triggers. You could force the script execution on '''page load''' (onLoad) or '''Save''' (OnSubmit).
'''==[[Template / Type Formula||Template Level Formulas''']]==
* Template level formulas can be associated with [[UTA level 1 ]] {{l1}} and 2 {{l2}} [[Template|templates]] plus [[Sales Tracking]]. * Template level formulas are not '''[[JavaScript''' ]] functions and are not executed in the client [[Browser|browser]].
* These formulas are executed in the database server and are constructed using valid '''SQL''' syntax.
* The benefit of this approach is that you can aggregate data across [[Entity|entities]] and update information across other [[Entity|entities]].
8,849
edits

Navigation menu