Customer unable to see document uploaded via api

[iWader]

Describe the bug

We've uploaded a document to the tenancy, however the customer is unable to see this document in RPS

Document looks to have uploaded all correctly. We can retrieve this document both via the id and searching documents for the relevant tenancy.

Property TIL120043
Appointment TIL1700041
Tenancy TAL160016
Document RPT24016820

To Reproduce

1. POST /documents/signedUrl
2. POST <signedUrl>
3. POST /documents with below payload

{
    "associatedType": "tenancy",
    "associatedId": "TAL160016",
    "typeId": "FPI",
    "name": "Property Inspection on 2024-06-01.pdf",
    "fileUrl": "<signedUrl>"
}

Expected behaviour

Customer can see the document when viewing property/tenancy letters

Additional context

Ashley asked us to file this issue and suggested is possibly related to the users office groups.

[github-actions]

Thank you for taking the time to report a bug. We prioritise bugs depending on the severity and implications, so please ensure that you have provided as much information as possible. If you haven’t already, it really helps us to investigate the bug you have reported if you provide ‘Steps to Replicate’ and any associated screenshots.
Please ensure any personal information from the production database is obscured when submitting screenshots.
This issue will be reviewed in our weekly refinement sessions and assigned to a specific project board. We may also update the ticket to request additional information, if required.
For more information on our processes, please click here

[plittlewood-rpt]

Hi @iWader can you confirm the customer please? Thanks

[iWader]

It's Parkers Properties

[plittlewood-rpt]

Thanks. I can see this document fine against the tenancy, which is what you're attaching to (slight difference in the filename but assuming that's expected)

Please can you confirm what the customer is expecting so we can try to work backwards?

[iWader]

Different document name is expected, mine was just a sample payload. Confirmed that the timestamp of 2024-06-10T17:04:14 from our logs matches up with timestamp in your screenshot.

We've requested further examples from the customer.

[plittlewood-rpt]

Thanks very much. I have a hunch that they might be expecting to be able to see this either in the property letters section (which won't happen because the document is attached to the tenancy), or possibly they're expecting it to be attached to the inspectionn appointment. If the latter, you need to PATCH the respective appointment, setting the documents properties respectively eg:

PATCH /appointments/{id}
{
   "documents": {
       "finalPropertyInspectionReportId": "ABC1234567"
   }
}

ABC1234567 would be your document id, so RPT24016820 in your above example. This will cause AgencyCloud to link the appointment to the document:

This is a fairly new feature so it might be that you're not aware of it. There's also the facility to upload a draft report, please refer to the Swagger spec for PATCH /appointments/{id} for more details

[github-actions]

We have recently requested additional information relating to the issue you have raised. Please can you take the time to review this ticket and where applicable, provide the information requested.
For more information on our processes, please click here

[iWader]

We should already be updating the documents on the appointment, from our logs I see we attempted to do this. I have added more detailed logging to confirm the api responds as expected.

Waiting on further examples and details from the customer.

[iWader]

Have received no further updates on my side for this, so assume the issue the customer was facing is resolved.

[github-actions]

It looks like you have commented on a closed issue. If your comment relates to a bug or feature request, please open a new issue, and include this issue number/url for reference.
For more information on our processes, please click here