Forum Discussion
ShawnRenn2
8 years agoQrew Trainee
Hey Mel,
We seem to keep bumping into each other here!
In all honesty your best bet is to create a new table in the source app called documents, and relate it back to whichever table you currently have your single file attachment field on.
Any time you could have an unknown number of data points related to a "record", it's almost always a queue to make a related table for it.
This solves two problems, first being the flexibility of attaching any number of pictures, (and any other supporting details that really should be unique to the document like description, location, date, etc.) and the issue you're having where these images become useless in the linked application.
Since the related files would be individual records, each would have a unique link to the image, which also allows you to take another step an display a thumbnail of that image in report view if that would be of use to you. Imagine opening a "project" (or whatever the core table is these images are captured on now) and instead of opening each attachment in a seperate browser window, you could click the "Full Report" link and see all the images at once!
Hope that helps!
MelissaDoran
8 years agoQrew Cadet
The data is coming in from an external app, ie not a quickbase app, through Zapier.
Is there a way to format the incoming chunk of data to split into three (or however many photos there are) fields?
Is there a way to format the incoming chunk of data to split into three (or however many photos there are) fields?