SharePoint 2.5.0 Connectors - Setup and URLs?
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hi there! I'm trying to connect as an App/Service Principal to SharePoint with the new 2.5.0 connectors from the Marketplace.
The SharePoint team at my company created credentials and a certificate following these instructions https://help.alteryx.com/current/en/designer/data-sources/microsoft-sharepoint/create-certificate-fo...
Anyone have experience with this? What do I enter as the URL? Is it the base company url, the site url, the list url? I've tried a combo of these and they get an Error 404 message.
Is this user error, Alteryx error or SharePoint error (credentials not setup correctly?)?
- Labels:
- Best Practices
- Settings
- Sharepoint
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
I'm running into a similar issue too. I have SharePoint 2.3.0 tool for Lists and am getting the same 404 error when using the Browser sign in as a User (OAuth) option. I've tried different URLs but to no success. Anyone know why we are getting this error? My error results say User must be logged in but I had set up a DCM. I can connect to SharePoint Libraries without issues.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hi! Alteryx support got back to me and said there is an open defect when using the App-Only method. No ETA. :|
"The defect is TDCE-383. Essentially, something has changed for the App-Only method on our end at this time and we are trying to address this ASAP."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Confirming this is still an issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Can you let us know what the fix was?
We are seeing the same issue with 2.5 and 2.7 as well.
