Chained Server app, how to output data to temp and input data from temp

[wonka1234]

Hi,

First part of chained app, I want to write to temp folder.

I use output data like this -

%temp%..\filename1.yxdb

but how to import this to my 2nd page of my chained app?

is it as simple as input data ?

%temp%..\filename1.yxdb

all users who access this on the server will have to be able to do this.

[jrgo]

assuming your chained app is saved in the same location as the initial app (not s sub-folder), you don't have to specify file paths. So our output would just be ".\filename1.yxdb" and you chained app would be configured to also read ".\filename1.yxdb".  it's also explained in the link below.

https://help.alteryx.com/20231/designer/app-building-guidelines#%25temp%25

[wonka1234]

@jrgo  even if Im exporting headers to another chained app? w here  should these headers file reside?

[jrgo]

Hi @wonka1234 

Sorry, not sure if I'm following... can you describe what type of output file the first app is generating and how it's intended to be used in the next app? If you're able to share screenshot or (preferably) desensitized copies of the apps, that would really help to fill in some of the gaps.

[Tam]

@wonka1234 I stumble across this, it might help from App Building Guidelines (alteryx.com)

%temp%
Do not use %temp% to write to the temp directory when you build workflows or apps to be saved to Server. Keep all file paths within the workflow. If you develop a chained app, use only the file name rather than any file path, for example, .\fileOutput.yxdb and not %temp%\fileOutput.yxdb or something similar. Select a file by browsing to it and then change the file dependency path to a relative path via the Workflow Dependencies window.

In previous chained apps that I've build, App1 writes a temp file : tempfile.yxdb (no path) App 2 in the chain input data tools or interface calls  tempfile.yxdb  (no path). 

HTH.