Does anyone have any additional setup/guide/information regarding the use of File Stores in Netcall.
I have used various API calls with our Azure communication service to interact with MS Graph and that all works (calendars, teams, uploading to sharepoint), but when I attempt to setup a File Store using the same access values.
Tenant ID
Azure client ID
Azure key
Drive ID
I simply get a Connection not working message when hitting “Test Connection”, its hard to know whats wrong with such a generic error message.
I’m fairly certain I am passing all the correct values into setup.
Does anyone know what privileges the azure comm service requires to utilise File Stores.
Did you enter a path? The path help text suggests its the full URL when it isn’t. Try no path initially and see if that works. A test .txt file should appear in the recycle bin of the SharePoint site.
If it works with no path simplify the path to whatever comes after the Drive ID you’ve specified. e.g. If the drive ID is for the “Shared Documents” library and you have a folder under there called PDFs the path would just be PDFs.
The problem I’m now having is that even with a file store setup, with the connection test working, the files aren’t moving to SharePoint at all. This includes new files added to an object with file store set and existing files which according to the docs should move on running batch jobs.
Some documentation, provided by Netcall, for setting up the SharePoint site and Azure app registration would be really helpful. If the guide explained what needed to be setup and where to take each of the 4 values for the file store from that would help rule out a configuration issue.
When I had any of those values incorrect, in the detective say “incorrect azure key” for example.
My first thoughts were that Azure client ID and Azure key would be the value and secret from “certificate and secrets”, but the azure client ID was the actually the application ID from the App registration.
And the Azure key the value from certificates and secrets.
I think some documentation from Netcall rather than guess work is much needed.