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.
Related
What is the difference between these 2 APIs and what do they each allow you to do?
I've tried Googling, searching the GCP docs and running some tests in the console.
The API Library console page does not have very descriptive descriptions [see screenshot].
If I leave both of those APIs disabled, I can still create a SQL instance! Creating a SQL instance only appears to need the Compute Engine API.
If I need to use the Python libraries to query the instance(s) for its attributes, the error message tells me that the SQL Admin API (sqladmin.googleapis.com) needs to be enabled. However, there's a twist. The API only needs to be enabled in the Project that's set in my ADC, not in the (other) Project that I'm actually querying.
Cloud SQL Admin API aka sqladmin.googleapis.com is the correct api to use. You can also look at the documentation page for all the actions this API supports. You can ignore the Cloud SQL aka sql-component.googleapis.com. It is an obsolete api that does nothing.
Admin API is for administering your instances programmatically. The REST API is defined by BackupRuns, Databases, Instances, Flags, Operations, SslCerts, Tiers, and Users resources. You can check the details here. As you have correctly noticed this api is not required for creating Cloud SQL instances but it is required for other features like Flags, Certs BackupRuns etc.
I have a "Starter Portal" Power App Portal. I would like to utilize JavaScript and the Web API for querying data. Documentation states
You can use the Web API to perform create, update, and delete operations across all Microsoft Dataverse tables from your portal pages.
Further documentation only lists the CREATE, UPDATE, DELETE operations, and this API being accessible as
[Portal URI]/_api
And I have found how to successfully authenticate using a helper method to get a token for the header:
shell.getTokenDeferred().done(function (token) { ...}
This allows authentication as the user logged into the portal so I believe all relevant Table Permissions, etc. are applied.
But, I would like to retrieve data (HTTP GET). I know this is possible from the Dataverse Web API.. This api is exposed as
[Organization URI]/api/data/v9.1/
Are these really the same API, just exposed a different way for the portal? Is it possible to use the GET endpoints or the second API altogether, authenticated as a Portal Contact user like the previous operations?
It's the same API but permissions are different, you will need to enable the tables you want to access inside the _api endpoint.
You can read more info at this page: https://learn.microsoft.com/en-us/powerapps/maker/portals/read-operations, there is also an XrmToolBox tool to assist you in this operation (but I didn't try it) https://www.xrmtoolbox.com/plugins/PowerPortalWebAPIHelper/
Regarding the Web API calls, I released a new tool to create them (similar to CRM REST Builder) I also added a "Portals" syntax (is in preview) but the generated urls are the same. Link: https://github.com/GuidoPreite/DRB
I have installed WSO2 IS (5.10) and Analytics (5.8), on separate servers, following the WSO2 IS documentation. I am successfully getting authentication events received into Analytics and can view them (after many headaches with IS insisting on using ports and SSL that I never told it to use - another story).
Now I can log into the dashboard, (/portal, admin/admin), and I see the IS events. Where do I manage portal users, permissions, and authentication? I want to add additional viewers (via LDAP) but can't even find a place to change the admin password, never mind manage additional users.
Nor can I find any documentation on how to manager users in Analytics. Any help is appreciated.
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.