Chain to validate Connection IDs?
BeantwoordIs there a quick and easy way to automate a check to confirm that a Connection ID is valid and/or accessible by the executor of a chain?
We currently have multiple control sheets that list Connection IDs and are used to trigger refreshes across multiple spreadsheets and multiple workspaces. While the process works quite well, we occasionally have failures that typically fall into two main categories.
1. The connection ID has changed since the last time it was executed and we missed updating the control sheet
2. A new connection was added, however we missed granting access to the automation ID that executes the scheduled chains
While the fix is pretty straightforward, it requires us to execute the chains and trigger a failure, to identify the point of correction.
Ideally, I'd like to execute a chain that simply confirms if the connection ID is valid, without executing it, and provides a list of all issues.
This would allow a more proactive approach to issue identification, without the impact of a failed execution.
-
Perhaps you could use List connections to return all valid connections from the target sheets in question, or, if that doesn't work, try the Get connection details endpoint?
I'm not sure about an approach for checking on permissions, however.
0
Hi Erik Tremblay,
Andrew's suggestion of getting the list of connections and checking if a particular Connection ID is found in the list would be a good way to make sure the Connection ID still exists. A Connection ID won't change. However, if the connection is deleted and then reestablished, the new connection will have a new unique Connection ID.
You could verify part of the permissions for a Connected Sheet. In order for the Chain to refresh a connection, the Username associated to the Workiva Connector must be at least an Editor or higher for the particular Connected Sheet. You can use the Prototype Platform Spreadsheet API endpoint Retrieve Permissions for a Sheet in a Spreadsheet to get a list of permissions for the given Sheet. Then verify that the user has adequate permissions based on the results. This API endpoint requires that the user has explicit permissions for the Connected Sheet and not just inherited permissions to the Sheet. Additionally, at this time, this is a prototype API endpoint and is subject to change or removal without warning.
Assuming that the Connected Sheet is connected to a Wdata Query, the user will also need access to the query to run it. There is not an API endpoint at this time to verify permissions of this side of the connection.
0
Thanks for the suggestions Andrew and Jeff, really appreciate it.
The List Connections approach is something we've considered, however with the connections spanning multiple spreadsheets, it ultimately became more overhead than addressing the occasional failure points. With the List Connections approach, we equally need to identify all the spreadsheet IDs and parse the JSON files for each spreadsheet to produce the list for comparison.
That said, if you have any examples of successful chains pulling this off, I'd be very interested to see how you've configured them.
0
Our situation may be simpler than yours Erik Tremblay, but we simply have a chain that lists connections for the relevant spreadsheets and refreshes all of them. It doesn't discriminate among connections and hence refreshes whichever are used in each spreadsheet. And regarding permissions, we have a CloudRunner connection set up for a generic integration user we've created in Wdesk that we've granted sufficient permissions on each spreadsheet to.
0U moet u aanmelden om een opmerking te plaatsen.
Opmerkingen
4 opmerkingen