SharePoint 2013 Hosting – HostForLIFE.eu : Getting List Properties From SchemaXml

Mar 21st

Posted by Peter in European SharePoint 2013 Hosting

There are many ways in CSOM to get the list properties from a SharePoint site. But there are a few properties which we can’t get directly from the list object. In this blog, I will explain how to find those using the SchemaXml.

This below-mentioned code sample will help us to get those properties which we cannot access directly from the list object.

The code block for this is mentioned below.

    using System;  
    using System.Collections.Generic;  
    using System.Linq;  
    using System.Text;  
    using System.Threading.Tasks;  
    using Microsoft.SharePoint.Client;  
    using System.Net;  
    using System.Security;  
    using Microsoft.SharePoint.Client.Utilities;  
    namespace SchemaXml {  
        class GetListSchema {  
            static void Main(string[] args) {  
                string listName = "CopyDoc";  
                string username = string.Empty;  
                string password = string.Empty;  
                SecureString secureString = new SecureString();  
                SharePointOnlineCredentials credentials = null;  
                List list = null;  
                System.Xml.Linq.XDocument xDocument;  
                string modified = string.Empty;  
                try {  
                    username = "userName@domain.com";  
                    password = "******";  
                    foreach(char ch in password.ToCharArray())  
                    secureString.AppendChar(ch);  
                    ClientContext ctx = new ClientContext("siteUrl"); //creating ClientContext from given SharePoint Site  
                    credentials = new SharePointOnlineCredentials(username, secureString); //creating creadential object for office365 site.  
                    ctx.Credentials = credentials;  
                    Web web = ctx.Web;  
                    list = ctx.Web.Lists.GetByTitle(listName);  
                    ctx.Load(list, l => l.SchemaXml, //loading schemaXml  
                        l => l.EnableVersioning);  
                    ctx.ExecuteQuery();  
                } catch (Exception ex) {}  
                try {  
                    using(System.IO.StringReader reader = new System.IO.StringReader(list.SchemaXml)) //getting the data from SchemaXml  
                    {  
                        xDocument = System.Xml.Linq.XDocument.Load(reader); //converting StringReader to XDocument  
                        List < ListpropertiesInfo > listSchemaXml = (from l in xDocument.Descendants("List") select new ListpropertiesInfo // class to store the properties  
                            {  
                                PropMajorVersionLimit = l.Attribute("MajorVersionLimit").Value,  
                                    PropMajorWithMinorVerionLimit = l.Attribute("MajorWithMinorVersionsLimit").Value,  
                                    PropExcludFromOfflineClient = l.Attribute("ExcludeFromOfflineClient").Value,  
                                    PropEnableFolderCreation = l.Attribute("EnableFolderCreation").Value  
                            }).ToList();  
                        foreach(var item in listSchemaXml) {  
                            int majorVersion;  
                            int minorVersion;  
                            if (list.EnableVersioning) {  
                                if (Int32.TryParse(item.PropMajorVersionLimit, out majorVersion)) {  
                                    Console.WriteLine("Major Version: " + majorVersion);  
                                }  
                                if (Int32.TryParse(item.PropMajorWithMinorVerionLimit, out minorVersion)) {  
                                    Console.WriteLine("Minor Version : " + minorVersion);  
                                }  
                            } else {  
                                Console.WriteLine("Major Version: 0");  
                                Console.WriteLine("Minor Version : 0");  
                            }  
                            if (Convert.ToBoolean(item.PropExcludFromOfflineClient)) Console.WriteLine("Status: false");  
                            else Console.WriteLine("Status: true");  
                            Console.WriteLine("Folder Creation: " + item.PropEnableFolderCreation);  
                            Console.ReadLine();  
                        }  
                    }  
                } catch (Exception er) {}  
            }#  
            region ListpropertiesInfo  
            public class ListpropertiesInfo {  
                public string PropMajorVersionLimit {  
                    get;  
                    set;  
                }  
                public string PropMajorWithMinorVerionLimit {  
                    get;  
                    set;  
                }  
                public string PropExcludFromOfflineClient {  
                    get;  
                    set;  
                }  
                public string PropEnableFolderCreation {  
                    get;  
                    set;  
                }  
            }#  
            endregion  
        }  
    }

using System;

using System.Collections.Generic;

using System.Linq;

using System.Text;

using System.Threading.Tasks;

using Microsoft.SharePoint.Client;

using System.Net;

using System.Security;

using Microsoft.SharePoint.Client.Utilities;

namespace SchemaXml {

class GetListSchema {

static void Main(string[] args) {

string listName = "CopyDoc";

string username = string.Empty;

string password = string.Empty;

SecureString secureString = new SecureString();

SharePointOnlineCredentials credentials = null;

List list = null;

System.Xml.Linq.XDocument xDocument;

string modified = string.Empty;

try {

username = "userName@domain.com";

password = "******";

foreach(char ch in password.ToCharArray())

secureString.AppendChar(ch);

ClientContext ctx = new ClientContext("siteUrl"); //creating ClientContext from given SharePoint Site

credentials = new SharePointOnlineCredentials(username, secureString); //creating creadential object for office365 site.

ctx.Credentials = credentials;

Web web = ctx.Web;

list = ctx.Web.Lists.GetByTitle(listName);

ctx.Load(list, l => l.SchemaXml, //loading schemaXml

l => l.EnableVersioning);

ctx.ExecuteQuery();

} catch (Exception ex) {}

try {

using(System.IO.StringReader reader = new System.IO.StringReader(list.SchemaXml)) //getting the data from SchemaXml

{

xDocument = System.Xml.Linq.XDocument.Load(reader); //converting StringReader to XDocument

List < ListpropertiesInfo > listSchemaXml = (from l in xDocument.Descendants("List") select new ListpropertiesInfo // class to store the properties

{

PropMajorVersionLimit = l.Attribute("MajorVersionLimit").Value,

PropMajorWithMinorVerionLimit = l.Attribute("MajorWithMinorVersionsLimit").Value,

PropExcludFromOfflineClient = l.Attribute("ExcludeFromOfflineClient").Value,

PropEnableFolderCreation = l.Attribute("EnableFolderCreation").Value

}).ToList();

foreach(var item in listSchemaXml) {

int majorVersion;

int minorVersion;

if (list.EnableVersioning) {

if (Int32.TryParse(item.PropMajorVersionLimit, out majorVersion)) {

Console.WriteLine("Major Version: " + majorVersion);

}

if (Int32.TryParse(item.PropMajorWithMinorVerionLimit, out minorVersion)) {

Console.WriteLine("Minor Version : " + minorVersion);

}

} else {

Console.WriteLine("Major Version: 0");

Console.WriteLine("Minor Version : 0");

}

if (Convert.ToBoolean(item.PropExcludFromOfflineClient)) Console.WriteLine("Status: false");

else Console.WriteLine("Status: true");

Console.WriteLine("Folder Creation: " + item.PropEnableFolderCreation);

Console.ReadLine();

}

} catch (Exception er) {}

region ListpropertiesInfo

public class ListpropertiesInfo {

public string PropMajorVersionLimit {

get;

set;

}

public string PropMajorWithMinorVerionLimit {

get;

set;

}

public string PropExcludFromOfflineClient {

get;

set;

}

public string PropEnableFolderCreation {

get;

set;

}

endregion

}

In this blog, I have explained how you can get the properties of a SharePoint list from SchemaXml. I hope this information will help you out in a few scenarios.

SharePoint 2013 Hosting Recommendation

HostForLIFE.eu’s SharePoint 2013 Hosting solution offers a comprehensive feature set that is easy-to-use for new users, yet powerful enough for the most demanding web developer expert. Hosted SharePoint Foundation 2013 is the premiere web-based collaboration and productivity enhancement tool on the market today. With SharePoint 2013 Foundation, you can quickly access and manage documents and information anytime, anywhere though a Web browser in a secure and user friendly way. SharePoint hosting services start at only at €9.99/mo, allowing you to take advantage of the robust feature set for a small business price. HostForLIFE.eu offers a variety of hosted SharePoint Foundation 2013 plans as well as dedicated SharePoint 2013 Foundation options

Sharepoint 2013 Hosting – HostForLIFE.eu :: How To Create Structural Navigation Nodes In Quick Launch And Top Navigation?

Mar 14th

Posted by Peter in European SharePoint 2013 Hosting

No comments

You can add, edit, or remove links on the left-hand menu (Quick Launch menu), the top menu (Top Navigation Node) through “Edit Links” in SharePoint. In this blog, we are going to create a structural navigation node that is the root node having subnodes in both – top navigation and quick launch.

The code block for this is mentioned below.

    using System;  
    using System.Linq;  
    using System.Security;  
    using Microsoft.SharePoint.Client;  
    namespace StructuralNavigationNode {  
        class Program {  
            static void Main(string[] args) {  
                ClientContext ctx = new ClientContext("http://portal/sites/site1");  
                string password = "Password";  
                SecureString secureString = new SecureString();  
                foreach(char c in password.ToCharArray()) secureString.AppendChar(c);  
                ctx.Credentials = new SharePointOnlineCredentials("user@domain.com", secureString);  
                ctx.ExecuteQuery();  
                Web web = ctx.Web;  
                NavigationNodeCollection quickLaunchNodeColl = web.Navigation.QuickLaunch; // we are getting all quick launch node collection  
                NavigationNodeCollection topNavNodeColl = web.Navigation.TopNavigationBar; // we are getting all top navigation node collection  
                NavigationNodeCreationInformation quickLaunchNodeCreation = new NavigationNodeCreationInformation();  
                quickLaunchNodeCreation.Title = "QuickLaunchNode";  
                quickLaunchNodeCreation.Url = "http://www.softreeconsulting.com/";  
                quickLaunchNodeColl.Add(quickLaunchNodeCreation); //we are creating root quick launch node  
                ctx.Load(quickLaunchNodeColl);  
                ctx.ExecuteQuery();  
                NavigationNode quickLaunchParentNode = quickLaunchNodeColl.Where(n => n.Title == "QuickLaunchNode").FirstOrDefault(); //retrieving parent quick launch root node for which we will add sub nodes  
                NavigationNodeCreationInformation quickLaunchNodeCreationInformation = new NavigationNodeCreationInformation();  
                quickLaunchNodeCreationInformation.Title = "QuickLaunchSubNode";  
                quickLaunchNodeCreationInformation.Url = "http://www.softreeconsulting.com/about-us/";  
                quickLaunchParentNode.Children.Add(quickLaunchNodeCreationInformation); //we are creating sub quicklaunch node  
                quickLaunchParentNode.Update();  
                ctx.ExecuteQuery();  
                NavigationNodeCreationInformation topNavNodeCreation = new NavigationNodeCreationInformation();  
                topNavNodeCreation.Title = "TopNavNode";  
                topNavNodeCreation.Url = "http://www.softreeconsulting.com/";  
                topNavNodeColl.Add(topNavNodeCreation); //we are creating root top navigation node  
                ctx.Load(topNavNodeColl);  
                ctx.ExecuteQuery();  
                NavigationNode topNavParentNode = topNavNodeColl.Where(n => n.Title == "TopNavNode").FirstOrDefault(); //retrieving parent top navigation root node for which we will add sub nodes  
                NavigationNodeCreationInformation topNavNodeCreationInformation = new NavigationNodeCreationInformation();  
                topNavNodeCreationInformation.Title = "TopNavSubNode";  
                topNavNodeCreationInformation.Url = "http://www.softreeconsulting.com/about-us/";  
                topNavParentNode.Children.Add(topNavNodeCreationInformation); //we are creating sub top navigation node  
                topNavParentNode.Update();  
                ctx.ExecuteQuery();  
            }  
        }  
    }

using System;

using System.Linq;

using System.Security;

using Microsoft.SharePoint.Client;

namespace StructuralNavigationNode {

class Program {

static void Main(string[] args) {

ClientContext ctx = new ClientContext("http://portal/sites/site1");

string password = "Password";

SecureString secureString = new SecureString();

foreach(char c in password.ToCharArray()) secureString.AppendChar(c);

ctx.Credentials = new SharePointOnlineCredentials("user@domain.com", secureString);

ctx.ExecuteQuery();

Web web = ctx.Web;

NavigationNodeCollection quickLaunchNodeColl = web.Navigation.QuickLaunch; // we are getting all quick launch node collection

NavigationNodeCollection topNavNodeColl = web.Navigation.TopNavigationBar; // we are getting all top navigation node collection

NavigationNodeCreationInformation quickLaunchNodeCreation = new NavigationNodeCreationInformation();

quickLaunchNodeCreation.Title = "QuickLaunchNode";

quickLaunchNodeCreation.Url = "http://www.softreeconsulting.com/";

quickLaunchNodeColl.Add(quickLaunchNodeCreation); //we are creating root quick launch node

ctx.Load(quickLaunchNodeColl);

ctx.ExecuteQuery();

NavigationNode quickLaunchParentNode = quickLaunchNodeColl.Where(n => n.Title == "QuickLaunchNode").FirstOrDefault(); //retrieving parent quick launch root node for which we will add sub nodes

NavigationNodeCreationInformation quickLaunchNodeCreationInformation = new NavigationNodeCreationInformation();

quickLaunchNodeCreationInformation.Title = "QuickLaunchSubNode";

quickLaunchNodeCreationInformation.Url = "http://www.softreeconsulting.com/about-us/";

quickLaunchParentNode.Children.Add(quickLaunchNodeCreationInformation); //we are creating sub quicklaunch node

quickLaunchParentNode.Update();

ctx.ExecuteQuery();

NavigationNodeCreationInformation topNavNodeCreation = new NavigationNodeCreationInformation();

topNavNodeCreation.Title = "TopNavNode";

topNavNodeCreation.Url = "http://www.softreeconsulting.com/";

topNavNodeColl.Add(topNavNodeCreation); //we are creating root top navigation node

ctx.Load(topNavNodeColl);

ctx.ExecuteQuery();

NavigationNode topNavParentNode = topNavNodeColl.Where(n => n.Title == "TopNavNode").FirstOrDefault(); //retrieving parent top navigation root node for which we will add sub nodes

NavigationNodeCreationInformation topNavNodeCreationInformation = new NavigationNodeCreationInformation();

topNavNodeCreationInformation.Title = "TopNavSubNode";

topNavNodeCreationInformation.Url = "http://www.softreeconsulting.com/about-us/";

topNavParentNode.Children.Add(topNavNodeCreationInformation); //we are creating sub top navigation node

topNavParentNode.Update();

ctx.ExecuteQuery();

}

Output

After the code is executed, you can see the root navigation with its respective subnodes created successfully.

SharePoint 2013 Hosting Recommendation

Sharepoint 2013 Hosting – HostForLIFE.eu :: Search Database Related Tables Using BCS

Mar 8th

Posted by Peter in European SharePoint 2013 Hosting

No comments

Configure BCS to search a Database, where the Tables have a parent-child relationship. When searching for any term within the child table, the item linked in the parent item has to be displayed on the result page then the searched term or item from the child table.

The requirement makes sense in a way, that the child tables are considered as paragraphs within a document. When searching for a term within the paragraph, you would expect the link to the document to be displayed. After all, the child tables will always be additional information about the parent item.

Design

While designing for this requirement the data to be retrieved from the parent table and the child table has to be from two different entities, however, they need to be within the same LOBInstance.

By which, we have control to define the association between these entities within the Model.

Here is how the Method and the method instance need to be defined.

<Method Name=”PartItemToRevisionItem”>      <Properties>          <Property Name=”HideOnProfilePage” Type=”System.Boolean”>true</Property>      </Properties>      <Parameters>          <Parameter Name=”partID” Direction=”In”>              <TypeDescriptor Name=”PartID” TypeName=”System.String” IdentifierEntityName=”PartItem” IdentifierEntityNamespace=”MultiBCS.MultiEntity” IdentifierName=”PartID” ForeignIdentifierAssociationName=”PartItemToRevisionItem” />          </Parameter>          <Parameter Name=”revisionAssociationItemList” Direction=”Return”>              <TypeDescriptor Name=”RevisionItemList” TypeName=”MultiBCS.MultiEntity.RevisionItem[], MultiEntity” IsCollection=”true”>                  <TypeDescriptors>                      <TypeDescriptor Name=”RevisionItem” TypeName=”MultiBCS.MultiEntity.RevisionItem, MultiEntity”>                          <TypeDescriptors>                              <TypeDescriptor Name=”RevisionID” TypeName=”System.String” IdentifierEntityName=”RevisionItem” IdentifierEntityNamespace=”MultiBCS.MultiEntity” IdentifierName=”RevisionID” />                              <TypeDescriptor Name=”Revision_Name” TypeName=”System.String” />                              <TypeDescriptor Name=”Revision_Cost” TypeName=”System.Int32″ />                              <TypeDescriptor Name=”PartID” TypeName=”System.String” />                              <TypeDescriptor Name=”Revision_Type” TypeName=”System.String” />                          </TypeDescriptors>                      </TypeDescriptor>                  </TypeDescriptors>              </TypeDescriptor>          </Parameter>      </Parameters>      <MethodInstances>          <Association Name=”PartItemToRevisionItem” Type=”AssociationNavigator” ReturnParameterName=”revisionAssociationItemList” IsCached=”false”>              <Properties>                  <Property Name=”AttachmentAccessor” Type=”System.String”></Property>              </Properties>              <SourceEntity Name=”PartItem” Namespace=”MultiBCS.MultiEntity” />              <DestinationEntity Name=”RevisionItem” Namespace=”MultiBCS.MultiEntity” />          </Association>      </MethodInstances>  </Method>

The association method can be written in any entity (parent or child). But the tag that defines the source and the destination can be seen within the MethodInstance.

Silver Bullet

Of all this requirements, the most important part and the one that defines that the child tables need to be crawled as attachments, by which I mean that “when searched for a term in the child table, the item linked in the parent table to be displayed”. The below tag needs to be added within the method instance, otherwise multiple results will be displayed for a single record, which is unwanted.

<Property Name=”AttachmentAccessor” Type=”System.String”></Property>

1	<Property Name=”�� Type=”System.��></Property>

Thanks to Scott Hillier to the right pointer on the “Attachment Accessor” which is significant for this requirement.

SharePoint 2013 Hosting Recommendation

Sharepoint 2013 Hosting – HostForLIFE.eu :: Use Of UseClientCachingForSearch Property In BDC Model

Feb 28th

Posted by Peter in European SharePoint 2013 Hosting

No comments

We are using a custom BCS connector to crawl the data from SQL for a SharePoint 2013 search. There are 2.1 million records in the SQL table. The data is being read in batches and provided to the crawler (we have implemented our own logic to supply the records to the search crawler in batches).

The issue here is the crawl rate. The rate of crawl at which the out of the box (OOTB) External Content type retrieves the data is way higher than the custom process (2.1 M items in 8.30 hrs.). But when we try to crawl the BCS External Content type using custom BCS connector, it takes 10 hours. (If the load is high or multiple users log into the server sometimes it takes 19 hrs. to crawl 1M items)

At this point in time, we are unable to identify the cause of the issue or find the section where the bottleneck is.

Solution

When we compared the OOTB and Custom BDC model files (.bdcm), we found that one additional property called UseClientCachingForSearch was used in the OOTB BDC model. Then, we started investigating this property and found that this is the property that produced the magical number for OOTB BCS.

The UseClientCachingForSearch property in the BDC model improves the speed of full crawls by caching the item during enumeration. This property is also recommended when implementing incremental crawls that are based on change logs because it improves incremental crawl speed.

Basically, when we make a model using Out of the box, the UseClientCachingForSearch property is added automatically. When we make our own custom BCS model we have to add this property manually.

Important Note

If BCS crawl items are larger than 30 kilobytes on average, we should not set this property, as it will lead to a significant number of cache misses and negate performance gains. In our case, our records are not more than this limit.

Output

After implementing this, we get the magical number similar to out of the box BCS crawl in our custom BCS crawl activity. This is just in the development environment. When it goes to production, it should definitely give very good performance.

Why Custom BCS Connector?

Custom BCS connector is used here for the following reasons,

Out of the box, BCS Connector has a response limit. The maximum number of rows that can be read through the Database Connector is 1,000,000. The limit can be changed via the ‘Set-SPBusinessDataCatalogThrottleConfig’ cmdlet using PowerShell. But it is not recommended. To handle this threshold issue on the search crawler, we are writing the custom BCS connector with the batch processing.
Currently, our external system (Teamcenter) has 2.1 million data and this may grow up to 6 million in the next 4 to 5 years. To process this dynamic data growth we have implemented batch processing in our Custom BCS connector.
OOTB SharePoint incremental crawl will not delete the deleted items in the external system from the search indexes until we do a full crawl. To implement this logic for incremental crawl we choose custom BCS connector.

The researches, findings, and learning we have done in this project are going to be a great knowledge-base for everyone.

SharePoint 2013 Hosting Recommendation

Sharepoint 2013 Hosting – HostForLIFE.eu :: How To Use Submit Logic In PowerApps

Feb 14th

Posted by Peter in European SharePoint 2013 Hosting

No comments

When you insert a connection to SharePoint, a form or the grid loads up but you don’t have a way to edit the form and submit the newly updated data. We can achieve that with the following process.

Once your connection is finished with the data, drag and drop a button from the gallery and name it “Submit”, as shown below under the button’s Advanced properties.

To add the functionality to the button where it will update your data source, on the window above, you will have to update the OnSelect code. Paste the following code for each submit.

Submit – SubmitForm(Form1)

SubmitForm is the function to submit the form and “Form1” is the name of your data source. This button, when clicked, submits the data to the data source. I hope it helps you. Keep reading and keep learning!

SharePoint 2013 Hosting Recommendation

Sharepoint 2013 Hosting – HostForLIFE.eu :: SharePoint App Operations Using PnP PowerShell

Jan 24th

Posted by Peter in European SharePoint Server 2013 Hosting

No comments

PnP PowerShell can be used to automate the deployment, publishing, installing, upgrading and retracting of apps in Sharepoint online as well as Sharepoint on-premises.

In this blog, we will look at steps to get, add, install, deploy, update, remove and uninstall SharePoint apps to modern sites using PnP PowerShell.

Adding and publishing apps to the app catalog:

Adding app (.sppkg file, .app file) to the tenant scoped app catalog.

 Add-PnPApp-Path<App Path>-ScopeTenant

1	Add-PnPApp-Path<App Path>-ScopeTenant

Once added, we need to continue with publishing the app using the below command.

 Publish-PnPApp -Identity <App Id>

1	Publish-PnPApp -Identity <App Id>

Removing the app from the app catalog:

To remove the specified app from the tenant scoped app catalog.

 Remove-PnPApp -Identity <App Id> -Scope Tenant

1	Remove-PnPApp -Identity <App Id> -Scope Tenant

Getting the app from the app catalog:

Get a list of apps in the tenant scoped app catalog.

 Get-PnPApp -Scope Tenant

1	Get-PnPApp -Scope Tenant

Installing the app to site collection:

After the app is added to the app catalog and published, you can install the app to the specific site.

Install-PnPApp -Identity <App Id> -Scope Tenant

1	Install-PnPApp -Identity <App Id> -Scope Tenant

Upgrading the app:

The command is used to update an already installed app if a new version is available in the tenant app catalog.

Update-PnPApp -Identity <App Id> -Scope Tenant

1	Update-PnPApp -Identity <App Id> -Scope Tenant

Uninstalling the app from site collection:

To uninstall the app from your site.

Uninstall-PnPApp -Identity <app id> -Scope Tenant

1	Uninstall-PnPApp -Identity <app id> -Scope Tenant

In the above write-up, I have explained all the PnP PowerShell commands for all operations, such as – getting, adding, installing, upgrading, removing, and uninstalling SharePoint app on SharePoint modern sites programmatically.

SharePoint 2013 Hosting Recommendation

European Sharepoint 2013 Hosting Blog

SharePoint 2013 Hosting – HostForLIFE.eu : Getting List Properties From SchemaXml

SharePoint 2013 Hosting Recommendation

Sharepoint 2013 Hosting – HostForLIFE.eu :: How To Create Structural Navigation Nodes In Quick Launch And Top Navigation?

SharePoint 2013 Hosting Recommendation

Sharepoint 2013 Hosting – HostForLIFE.eu :: Search Database Related Tables Using BCS

Design

Silver Bullet

SharePoint 2013 Hosting Recommendation

Sharepoint 2013 Hosting – HostForLIFE.eu :: Use Of UseClientCachingForSearch Property In BDC Model

Solution

Why Custom BCS Connector?

SharePoint 2013 Hosting Recommendation

Sharepoint 2013 Hosting – HostForLIFE.eu :: How To Use Submit Logic In PowerApps

SharePoint 2013 Hosting Recommendation

Sharepoint 2013 Hosting – HostForLIFE.eu :: SharePoint App Operations Using PnP PowerShell

SharePoint 2013 Hosting Recommendation

BLOGROLL

Featured On

European Sharepoint 2013 Hosting Blog

SharePoint 2013 Hosting – HostForLIFE.eu : Getting List Properties From SchemaXml

SharePoint 2013 Hosting Recommendation

Sharepoint 2013 Hosting – HostForLIFE.eu :: How To Create Structural Navigation Nodes In Quick Launch And Top Navigation?

SharePoint 2013 Hosting Recommendation

Sharepoint 2013 Hosting – HostForLIFE.eu :: Search Database Related Tables Using BCS

Design

Silver Bullet

SharePoint 2013 Hosting Recommendation

Sharepoint 2013 Hosting – HostForLIFE.eu :: Use Of UseClientCachingForSearch Property In BDC Model

Solution

Why Custom BCS Connector?

SharePoint 2013 Hosting Recommendation

Sharepoint 2013 Hosting – HostForLIFE.eu :: How To Use Submit Logic In PowerApps

SharePoint 2013 Hosting Recommendation

Sharepoint 2013 Hosting – HostForLIFE.eu :: SharePoint App Operations Using PnP PowerShell

SharePoint 2013 Hosting Recommendation

BLOGROLL

Featured On

Tags