Recipe - How To Store Per-Transaction Values

Recipe - How To Store Per-Transaction Values

This article describes a recipe to store per-transaction values. For example, you could calculate a "Commissionable" amount once and store it. You can then re-use this value within different reward formulas, or perhaps simply show it to payees.

Storing Per-Transaction Values

You can store calculated per-transaction values within:

• Scoring formulas
• Dynamic filtering formulas 
• Dynamic crediting formulas
• Custom metric formulas (when checkbox "this is a global attainment value" is NOT checked)
• Etc.

To store your value within the transaction, use the StoreTransaction(Name, Value) function. Specify a name and the value to store.

For example, you could specify a scoring formula like this to store a value called "Commissionable" within each transaction:

Loading Per-Transaction Values

You can now load per-transaction stored values within:

• Per-transaction reward formulas
• Global reward formulas
• Etc.

To load values from your transactions, use the [Transaction].[Name] convention.

For example, you can load each transaction's "Commissionable" value in a per-transaction reward formula:

For example, you can use the same convention to load each transaction's "Commissionable" value in a global reward formula:

 

Exporting Credits

When exporting credits from a calculation, calculated fields are automatically included in the export:

  

Displaying Stored Values

To display the calculated field on incentive dashboards, you need to specify an advanced option on your plan. The convention is CreditingFieldShow=<Name> (ex: CreditingFieldShow=Commissionable).