Bring your best ideas to the AI Use Case Contest! Enter to win 40 hours of expert engineering support and bring your vision to life using the powerful combination of Alteryx + AI. Learn more now, or go straight to the submission form.
Start Free Trial

Alteryx Server Discussions

Find answers, ask questions, and share expertise about Alteryx Server.

Chain app not updating correctly

adrilarotta
8 - Asteroid

So I have this issue with chain apps, I have asked to Alteryx Consultants and they have not been able to solve it and I can't believe this does not have a solution.

 

The first app takes the inputs, and as a result two alteryx data bases are obtained, one feeds a dropdown list tool where the user can select the city/municipality for which the income tax will be calculated and the other output is the input for the second app which contains the actuall data with the value of the tax. I am doing tests with two different sets of data (both of them with the same schema).

 

When the workflow is run with the first set of data (the same uploaded in designer as input) it works fine, but then when I upload the second set of data it works just for the first municipality I select, if I re-run and select a different municipality or even the same one I selected at first, the result obtained correspond to the first set of data not the second.

 

If I change the data in designer to the second set of data it will occur the same, the workflow will run without any problem for the second set and if I select the first set I will obtain correctly just the result for one municipality and the others will correspond to the second set of data.

 

One particularity is that the dropdown list update correctly, the problem is with the input file for the second application apparently. In designer it works perfectly, also I already have gone through the change of the paths to relatives...

 

I appreciate your help to check once more and identify where the inconsistency is.

10 REPLIES 10
trampai
6 - Meteoroid

Hi everyone has anyone found the solution this? This bug still persists on Version: 2023.1.1.336.