Home Forum Blog Market Events Resources
Showing results for 
Search instead for 
Do you mean 
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.

NAB-K2-SharePointSearch

by NathanBrown ‎04-01-2016 04:08 PM - edited ‎04-06-2016 11:39 AM

This broker provides a method to craft optimized queries that will run against a SharePoint farm and expose them as specific broker objects to K2 Blackpearl.  This broker provides different functionality than the out of the box broker in that queries are pre-defined and optimized at design time so as to provide runtime performance that is more finely tuned to the need of a K2 form or workflow.

 

This broker can be described as providing ?views? into your SharePoint farm just as you might create highly optimized views or stored procedures in Microsoft SQL Server to only return columns needed for an operation.  So too can you create those CAML / KQL (and FQL) queries using this broker to return just the data you need.

 

This broker support both CAML and Search queries and can be used to expose an unlimited number of queries using a single instance of the broker.  It additionally supports caching to improve perormance when possible.

 

Full code is available on Githut at https://github.com/thystonius/NAB.K2

 

Demo

 

Part 1 of 3 - Basic Query at https://youtu.be/qnJH8dkaL9U

Part 2 of 3 - Parameters at https://youtu.be/c3QPxUi9XtE

Part 3 of 3 - SharePoint Search at https://youtu.be/RDZQrpLjrOM

 

Comments
by Jason_Discover
on ‎01-26-2017 04:40 PM

When compiling the source code from github I'm getting several errors, with the same results on different vm's. My environment is K2 4.6.11 and SharePoint 2013, with Visual Studio 2013 (Ultimate).

 

2017-01-26_18-28-04.png

 

 

 

This is an amazing solution, and your videos provide a greate overview of all of the features.

 

Jason

by Jason_Discover
on ‎02-08-2017 07:55 AM

The error was due to SharePoint not being up to date. After applying the most recent CU's, the error was resolved.