Hi,
I have a solution containing a cloud workflow that copies folders and files from a document library on a SharePoint site. Since the solution will be moved between environments both within our own tenant and eventually to a customer’s tenant, the Site Address must be dynamic. This is how it looks in my Dev env. (and it works as expected):
If I export and then import the unmanaged solution into my Test env. and don’t change anything, it still works, in the sense that I can manipulate SharePoint folders, but obviously on my Dev SharePoint site as set in the environment variable like this (it’s got a crappy name, I know…):
Then I change the variable to my Test site:
When I stop/start my flow, I get the following error message:
Turn on failed. Flow client error returned with status code "BadRequest" and details "{"error":{"code":"InvalidOpenApiFlow","message":"Flow save failed with code 'DynamicOperationRequestClientFailure' and message 'The dynamic operation request to API 'sharepointonline' operation 'GetTable' failed with status code 'NotFound'. This may indicate invalid input parameters. Error response: {\r\n \"status\": 404,\r\n \"message\": \"List not found\\r\\nclientRequestId: 9b57a71c-ba1d-4595-8a82-8842cf75a6f0\\r\\nserviceRequestId: 9b57a71c-ba1d-4595-8a82-8842cf75a6f0\"\r\n}'."}}".
And if I go and look in my flow, the Create project folder configuration looks like this:
The List or Library now has a GUID and not a symbolic name which leads me to suspect that it does not point to the identically named document library on the Test site but maybe to the GUID of the library on my Dev site. But that’s just a guess.
And this doesn’t even begin to address the issue of trying to do this with a managed solution, in which case, to the best of my understanding, I can’t even change the environment variable, nor the issue of how to automate this in my CI/CD pipeline (some googling on the latter topic seems to indicate that this is a less than mature area).
Any help on how to fix the immediate problem would be much appreciated. For a while we can live with working with an unmanaged solution. But for environment variables to be of any use they must at a minimum be editable when manually importing a managed solution, so help on this topic is also appreciated. Input on the third CI/CD topic would be a bonus.
Thanks!
