so currently I have an app that uses Cisco Spark, which can create connectors "webhooks" through a simple POST request. I am trying to create an app with MS teams that opens a connector "webhook" whenever a new team is created. Does Office365 Connectors support this functionality? or do the connectors need to be manually added through the MS teams application?
At present you need to do it manually through the MS teams application for each MS team you create.
Related
I am trying to find publish profile option in VS2017 Enterprise edition .However when i click Publish ,i get only the below option and no option to create a profile.I have a requirement to deploy WPF application to multiple servers ,and so wanted to create a publish profile for each server.
We would like to use the connectors feature to give users access to information from our line of business system inside groups. This seems possible using the webhooks method mentioned, but how do we get our connector in the list of Connectors our users can access?
That is correct, Incoming WebHooks allow you to build your own connectors.
You would be able to submit custom built Connectors to the 'Connector Store' as soon as connectors are out of developer preview.
Until then, you can facilitate connections to Office365 directly from your LOB applications using the 'Connect to Office 365 button'. This way you can abstract out copy-pasting WebHook URLs from your end users.
I am very new to SharePoint development as well as SharePoint overall, so I apologize if this question seems like a no-brainer. I'm currently working on a SharePoint 2013 app and I'm wondering if it's possible to make a call out to some URL from within the SharePoint environment. Basically, I want to do this within an event receiver after some action is done to a list, and from there I want to make a call to some web service on my server to update my system. Using the REST API to poll the SharePoint server isn't a good option for this scenario since it won't scale very well.
When dealing with SharePoint 2013 apps you can access any resource using standardized APIs. In addition to REST SharePoint is offering the JS Client Object Model (CSOM).
In order to access data from another web than the current one, your app needs the permission to interact with the entire tenant.
If you're trying to query data from another host, you have to use JSONP because of the same origin policy.
if you are building an app using the "new App Model" for wiring up Remote Event Receivers it is possible to do anything, in which your app hosting framework/environment allows you to. If you are building a Classic App (Farm Solutions) you'll have access to perform operations which are allowable from the SharePoint servers directly...typically this is a lot as GAC deployed assemblies are granted full trust.
depending on what you are trying to do and what kind of resources you app will consume. I'd consider moving the dependancies away from SharePoint and building using the new App Model versus the older farm solutions. As you sound like you are starting in SharePoint, this gives you an opportunity to learn the new ways of doing development for SharePoint.
Lastly, you might consider building a workflow. Not sure what kind of app you are building but the new workflow capabilities include actions which can make RESTful calls. Potentially making your application a "no code" solution. Again it all really depends.
Background:
I'm building a small application that will be run daily, pulling data from our own in-house databases and sending it over to our corporate Salesforce instance. I've built a custom object (called Marqui_Instance) in our Salesforce instance to house the data. The app will be creating a couple hundred of these, and attaching them to various Account records.
The Problem:
Our Salesforce instance is Professional edition, which means I can't generate the WSDL for our instance, which makes me think I'm not going to be able to develop code that can create/edit/delete Marqui_Instance objects.
Before I start floundering around in the dark, I thought I'd post on here for advice. The only thing I can think of is to create an identical object in a Salesforce developer account, and use the WSDL from there... but then when I go to deploy the code in production, will it work? I'm scared that the WSDL from my dev account will have some guids or something similar, and my code will only work against the dev account.
If you get your application certified by Salesforce they will provide you with a "Partner Application API" token. Using this when establishing the Salesforce API session will allow your application to work with a professional edition org.
Alternatively, you can also obtain API access to a Professional Edition org by paying an additional fee. You will need to contact your salesforce.com sales person.
Update: Apparently the functionality is enabled by Salesforce internally using the informally named "Black Tab".
See also: Re: Use of the API and Salesforce.com Professional Version
Access to the web services API for Salesforce is only available in Developer, Enterprise, and Unlimited Editions.
I believe that you aren't allowed to login to the API, so even if you managed to generate a WSDL it wouldn't work.
See the full edition comparison chart [PDF].
So here is the scenario:
I have a MOSS 2007 box and I want my clients to be able to access a SharePoint site via the internet. I am told that I will be using an IPA and AD for authentication. However I have a DB outside of SharePoint that holds various business data and I want to use Web Services to access the data, manipulate it, and send it back to SharePoint via web parts.
The issue is that, from what I understand, I am going to have to authenticate the AD user every time a request to the Web Service happens. Obviously I dont want to do this every time because they have already authenticated to get onto the site, however I do want each call to have some form of security so its not open calls to my db. I do plan on having other applications access this service outside of SharePoint, so I dont want to have to reinstall the service for each application or even again.
Has anyone had to perform this task or something similar or do you have any suggestions on how to do this?
Thank you in advance and happy coding!
Why not just deploy the webservice to Sharepoint using a Sharepoint solution and a Feature.
That way it will be running under the sharepoint app pool and all authentication is done by sp.
Edit:
Seeing that SharePoint should not be in "control" (as stated in the comment), you should create the webservice, and run the application it's under in as using Windows Authentication. IMHO you should create a WCF Service. The, using the information found in this article you make the Service authenticate users against the AD usergroups they are in. see the "Security: Authentication" section of the article.
Then in Visual Studio you create a webpart and add a service reference to the project, pointing to your newly created Service. Have the webpart perform the needed logic (i.e. display data etc.)
Deploy the webpart to SharePoint using a SharePoint solution (.wsp files, created with WSPBuilder). Google for SharePoint + wspbuilder + tutorials. The solution should contain 1 feature to deploy the webpart. WSPBuilder integrates with VS and allows for the creation of WSPBuilde project. add a webpart feature item to the project (it will create the xml (deployment related) and code file for the webpart.