Classic file types are no longer available for use as of January 2021. You can transition your classic files or download a PDF. Learn More

Unable to Migrate query result to different workspace through chains

Answered

Comments

8 comments

  • Wayne Paffhausen

    Hi A,

    Unfortunately nothing you have provided demonstrates an error.  The actual error information will be displayed after what you have provided.  The text information you have provided above is the command configuration; which provides some basic information on the inputs the command was provided.

    Looking at the basic inputs you have provided it appears to be OK at the first glance.  You will need to provide complete details of the overwrite sheet data command.

    Thank you!

    0
  • Tony Scalese

    It looks like the spreadsheet ID that you configured the Command to use is not valid.  Make sure you are using a Connection that has access to the Spreadsheet in the current Workspace.  

    0
  • Eric Braun

    I can confirm that we walked through the Chain and the Overwrite Sheet Data command has the correct spreadsheet ID and sheet ID. Additionally, we confirmed that the user associated with the OAuth2 grant and connection has access to both workspaces and the spreadsheet where we are writing the query output. Also, what was pasted above was the entire text in LOGS, there is nothing displayed after.

    0
  • Tony Scalese

    I want to confirm a few things.  This Chain is being used to pull query results from one Workspace and load them to a spreadsheet in another Workspace.  Is that correct?

    If so, please provide screenshots of the Download Query Results and Overwrite Sheet Data Command configurations.  Full screenshots of both please.

    0
  • Eric Braun

    That is correct. We have a query in an SEC workspace and want to push the query output to a spreadsheet in a Management Reporting workspace.  Please see screenshots of Download Query Results and Overwrite Sheet Data command configurations below:

     

    Customer has tried running with "Use Async" and without as well as using the cloudrunner instead of the groundrunner you see now above.

    0
  • Tony Scalese

    You're using the same Connection (Chains Connector External Reporting) across both Commands.  A Connection has a 1:1 relationship with the Workspace in terms of OAuth grants.  I think you need to use a different Connection in the Overwrite Sheet Data Command.  

    0
  • Eric Braun

    Twofold follow up, we have an OAuth2 grant in the Management Reporting workspace but it does not show up as an available connection (two images below):

     

    Additionally, in the connection itself we have selected the workspaces where the connection can be used, am I thinking of this wrong?

    0
  • Tony Scalese

    Let's break this down.  You have two Workiva Connections to correspond to the Wdesk Workspaces:

    • External Reporting
    • Management Reporting

    Your use case is that you want to extract data from the External Reporting Workspace and load to the Management Reporting Workspace.  To do this, both Connections need to be enabled for at least one of the Chains Workspaces.  Let's assume that you built this Chain in the External Reporting Workspace.  In that case, then you would enable both Workiva Connections for the Chains External Reporting Workspace.  

    0

Please sign in to leave a comment.