In-Database Chained Apps

[Xeu911]

Hi everyone,

I've been looking but couldn't find an answer. I'm basically trying to build a chained app (I've already done it using In Memory tools) using in DB tools.

My use case is quite simple :

1. A connect in DB tool containing a select statement in sql oracle
2. A 1st filter in DB tool on which I'm connecting the 1st text box (The user need to enter a period format YYYYMM)
3. A 2nd filter in DB tool on which there is the 2nd text box (This time the user enter a product code)

Is there any way I could build a chained app while keeping the in db tools ?

I would appreciate any help on this.

Thanks!

Clément

[davidskaife]

Hi @Xeu911 

I'm no expert on the In-DB tools, but in theory what you're suggesting is possible i think - the main issue would be persisting the data output from the first filter so its available for the second filter/second app.

I'd say you'd need to write the data from the first filter/app to a table within the database, and then have the second filter/app pick up the data from that table and perform the next steps. Maybe one to trial and see how it goes.

Of course, someone else far cleverer than me may come along with a different suggestion or even say its not possible!

[alexnajm]

I don’t see why not - @davidskaife @is spot on, the question will be where will the drop down values live once the first app is run

[Xeu911]

Thanks for your swift reply! I've done what you suggested and it works indeed.
The only remaining issue is I don't know how to update the list of available values within the list tool : I'd like once my period is filtered on step 1, to display only available values from the DB.

[davidskaife]

Would you not need to pull this from the filtered table created in app 1?

[Xeu911]

Let me explain with screenshots : 

Here is my 2nd app, in which I select the values from the table created in step 1. 
How can I get the data from my table within the drop down tool ?

I tried to configure the tool using the external source option and make a "select *" statement. However I get an error when running the app :

[alexnajm · Accepted solution]

So the second table you created has two columns - NAME and VALUE - as the error indicates?

If it continues to error, I might just Data Stream out to a .yxdb and reference that with a relative path instead

[apathetichell]

@alexnajm is correct -- you'd need to use the datastream out --- create the .yxdb and then send that into app 2. Note --- when I build these - I do not use the filters directly on in-db tools. I use:

app 1: create list of potential filter values (usually using summarize in-db or group by in my sql) --- datastream out/output data

2.text input, filters from app interface --> append fields/summarize/whatever to build my query as text -> dynamic input in db/ etc.

[Xeu911]

Thanks all of you for your replies. Noted, I'll use the data stream out and the yxdb file. I was trying to avoid it at first because I have a lot of data (couple million of rows).

Thanks!

[alexnajm]

You should not need to data stream out millions of records - do another branch, summarize in-db on product code, THEN data stream out