9 articles about Files and images, in reading order.
Parsware Platform
A File field holds a document and an Image field holds a picture, each belonging to one record. Add one to a table, attach a file on the form, and see what Save, the size cap and the record's permissions do with it.
Parsware Platform
A file too big for the environment's database is moved to object storage on its own. The form, Download and who may read it all stay the same, and deleting the record deletes the file.
Parsware Platform
Choose one field as a table's record image and one as its secondary text, and every list and lookup shows a picture and a second line beside each record's name. Two contacts with the same name stop looking the same.
Parsware Platform
A server-side script can write a file to storage and read it back, and it can put a file into one record's File field. They're two different places for two different kinds of file. We exported expense claims as a CSV into a bucket, then attached a receipt to one claim and found it on the claim's form.
Parsware Platform
An image picker on the Contact screen holds the photo somebody chose, and a Save photo button stores it in the contact's Photo field with one updateRecord. The picker is the platform's own control, so it previews, it refuses a file that's too big, and the stored photo shows up beside the contact in every list.
Parsware Platform
At the end of the month, finance wants the expense claims as a CSV file it can fetch. A Custom API builds the file from the claims table and puts it in object storage, where it stays until somebody collects it. We called it from finance's own system and found the file in the Storage screen.
Parsware Platform
Everything a custom app does in Parsware goes through one object: who's using it, where it was opened, the data their role can read, saved queries, Custom APIs, object storage and the log. We grew the visitor board with company totals from a saved query, readable visit purposes, and a button that keeps today's list as a file.
Parsware Platform
A web resource is a file stored in a solution and served by the platform: a stylesheet, a script, an image, a page. We built the printable visitor badge as four of them, a page with its stylesheet, script and logo, and opened it at its address.
Parsware Platform
Apps and integrations keep their files in object storage: exports, uploads, documents too big for a record. Storage in the Admin Control Center shows every bucket, what is in it and how much room it takes, and clears out files nothing points at. We looked inside Northwind's finance bucket, uploaded an invoice into one of its folders, and previewed a sweep.
