When using the action "Upload file" this would be really helpful to be able to store the name of the uploaded file in a variable (or a range) for further manipulation (launch and etl job for instance)
ADMIN RESPONSE
Dec 18, 2020
Hi Pierre. This is a good idea. While we cannot commit to a specific target version, we will consider adding it to our future internal backlog. If you can add further information about the context / use case of this feature, please add it here.
thank you for the reply. This functionality is mainly used from users which should not be able to access the report designer. Usually, the upload of a file includes an on-demand action which results in the further usage of the file and it's data points. Without the information of the uploaded file location, you can't proceed with an integrated frontend workflow. Since you need to store the name any way it should be easy to integrate this into the return function.
-> The function is not really useful without this functionality.
The only option to use the file is typing the name of the file into a field and take it from there. But this will lead to false user inputs and potential failure of the process + it is not automated.
The implementation of this task is a good idea, but without this return not really useful for end-user purposes.
Hello Jedox Team,
thank you for the reply.
This functionality is mainly used from users which should not be able to access the report designer.
Usually, the upload of a file includes an on-demand action which results in the further usage of the file and it's data points. Without the information of the uploaded file location, you can't proceed with an integrated frontend workflow.
Since you need to store the name any way it should be easy to integrate this into the return function.
-> The function is not really useful without this functionality.
The only option to use the file is typing the name of the file into a field and take it from there. But this will lead to false user inputs and potential failure of the process + it is not automated.
The implementation of this task is a good idea, but without this return not really useful for end-user purposes.
Thank you!