Open rajeshwl opened 2 months ago
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
Hi @rajeshwl I'll raise this with our service team. The data looks like it's come from a previous system and would have been imported 'as is'. In the meantime you can work around this yourself though by also using the modifiedTo parameter to essentially cap the query and ignore anything that's modified in the future
Internal support ref RSD-290471
As this issue relates to AgencyCloud, we are unable to process this through the Platform in accordance with our Developer Processes. Issues relating to AgencyCloud should not be submitted via the Foundations GitHub repo but should be raised via the Reapit Service Desk by a Reapit Customer. Please ask a Reapit Customer to raise this issue via the Reapit Service Desk. For more information on our processes, please click here
@plittlewood-rpt ,
Thanks for the details. We will use the modifiedTo param as well.
Regards, Rajesh
It looks like a data fix is due to be run in the next day or too to sort this so I guess weigh that up with any dev work you might need to do at your end for this workaround. Thanks
From: rajeshwl @.> Sent: Friday, June 14, 2024 6:41:08 AM To: reapit/foundations @.> Cc: Pete Littlewood @.>; Mention @.> Subject: [EXTERNAL] Re: [reapit/foundations] Property Certificates API Issue (Issue #11212)
External Message - Please be cautious when opening links or attachments in email
@plittlewood-rpthttps://github.com/plittlewood-rpt ,
Thanks for the details. We will use the modifiedTo param as well.
Regards, Rajesh
— Reply to this email directly, view it on GitHubhttps://github.com/reapit/foundations/issues/11212#issuecomment-2167250410, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHK7GIY3TDJ6TELGE6NIGULZHJ67JAVCNFSM6AAAAABJEKPGXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRXGI2TANBRGA. You are receiving this because you were mentioned.Message ID: @.***>
Describe the bug We are trying to pull the property certificate entries for our mutual client Johnshepherd - Lomond Group. We are using the following endpoint.
https://platform.reapit.cloud/properties/certificates
In this we are passing the modifiedFrom params to pull the updated records. But seems the records in your side has the modified date in future for most of the records(Nearly 20000+ records). The date's are like 11 March 3000, 20 March 2026, 10 May 3036. Can you please check this and update the records. So that the duplicate calls will be reduced.
Expected behaviour We are expected the records to have correct modified date according the record updated in the application.