gramlot.

Course · Lesson 16 of 20

Save, restore and send Data deliberately

Choose an interchange format and separate local editing from explicit data delivery.

Reading · Practice2 sectionsPrerequisites: Load Data when it is read
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

Decide what leaves the page

The Data exchange example separates local editing from export, typed save/restore and submission. These are explicit actions. A field update is not automatically a database write, and leaving a page does not guarantee that its Data was saved.

JSON is useful for interchange with other services. Typed TYTX save/restore preserves the richer value model. Choose the representation according to what the receiver understands, rather than treating the two as interchangeable.

Define the receiving workflow

A form can send a structured request to a service that generates a document. The receiver owns authentication, authoritative validation and PDF generation; the page must handle the response. The core does not turn every form into a finished PDF application.

For offline work, decide where an explicit save goes and how it will later be delivered. Network access, CORS and CSP still apply when contacting an external service.

Your turn

Try it yourself

  1. Open Data exchange and save the example’s current record using its typed save action.
  2. Change a value, restore the saved record and compare the result.
  3. Inspect the JSON export and identify which representation your intended receiving service needs.

Check your understanding

Does downloading an offline page guarantee that the next browser session restores your edits?

Show the answer and expected result

No. Delivery and persistence are separate. The application needs a deliberate save/restore workflow or other storage. Test closing and reopening only after saving, and verify the actual result rather than assuming browser memory is durable.

Working examples and reference