Edit, validate and save
Lesson 12 of 25 8 min read
Use the buttons on a map or profile page, read the Diagnostics panel, and avoid clashing with a colleague.
The page of a map or profile is where most of your time goes. In this lesson you will learn which buttons appear for which status, how to read Diagnostics, and how to jump straight to the part of the body that needs fixing.
The page
The page shows the version, status, scope and integration, and the body in an editor.
Someone else is here
If another person has the same page open, the top of the page shows their name, for example Name is also viewing. Speak to them before you save or publish, so you do not both change the same map or profile at once.
The buttons
The buttons at the top change with the status:
| Status | Buttons |
|---|---|
| Draft | Validate, Save, Changes, Publish, Preview, Versions |
| Live | Edit, Archive, Preview, Versions |
| Overlay | Also Rebase and End result |
| Button | What it does |
|---|---|
| Edit | Starts a new version from the live one. You cannot edit a shared base. |
| Validate | Checks the body. The result shows in Diagnostics. Not available for an overlay. |
| Save | Saves a new version. A draft replaces the draft before it. |
| Changes | Compares your version with the live version. |
| Publish | Makes the version live. |
| Discard | Removes your changes to a live version. |
| Archive | Stops the live version. Nothing takes its place. |
| Preview | Shows the body as an outline. |
| Versions | Opens the version history. |
A typical edit goes: Edit on the live version, change the body, Validate, Save, Changes to review what you did, then Publish.
Use Changes before every publish
Changes shows exactly what you are about to put live, compared with the live version. Before the first publish there is nothing to compare with, and Prism says so: Nothing has been published yet, so there is nothing to compare with.
Diagnostics
When you select Validate, the result shows in the Diagnostics panel. Each problem Supply Lens finds is also underlined in the editor. Put the pointer on an underline to read the message.
- Nothing to report. means the body is correct.
- An error stops you publishing. Correct it, then validate again.
- A warning does not stop you publishing.
Each message names a node id: the part of the body it is about, not a form field. Select the node id to scroll the editor to that part of the body.
If Supply Lens cannot read the body at all, for example because of a mistake in a name, the message shows a line and column instead, such as Line 48, column 57. Select it to scroll to that line.
Overlays are checked differently
Validate is not available on an overlay, because an overlay only makes sense against its base. Supply Lens checks it with its base when you publish. Use End result to see what it will produce.
Fixing a broken draft
You validate Hilltop's new purchase order map and the panel shows 2 errors, with the reminder that an error blocks publishing and a warning does not. The first names the node line.quantity; you select it and the editor scrolls there, where the message reads A coalesce has no values. The second shows Line 112, column 9, where a name in the body is mistyped. You fix both, validate again, and see Nothing to report. You select Save.
Recap
- The buttons depend on status: drafts have Validate, Save, Changes and Publish; live versions have Edit and Archive.
- If someone else is viewing the page, talk to them before you save or publish.
- Validate fills Diagnostics: errors block publishing, warnings do not.
- Select a node id, or a line and column, to jump to the problem.
- Overlays cannot be validated alone; they are checked with their base at publish.
Your progress is saved in this browser. Create a free account to keep it everywhere, take quizzes and earn certificates.