Exception :- While connecting webparts “No Provider Schema” – Relational WebPart – SharePoint Online

Sathish Nadarajan
 
Solution Architect
August 21, 2018
 
Rate this article
[Total: 0    Average: 0/5]
 
Views
1720

In this article, let us discuss about an exception “No Provider Schema” when trying to connect two webparts. In my case, I have a Custom NewForm on which I have a default list webpart. Along with that, I am adding another webpart which is connected with the default webpart.

 

image

 

On the above screen, the SOW Tracking webpart should provide Filter data to SOW Communications WebPart. To achieve that, usually we will establish a connection as shown in the image.

 

image

 

The connection will be established in the Default NewForm.aspx without any issue. But, when I try to do that from a custom new form, then the exception will be shown as below.

 

image

To overcome this, on the custom new form, we need to add the below tags.

 

 <WebPartPages:SPProxyWebPartManager runat="server" ID="__ProxyWebPartManagerForConnections__">
 
 <SPWebPartConnections></SPWebPartConnections></WebPartPages:SPProxyWebPartManager>
 

The position of the snippet in the customnewform.aspx would be

 

image

 

We need to edit this form in SharePointDesigner and update the aspx file.

Happy Coding,

Sathish Nadarajan.

Author Info

Sathish Nadarajan
 
Solution Architect
 
Rate this article
[Total: 0    Average: 0/5]
 
Sathish is a Microsoft MVP for SharePoint (Office Servers and Services) having 13+ years of experience in Microsoft Technologies. He holds a Masters Degree in Computer Aided Design and Business ...read more
 

Leave a comment