After successfully implementing a custom contact facet inside Sitecore, the next step was then to display this data on a custom tab inside the Experience Profile.
![]()
This traces back to the configuration file where the data access layer (query, population, etc.) is registered.
![]()
In the example above, the XML element is titled "employee". Which then means that the JavaScript file which is adding the new custom tab should reference it inside the base URL for the service.
Once all of the required steps were completed, the following error was appearing on the page and no data was displaying:
No pipeline was found for View [name]
This traces back to the configuration file where the data access layer (query, population, etc.) is registered.
In the example above, the XML element is titled "employee". Which then means that the JavaScript file which is adding the new custom tab should reference it inside the base URL for the service.
var baseUrl = "/sitecore/api/ao/v1/contacts/" + contactId + "/intel/employee";Ensuring these two variables matched, stopped the error from occurring.