Understanding how to handle write status partial success is crucial for ensuring that your data is correctly written to the PMS.

Understanding the Propexo API: Partial Success Scenarios (Part 3)

Hi, I’m Nick, co-founder and CTO at Propexo. This is the final part of our three-part series on write requests. After covering successful and failed requests, let’s explore partial success scenarios.

Complex Write Operations

In this example, we’ll demonstrate a more complex operation: creating a resident in Rent Manager while simultaneously adding an attachment to their profile.

The Request Structure

Our request includes:

1. Basic resident creation data
2. An attachment to be associated with the resident

Understanding Partial Success

When we send this request, we receive the standard 200 OK response with our job ID. However, checking the write status reveals a “partial success” response.

Why Partial Success Occurs

This outcome occurs because many PMS (Property Management System) APIs require split requests to different endpoints. In our case:

• Propexo allows you to combine resident creation and attachment addition in a single request
• Rent Manager requires these to be separate operations

The Result Breakdown

In our demonstration:

• The resident creation (Jerry Seinfeld) succeeded
• The attachment creation failed due to an ID mismatch

Note: The ID mismatch error was expected in this demo since we used fictional IDs. This error comes directly from Rent Manager, not Propexo.

Handling Partial Success

When encountering partial success scenarios, you’ll need to:

1. Identify which portions of the request succeeded
2. Review the error messages for failed portions
3. Decide whether to retry failed operations
4. Determine how to handle the partially completed state

This information allows you to make informed decisions about how to proceed, such as whether to attempt reattaching the document at a later time.

Key Takeaway

Partial success scenarios are common when working with complex PMS integrations. Understanding how to interpret and handle these cases is crucial for maintaining data consistency and ensuring successful integrations.