---
schema_version: "1"
id: 84a633bebdd4e0279fc1836777b498eab4bd7f85bc9a75fb2f678e21b467eb28
title: Error Messages for Pages Without Data in Experience Builder
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/experience/264-0-0/community_builder_error_messages.md
canonical_url: https://help.salesforce.com/s/articleView?id=experience.community_builder_error_messages.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 2ef92abdcd6cd25bd20ba0af2f90fd9a532e90ca0a1946ab62a4482e58e199fb
description: When you use Lightning components to build a template-based page in Experience Builder, sometimes the page doesn’t load correctly on your site. Find out why this error happens, and how you can fix it. Make sure that the component has underlying data.
products:
  - Experiences
release: "264"
---
# Error Messages for Pages Without Data in Experience Builder

When you use Lightning components to build a template-based page in Experience Builder, sometimes the page doesn’t load correctly on your site. Find out why this error happens, and how you can fix it. Make sure that the component has underlying data.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: both Salesforce Classic and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</td></tr></tbody></table>

![Error message stating that page can't be loaded.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-experience-communities-264-0-0-production-enus/bf7df212-91a1-4fa3-a007-4d6f3e3b470b/communities/images/networks_no_data_error.png)

An error occurs on site pages in one of the following three instances:

- The page has no components
- The page has one or more components, and one or more have no underlying data
- Your org has SEO-friendly URLs enabled, but there’s no URL slug specified for the object type

You see this error when components rely on dynamic data, and they don’t find any underlying data to draw upon. For example, a Group component that doesn’t find a group ID, or a record that can’t find a record ID would both give you an error.

![Error message for dynamic data](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-experience-communities-264-0-0-production-enus/bf7df212-91a1-4fa3-a007-4d6f3e3b470b/communities/images/networks_missing_dynamic_data.png)

Why do I see this error?

In most situations, the page is trying to draw information when information doesn’t exist. Let’s say you make a record detail page for the Account object. If you don’t have any accounts set up in Salesforce, you see an error. Or let’s say you set up a group detail page, but your new site doesn’t have any groups. Once again, you see an error.

To fix the errors that involve SEO-friendly URLs, add a URL slug to the object that you’re referencing in the component. That way, the component loads the correct data. You can add the URL slug programmatically, such as using Apex, on the `ObjectRelatedUrl` object.

Any gotchas?

The Customer Service template uses topics to organize content in a site. To see topic detail pages, first set up [Navigational Topics in Site Management](https://help.salesforce.com/apex/HTViewHelpDoc?id=networks_topics_navigational.htm&language=en_US).

The following default pages in the Customer Service template can show this error. Here are some tips on how to fix it.

- Article Detail: Create at least one Salesforce Knowledge article in your org.
- Topic Detail: Create a Navigational Topic.
- Question Detail: Create a Navigational Topic. Use the Ask a Question button to create a question.
- Feed Detail: Use the Post Publisher or Ask a Question button to create a post or question.
- Group Detail: Create a group in the site.