This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
I'm populating a drop-down list with files in a dropbox folder, from there I can process whichever has been chosen. It works great, but it doesn't work when I push it to the gallery. It seems the drop down in the gallery is only populated with whatever was in that dropbox folder when the workflow was saved to the server gallery?
I hope this makes sense:
Open dropbox directory
Dynamic open will open the contents of the file
I create 2 columns (Name, Value) - formula block left of the cross tab.
Cross tab and put into the drop down
Drop down should now have a list of file names
I then join that up later with the content to select the correct content
As an analytic app it works great, if I add a new file into dropbox and run the workflow I see it in the drop down. But when I run it from the server I never see the drop down update?
@StephenMack When your dropdown uses the "fields from connected tool", it is unfortunately stale in my experience. It saves that info in the xml and updates it whenever it's run as a workflow (but not when it's run as an app or run in the gallery). A semi-workaround would be to have your app save the name value pairs to a file and read that file into the dropdown using the external source option instead of fields from connected tool. The deal breaker here would be that you're always one run behind. So if you add a file to your dropbox, you would have to run your app once (and it wouldn't have the new file displayed) and then the second time you run it you would have the desired effect.
Not sure how similar something I do is, but here it is anyway in case it helps.....
I have an app that displays a tree list to the user that they can pick various options from. Only problem is that tree list is specific to the user. And can change at any moment (a user's list might have 5 options now, and 10 options 5 minutes from now, and another user will have a totally different list).
To accomplish this "dynamic" tree list based on user, I invoke the chained app functionality.
When the user logs into the app, they see a description of what the app does and a "NEXT" button. When they click the NEXT button, what's actually happening is it's capturing who that user is, and creating, on they fly, their own special list to display. When that is done, it immediately jumps into the app that's chained to it, which now pulls in that list that was just created right then and there. It's seamless to the user, they think it's all the same app.
If this sounds similar to what you need, let me know and I can give you more details.