Automate

Hi Community, 

I have a use case to cross link scripts to run a Transaction script first to upload data and then run a Query script to download the data. 

According to this article here this is possible in Studio 20.1 which is the version we have;
https://docs.winshuttle.com/studio-en-20-1-online-help-studio-with-evolve-studio-manager/cross-link-scripts.htm?TocPath=Studio%2020.1%20Online%20Help%7CQuery%7CRun%20Scripts%7C_____6

However when I go to chain my scripts together starting with my Transaction script, when the file explorer window opens to locate the next script file for the chain I only have the option of choosing a script file .txr for the transaction script, I don't have the option to choose a .qsq file type for a Query script. 

Yet if I were start with my Query script I have the option of adding either a Transaction .txr or Query script .qsq as the second script in the chain. 

To quote the Winshuttle article "Studio supports this script 'cross-linking,' enabling you to download and upload data (or upload and download data) in a single step."

Any help greatly appreciated. 


------------------------------
Ben
Woodside Energy Ltd
ben.crerar@woodside.com.au
------------------------------

Hi Ben

Cross-linking should work with Studio 12.1+ Connect and Studio Manager/Evolve 20.1+.

With a Connect license (am using 20.2), I can start with either Transaction or Query as the "base" script. 

With Evolve/Studio Manger, I can start with a Query and cross-link a Transaction, but not the other way around. 

The doc  doesn't specifically state you can't cross-link if you start with a Transaction script as the "base", except as it relates to the OOTB workflows.  Reading the doc, the details all start with Query, which is often the most requested use case.

 But I do know some people want to post & then query what was loaded to validate, to get defaulted values, or to prep for the next step in a process, i.e. create PO, create inbound delivery, etc.   

I'd suggest opening a Support ticket to request an improvement for starting with a Transaction as the base to chain with Query.  

Best Regards,
Sigrid


------------------------------
Sigrid Kok
PSE | Winshuttle NA
------------------------------

Thanks Sigrid

I have submitted a feature request #69719

It would be good to see this progressed ​as it seems a bit silly to restrict features based on the licencing. 

Thanks for your help.

------------------------------
Ben
Woodside Energy Ltd
ben.crerar@woodside.com.au
------------------------------

Original Message:
Sent: 02-17-2022 09:50
From: Sigrid Kok
Subject: Cross-link Scripts with Studio 20.1

Hi Ben

Cross-linking should work with Studio 12.1+ Connect and Studio Manager/Evolve 20.1+.

With a Connect license (am using 20.2), I can start with either Transaction or Query as the "base" script.

With Evolve/Studio Manger, I can start with a Query and cross-link a Transaction, but not the other way around.

The doc  doesn't specifically state you can't cross-link if you start with a Transaction script as the "base", except as it relates to the OOTB workflows.  Reading the doc, the details all start with Query, which is often the most requested use case.

 But I do know some people want to post & then query what was loaded to validate, to get defaulted values, or to prep for the next step in a process, i.e. create PO, create inbound delivery, etc.

I'd suggest opening a Support ticket to request an improvement for starting with a Transaction as the base to chain with Query.

Best Regards,
Sigrid


------------------------------
Sigrid Kok
PSE | Winshuttle NA
------------------------------