Hi, I use the smart node "Query database". Someone has try t

I don't believe you will be able to dynamically define the selection fields with the Query Database node. You can either pull back all columns you would need in each query, or run multiple Query DB nodes as you are now. Another alternative would be to use the Execute Stored Procedure node - create a procedure in SQL that allows you to send column name as an input, for use in a dynamic query there.

Ok, thank you for your feed back.

any particular reason you can't use a!queryEntity?

Try using a!queryEntity function to achieve what you are looking for.You can create rule inputs for the coloumns that you want to fetch.Query Db smartservice also degrades the performance of the application.As a best practice try using a!queryEntity functon.

I can't use QueryEntity because i need to request several tables with 1..n relationship. It will be implemented as nested mulitiples in Appian, but it's not recomanded due to performance issues and a!QueryEntity does not support request on nested multiple field.

If you want to fetch datas from multiple tables you can create view and fetch the same using a!QueryEntity function.

Hi Victor, you could also use a stored proceudure to achieve this.

Hi Fabien, yes i could do that but with this solution a part of the business rules isn't stored in Appian. Thanks anyway

@victorb what design / solution approach you followed to implement the above usecase. If you can share your thoughts ...