I am having problems running the connector.
When using the correct Document GUID (either with or without the curly brackets) The connector fails with a 'BadGateway' error.
"code": 502, "source": "uk-001.azure-apim.net", "clientRequestId": "bf53866f-0f29-4393-9b77-17350fb878c7", "message": "The response is not in a JSON format.", "innerError": "Cannot read server response." }}, clientRequestId: bf53866f-0f29-4393-9b77-17350fb878c7
If I enter an incorrect GUID the connector returns a 'Document NotFound' error as expected - although the full error does not seem right:-
"statusCode": "notFound",
Hi Peter,
First part #2 with incorrect GUID... you probably have provided a malformed GUID (i.e. one with missing character, or extra characters) so Flow treats it as path to a document and not a GUID, hence the error.
To test with correct GUID please do this:
1. Create a Find document action and manually navigate to THAT document (there is a picker control on the right of the input field. Sometimes it takes a few seconds for Flow to load it, so be patient!). This will fill in the path. Does it work?
2. If step #1 works, then add second Find by GUID and use document GUID variable from #1. Does it work?
I'm having a similar issue with the Fetch documents by saved search. Works fine when the search returns nothing but when the search returns a dociment(s) I get the same error. The error message seems to indicate that the response from the server is not valid json.
We have noticed that in some situations saved search fails when document attributes are requested. The work around for this problem is to select no environment in Find documents by Saved Search. The action will return documents but without environment attributes. If you need attributes, you can use Find Document by path or GUID action for each single document.
It is a known issue and will be fixed in future versions of ProjectWise/WSG.