gramlot.

Course · Lesson 15 of 20

Load Data when it is read

Distinguish a lazy Data resolver from an immediate RPC and a remote interface fragment.

Reading · Practice2 sectionsPrerequisites: Load a Source fragment
Course contents
Orientation
  1. 01 Install Gramlot and create Hello world
  2. 02 Connect text and colour to Data
  3. 03 Explore Data and Source with the inspector
  4. 04 Use relative and symbolic paths, then dataFormula
  5. 05 Call the server with dataRpc and .remote
Start a project
  1. 01 Create your first project
  2. 02 Read and compose Source
  3. 03 Initialize structured Data
  4. 04 Connect fields and values
Build a form
  1. 05 Accept values, preserve drafts
  2. 06 Declare a calculation
  3. 07 Run an action at the right time
  4. 08 Name behavior and understand lifecycle
Compose an interface
  1. 09 Arrange an application with containers
  2. 10 Style the page you own
  3. 11 Publish messages and ask before acting
  4. 12 Format values without changing Data
Connect services
  1. 13 Call an endpoint
  2. 14 Load a Source fragment
  3. 15 Load Data when it is read
  4. 16 Save, restore and send Data deliberately
Deliver your work
  1. 17 Organize pages and choose a host
  2. 18 Read the JavaScript edition
  3. 19 Deliver the JavaScript edition offline
  4. 20 Explain and change a complete form

Declare a resolver at a Data path

dataRemote associates a destination with a method that supplies its value. It resolves lazily when the Data is read. By comparison, dataRpc is an explicit triggered call, and remote supplies Source to an element.

This distinction lets you reason about whether opening a panel, reading a value or changing an input actually requests server work. Declaration alone does not establish durable storage or an automatic synchronization mechanism.

Inspect the cache policy

The Data remote example documents cacheTime and shows how a later read can reuse or resolve a value. Follow the stated timing in that example rather than assuming every read makes a fresh request.

When a result appears stale, first check which operation performed a read, which arguments were used and whether the resolver cache still applies. Reloading the entire page hides those relationships instead of explaining them.

Your turn

Try it yourself

  1. Open Data remote and read its explanation before activating the control that reads the value.
  2. Perform the initial read and note the result.
  3. Repeat within and after the example’s stated cache period; compare the evidence shown by the example.

Check your understanding

Which mechanism fits each task: returned scalar on click, a server-built panel, or a lazy Data value?

Show the answer and expected result

Use dataRpc for the triggered result, remote for the Source fragment, and dataRemote for a lazy value. They have different triggers and destinations even when all three ultimately call server-side methods.

Working examples and reference