Closed TMoffat closed 1 year 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
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
Hi @TMoffat I've had a look at this and based on my understanding, the API is returning what it should do.
The property manager on the property is set to Samantha Stockwell, and the propertyManagerId coming back from GET /properties/FSA230109 is FSST
Calling the negotiators API at GET /negotiators/FSST is Samantha Stockwell.
The primary negotiator (key contact) on the property however is Sarah Twigg, which is reflected in the negotiatorIds collection returned from GET /properties/FSA230109 - could it therefore be that your import system is not reading the propertyManagerId field?
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
I believe this might have been a case where Samantha had the wrong negotiator ID as these were not being pulled in initially.
There are an additional number of properties which I think may be affected by the same thing.
I have attached the list here. Could you let me know what negotiatorID the system is looking for. I can then raise this with our dev team incase they're looking at the wrong thing.
May thanks for your help.
On Thu, 9 Nov 2023 at 18:36, github-actions[bot] @.***> wrote:
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 https://foundations-documentation.reapit.cloud/dev-requests
— Reply to this email directly, view it on GitHub https://github.com/reapit/foundations/issues/10108#issuecomment-1804356355, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4HB3EZLHYTYEIU3JJYZQLLYDUPETAVCNFSM6AAAAAA7EHUJ3CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBUGM2TMMZVGU . You are receiving this because you were mentioned.Message ID: @.***>
Please ignore the previous file. Here is the updated list.
On Fri, 10 Nov 2023 at 09:08, Thomas Moffat @.***> wrote:
I believe this might have been a case where Samantha had the wrong negotiator ID as these were not being pulled in initially.
There are an additional number of properties which I think may be affected by the same thing.
I have attached the list here. Could you let me know what negotiatorID the system is looking for. I can then raise this with our dev team incase they're looking at the wrong thing.
May thanks for your help.
On Thu, 9 Nov 2023 at 18:36, github-actions[bot] @.***> wrote:
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 https://foundations-documentation.reapit.cloud/dev-requests
— Reply to this email directly, view it on GitHub https://github.com/reapit/foundations/issues/10108#issuecomment-1804356355, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4HB3EZLHYTYEIU3JJYZQLLYDUPETAVCNFSM6AAAAAA7EHUJ3CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBUGM2TMMZVGU . You are receiving this because you were mentioned.Message ID: @.***>
Hi @TMoffat if you are trying to send me a file, please can you email it to sinfo@reapitfoundations.zendesk.com with it 10108 in the subject.
Hi Pete,
How was your weekend?
Of course. Apologies, I should have asked.
Thanks!
On Mon, 13 Nov 2023 at 12:59, Pete Littlewood @.***> wrote:
Hi @TMoffat https://github.com/TMoffat if you are trying to send me a file, please can you email it to @.*** with it 10108 in the subject.
— Reply to this email directly, view it on GitHub https://github.com/reapit/foundations/issues/10108#issuecomment-1808119166, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4HB3EYUI72E63H5DDKQGLTYEIKR7AVCNFSM6AAAAAA7EHUJ3CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBYGEYTSMJWGY . You are receiving this because you were mentioned.Message ID: @.***>
Back with third party via zendesk
Hi Pete,
Apologies for the delay in response.
I really appreciate your help and have gone back to the client. Please consider this closed. Your investigation has really helped.
Have a great week.
Kind regards, Tom
On Wed, 15 Nov 2023 at 13:00, Pete Littlewood @.***> wrote:
Back with third party via zendesk
— Reply to this email directly, view it on GitHub https://github.com/reapit/foundations/issues/10108#issuecomment-1812498634, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4HB3E4RVJXBTCTXQKUZCTLYES4H3AVCNFSM6AAAAAA7EHUJ3CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJSGQ4TQNRTGQ . You are receiving this because you were mentioned.Message ID: @.***>
Great news thanks for confirming Tom
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
Describe the bug Our joint client Frosts PM are having issues with Agent Assignments not appearing.
We currently sync the Property Manager in Reapit as the Assigned Agent in Fixflo. In a number of cases it is the key contact being pulled through.
Property FSA230109 showing as Sarah Twigg, which is should be Samanth, shown below.
Screenshot deleted
Many thanks in advance.
Specification