I am trying to test some processes in our QA environment. Each process includes the same common library but one of the processes is failing trying to read a file from SharePoint using the same library activity as the other processes. I’ve narrowed the issue down to package requirements.
All the processes need a connection to SharePoint and all except the failing process use:
I can’t for the life of me understand why the OneDrive connection and queue didn’t show up for this process. They were all developed in the same way and published the same way. Also not that there should also be a connection for MS Outlook for all of my processes, which haven’t shown up.
I don’t know if I don’t have permissions to add them (although why should I have to manually add them), or what the problem is.
I guess I should have mentioned: The SharePoint activities are in a library I created and was published to the tenant. That library is a dependency for the process I published so I don’t need to include that dependency in the process. It comes in as part of the library’s dependency list.
I’ve gone to the package URL you showed. It has the following statement:
If the Office365 package is part of the library and the library is part of the process, this tells me that it should be picked up automatically. Same goes for the queues, etc.
The issue is “resolved”; or more accurately, a work-around was found. Apparently if Integration Services (Outlook, SharePoint) is used in a library, it will not be recognized properly when the main process is published to Orchestrator. I therefore created a dummy .xaml file that used the integration services, but were never called, to the project and published it.
The other thing I discovered was that it might take a few minutes for Orchestrator to add the integration services to the Package Requirements.
