Another method is to use ‘If File Exists’ in server connect. Here, after performing the query, I use a repeat to check if there is a corresponding image for each record.
I don’t actually want to do anything based on the result, so I add a dummy step (there may be a better way to do this). I just want the result:
… to use in App Connect to control what’s displayed:
I understand that Teodor but in this case there is no image information in a database.
I know I said dynamic at the beginning of the post, the dynamic part is to do with the path like this
repository/{{report_type}}/{{report_number}}/overview.png
and
repository/{{report_type}}/{{report_number}}/signature.png
where each '/report_type/report_number/' should have an 'overview.png' and 'signature.png' uploaded for the final report.
In your view should I still be going down the Server Connect route to do a 'If File Exists'?
And do this even if there are 20 or so different images to be checked for on each report?
My case may be simpler. I just need to find if there is a related image which I know will be named {{id}}.jpg. If there is, I know additional images will be named {{id_2}} .jpg, {{id_3}}.jpg.
It might make things easier if the filenames were in a database. If the files are not stored in a database when they’re uploaded, you can populate a database table with filenames etc quite quickly. I have an example with about 12k images and it only takes 4-5 second to store the filenames, size and dimensions.