Description
CMS message: Detail record could not be located
Symptoms
When navigating to a page within CMS, the user receives this message: Detail record could not be located.
Cause
This message indicates that the system is accessing a detailed content block, but either the block was configured incorrectly or the specified detailed record does not exist.
For example, the message can be seen just by viewing a custom CMS page called "test.do" where a detailed content block has been added:
Resolution
In the above example, the message displays in the Employee Self-Service site (for example, /ess/) on the test.do page. To resolve the message, go to the CMS page where the message is occurring:
- Navigate to Content Management > Pages.
- Go to the Test page.
- Under Related Links, select Edit Page.
- View the content block to see where the message is occurring:
- To prevent the message from displaying, delete this block using the X in the upper-right corner.
- To edit the block, select the pencil icon in the upper-right corner of the content block to view detailed content:
The content block above is configured to Show the page's current document. This is used to display the contents of an existing document, such as a knowledge article or service catalog request, as a block on a content page. For more about this functionality, see Detailed Content Blocks.
This detailed content block type cannot be used alone. The CMS page on which the detailed block is embedded must be specified in the Content Types record in the Default detail page field.
To view the content types and detailed pages:
- Navigate to Content Management > Content Types to see a list of content types and specified default detail pages:
- To create a CMS page that contains a custom detailed content block, ensure there is a corresponding Content Types record configured.
https://community.servicenow.com/thread/206370