Messages and what to do
Lesson 24 of 25 6 min read
Every message the Maps & Profiles screens show, what causes it, and what to do next.
Prism's messages are short and precise. Once you know what each one means, most of them tell you the next step directly. Use this lesson as a reference: the messages are grouped by when you will see them.
While you edit and validate
| Message | Cause | What to do |
|---|---|---|
| Nothing to report. | The body is correct. | Nothing. |
| N errors … An error blocks publishing; a warning does not. | The body has errors. | Correct the errors. Select the node id to go to each one. |
| A line and column, for example Line 48, column 57 | Supply Lens cannot read the body at all, for example a mistake in a name. | Select it to go to that line, and fix it. |
| There are no changes to save. | You selected Save with no changes. | Nothing. |
| Nothing has been published yet, so there is nothing to compare with. | You selected Changes before the first publish. | Nothing. |
| This is the shared base we ship. It cannot be edited here. | You opened a shared base. | Create an overlay onto it. |
When you publish
| Message | Cause | What to do |
|---|---|---|
| Version N is live. | The publish worked. | Select Done. |
| Publishing this would break N overlays. Nothing has been written. | The new version breaks overlays that follow it. | Select Go and fix them (safe), or Publish anyway and park them if the fix is urgent. |
| Another publish of this definition committed first | A different administrator published at the same time. | Open the map or profile again and look at the new version. |
Would break is not a failure
Publishing this would break N overlays is the publish checking itself before writing anything. Nothing has changed. Treat it as a question about who you would leave behind.
When you rebase
| Message | Cause | What to do |
|---|---|---|
| That does not compose, so nothing was changed. | The overlay does not fit the base version you chose. | Select a different base version, or change the overlay first. |
When you check what runs
| Message | Cause | What to do |
|---|---|---|
| Nothing is configured for that. | No published map or profile for that kind, integration type and document type. | Publish one. |
| Something is configured, but its chain no longer composes, so nothing would run. | An overlay does not fit its base. | Correct the overlay. |
On the overview
| Message | Cause | What to do |
|---|---|---|
| A warning about a Held overlay | A new base version broke an overlay and was published anyway. | Edit the overlay to fit, publish it, then Rebase. |
Reading the messages in order
You publish a new version of a create map. Prism says Another publish of this definition committed first. You reopen the map: a colleague has just published v8. You select Edit on v8, paste your change in, and publish again. This time Prism says Publishing this would break 1 overlays. Nothing has been written. You select Go and fix them, correct the overlay, and publish again: Version 9 is live.
Recap
- Diagnostics messages name a node id or a line and column; select it to jump there.
- Nothing has been written means the publish stopped safely; fix or park the overlays.
- Another publish … committed first: reopen and start from the new version.
- That does not compose: the rebase changed nothing.
- Nothing is configured and chain no longer composes come from What actually runs.
Your progress is saved in this browser. Create a free account to keep it everywhere, take quizzes and earn certificates.