Setting up tiles
Search Dynamic FactBoxes to see every tile. FactBox Pages (an action on the list and the card) shows each page that has the FactBox and how many tiles it shows; pick a page and choose Tiles to work page by page.
Admins can also go straight from a FactBox to its setup: … → Set Up This FactBox.
Create a tile
Section titled “Create a tile”-
On Dynamic FactBoxes, choose New.
-
General: Code, Description (the tile caption), Enabled and Sort Order.
-
Show On: add one or more pages, for example Customer Card and Customer List. The lookup lists every page that has the FactBox.
-
Measure: pick one, or choose New Measure. A new measure is created as Per Record, with its Record Table set to the table of the first Show On page, and opens so you can finish it:
- set the Source Table and Aggregation;
- write a filter using
{Rec.FieldName}for the record on screen, for exampleDocument Type=Order;Sell-to Customer No.={Rec.No.}.
The lookup offers just the measures that suit the tile’s pages, so the right choice is always easy.
-
Presentation: Decimal Places, Prefix, Suffix, Multiplier, Color and Tile Width.
-
Change Colour (optional): Change Colour When Value Is, Threshold and Condition Color. For example, Above
0in red turns an Overdue tile red whenever the customer has an overdue balance. -
Audience: Everyone, or Specific users.
-
Check it with Preview Value and Show Records. Both use the first record of the first Show On page’s table.
Per Record or Standard?
Section titled “Per Record or Standard?”- A Per Record measure must suit every page the tile is on. Customer Card and Customer List both show customers, so one measure works on both.
- A Standard measure works on any page, but shows the same value on every record. That’s useful for something like My overdue tasks in the corner of every page.
Example tiles
Section titled “Example tiles”| Page | Source Table (Record Table) | Aggregation | Filter |
|---|---|---|---|
| Customer Card | Sales Header (Customer) | Count | Document Type=Order;Sell-to Customer No.={Rec.No.} |
| Customer Card | Cust. Ledger Entry (Customer) | Sum of Remaining Amount | Customer No.={Rec.No.};Open=Yes;Due Date=..{TODAY-1D} |
| Item Card | Purchase Line (Item) | Sum of Outstanding Quantity | Type=Item;No.={Rec.No.} |
| Sales Order | Sales Header (Sales Header) | Count | Document Type=Order;Sell-to Customer No.={Rec.Sell-to Customer No.};No.=<>{Rec.No.} |
| Vendor Card | Purch. Inv. Header (Vendor) | Count | Buy-from Vendor No.={Rec.No.};Posting Date={TODAY-1Y}..{TODAY} |
Clear feedback
Section titled “Clear feedback”If a tile’s value can’t be worked out, for example because the user has no access to that data, the tile shows a grey - instead of interrupting their work. Clicking it explains why.
Fast by design
Section titled “Fast by design”Values are refreshed as the user moves between records. Counts and totals run as a single database query, so tiles keep up even on busy pages with large ledgers behind them.
Copying tiles to another company
Section titled “Copying tiles to another company”Use Set Up Dynamic FactBoxes. See Copying setup between companies.