Support pPrice, pMinPrice and pMaxPrice through the API

[rformato]

I'm writing an integration procedure and we used to query the pPrice, pMinPrice and pMaxPrice fields.

At the moment the API just exposed price and priceTo.

I was told in a previous interaction the following:

Min Price and Max Price for non development properties, relates to matching criteria which isn't currently exposed via the Properties API.

Would it be possible to expose those fields?

Thanks

Specification

• Project: Reapit.Services.Properties
• Review internal ref PBI-4745 and linked development items to understand the changes so we can correctly apply them to the API. Ensure multi currency is considered here too. This change is going into 12.186 which is only just starting beta so it'll be a while before this field is available everywhere
• Add new matchPriceFrom and matchPriceTo properties to PropertySellingModel. These should surface prp.minPrice and prp.maxPrice respectively
• Alter PropertySellingModel.PriceTo to map from prp.toPrice (this is a new field)
• Also support writing of these values via POST/PATCH as appropriate
• We will also need to review the filtering that takes place when the priceFrom/priceTo parameters are used as the upper bound will currently be using the prp.maxprice field
• Look at introducing a filterbuilder if not already present to separate out the filtering logic from the main repository classes

[github-actions[bot]]

Thank you for raising a feature request. Feature requests will be prioritised in accordance with our roadmap, customer and developer priorities. This request will be reviewed in our weekly refinement sessions and assigned to a specific project board or column, depending on the nature of the request and the development work required. For more information on our processes, please click here

[plittlewood-rpt]

Likely we should add a matching range to the selling/letting objects here. There is a ticket in the AC backlog for moving the match ranges to separate fields so they don't conflict with the marketing price. We should confirm if this is happening and wait if it is.

[plittlewood-rpt]

Internal ticket: PBI-4745

[MarcinuB]

Hi @plittlewood-rpt @HollyJoyPhillips .

Do you have any idea of the timeline for that one? We're interested to use pMinPrice and pMaxPrice for Michael Graham customer.

Thanks

[HollyJoyPhillips]

Hi @MarcinuB We can't currently provide a timeframe as it's under refinement with our desktop team. We can't expose these fields via the Platform if the underlying data structure is likely to change. As soon as we have more information/delivery time we'll update this ticket.

[HollyJoyPhillips]

AC development has been completed - see internal ticket AC-11420. Platform team to review data structure

[plittlewood-rpt]

This change is going into 12.186 so it'll be a while before we can push it out into the API. We can however get the changes prepped and into PR ready to merge

[github-actions[bot]]

This issue has been updated and moved to our ‘Near Term’ column (typically completed within 0 - 4 months). We have assessed the effort required and outlined a technical specification - please take the time to review this detail. When we're ready to schedule the issue, it will be assigned to the relevant board where you can continue to track its progress to completion. For more information on our processes, please click here