Skip to main content

How can I manually add, edit and ensure the visibility of task photos in reports on Uptick?

Elyce Smith avatar
Written by Elyce Smith
Updated over 2 weeks ago

How to manually add, edit and ensure the Visibility of Task Photos in Reports on Uptick

Uptick offers specific instructions and requirements to successfully add and display asset photos in service and call-out reports. This guide outlines the steps to correctly upload, name, and manage photo files to ensure they appear as intended.

Overview

Ensuring task photos are displayed in reports involves adhering to folder naming conventions, file format standards, and correct uploading workflows. Following these guidelines will minimize errors and ensure a seamless report generation process.

Importance of Folder Naming and File Format Conventions

To successfully display uploaded photos in reports, the following conventions must be observed:

  • Folder Name: Asset photos must be stored in a folder named "attachments" using all lowercase characters and no extra spaces or date stamps in the folder title.

  • File Format: Accepted file extensions for images are .jpg or .jpeg in lowercase. If the current file extensions are uppercase (e.g., .JPG), rename them to lowercase.

Adhering to these conventions ensures smooth integration of photos into both service and call-out reports.

Step-by-Step Guide to Add Task Photos

Follow these steps to add task photos to your reports:

Using the Desktop Interface

  1. View the task you wish to add photos to

  2. Navigate to the Documents tab in the top right corner

  3. Click on the folder named 'attachments'

  4. Select 'Upload Files to Folder'

Using the Mobile App

  1. Navigate to the task details page

  2. Click on documents

  3. Upload the photos to the folder names 'attachments'

  4. Click the '+' sign and upload photos

General Troubleshooting Steps

If your uploaded photos still do not appear in the generated report:

  1. Verify that the photo folder is named correctly as "attachments" in lowercase.

  2. Recheck the image file extensions to ensure they are lowercase (.jpg or .jpeg).

  3. Regenerate the report after making the necessary changes.

FAQs

  • What are the implications of incorrect folder names or file formats? Photos may fail to display in the service or call-out report if these conventions are not followed. Always double-check the naming and formatting before uploading.

  • Can I upload photos directly from other devices? To upload photos from another mobile device, the task must be opened in the new device and then the user will be able to navigate to the photos tab. Similarly for desk users they need to view the task and then follow the steps above.

  • What happens if my technician uploads asset remark photos to the wrong place?

    If this occurs, you will need to download the photos from the incorrect spot, delete them and upload them to the correct remark/asset.

    Note: Ensure you've downloaded the photos before deleting as Uptick cannot recover this information once deleted.
    ​

  • Why are my remark photos missing from the task?

    It is likely the photos have been uploaded to the incorrect place or asset. Ensure the photographs are linked to the remarks on the work tab/service tasks.

    If the photo are not attached to the remark against the correct asset, obtain the photos (if they are on the incorrect asset or remark refer to steps above) then upload to the remark.

    If they are there and still not displaying, please contact our support desk for further assistance.

  • How do I then get the photos onto my report?

    Ensure the correct photos are attached to the correct asset's remarks, and they should appear on your report if you are using a default reporting template.

Related Topics

  • Managing Asset Records in Uptick

  • Generating Call-Out Reports with Visual Documentation

  • Troubleshooting Report Visibility Issues

By following this guide, you can ensure the visibility of your asset photos in Uptick's service and call-out reports, minimizing errors and enhancing the professionalism of your documentation.

Did this answer your question?