Hello everyone. I am strugling with a large conceptual problem in Alteryx that I am hoping the community can help explain better to put my mind at ease :-)
Lets say I build a chained application for the following scenario.. A user needs to select a single client from a list of clients in a database, and then a query against the database needs to return a list of loan numbers for that client. Once again the user selects the loan he wants to look at and the workflow does its work.
I could accomplish this by having the first workflow return a dropdown box for all of the clients from the database. I could then write whatever client they choose to a alteryx file (YXDB) and have workflow #1 call a second workflow that would use that YXDB file to provide a secondary drop down selector.
Isn't concurrency a problem here
My concern is as follows. If I make this an analytic app and user A kicks off the workflow it will create the YXDB file... Say use B then kicks off the workflow before user A's app could read from the YXDB file... Wouldn't user B'd workflow then overwrite the YXDB file and user A's workflow results be corrupted?
Would this only happen if you hardcoded the YXDB file onto a network path (or C drive on the server) and alterYX base has a work around for this if you don't hardcode these results somewhere?
I would just like some more color around this problem if at all possible; as it is a major mental roadblocker for me being able to use linked applications in general in AlterYX. (I have looked but haven't bound any documentation that specifically addresses this concern, but if I missed it please just let me know!)
As always thanks everyone, this community is incredibly helpful!