Hi Bill! Currently, we have SharePoint available on our GitHub repository for our customers to utilize and build against as they desire. Our Professional Services team has recently leveraged this code for a project using SharePoint 2016 and SharePoint online with Telligent Community version 10 as an example.
Outside of the GitHub offering, we currently do not have plans to continue investing in the SharePoint connector as a product out of the box. We have decided to go this route so that our customers get the benefit of the code we’ve written, and the option to extend it to their specific needs.
As I mentioned, we do have our Professional Services team that has an offering to build to your specifications as well as provide ongoing support if that is of interest. I can have Melanie reach out to you about this further if you’d like! Alternatively, just let me know if you have any questions and I’d be happy to help!
Just thought of a followup question ... We have both SP 2016 and SP 2012 in use. Is it possible to use the same connector build to access both? I noticed that the SP Client Components SDK is used in the build which could make it version dependent.
The connector only allowed for you to use a single Sharepoint instance. In terms of version, since it will require custom development, you could make it work for either version.
As I thought, either not both. I will have to check into the "single SharePoint Instance". I am not overly familiar with SP, and SP terminology to know what would constitute an instance and whether we have more than one. Thanks.
As I thought, either not both. I will have to check into the "single SharePoint Instance". I am not overly familiar with SP, and SP terminology to know what would constitute an instance and whether we have more than one. Thanks.
