BYM - Withdrawn Date from Properties

[SLawrie2]

Hi Reapit,

Is your feature request related to a problem? Please describe.
A number of our mutual clients are looking to target marketing based on the date a property was Withdrawn. We understand that we already have Withdrawn status but our system cannot automatically trigger an email based on a status, it would rely on a date of an event. We are also aware of this field currently being in a journal entry, but we are struggling to work with journal entries due to the lack of ids on each - something we raised here #3256.

Describe the solution you'd like
We would like a withdrawn date field on the property model.

Describe alternatives you've considered
We would like ids on journal entries.

Thanks,
Sidonie

[github-actions]

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]

Hi Sidonie

Unfortunately this isn't something we can introduce at present due to the way the data is stored in our system. The way to get this information is like you have suggested to query the journalEntries API. You could choose to store the withdrawal date in your own system against a property, if desired. I will open a feature request to see if we can store this against the property, however I can't guarantee that it will be implemented.

Thanks
Pete

[github-actions]

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]

Internal ref PBI-5509

[SLawrie2]

Hi Pete, Thank you for your response on our request. Would you please be able to look at the older development request I highlighted in that ticket about journal entries so we can use them? Copied the ticket link here for ease #3256 Thanks, Sidonie Lawrie Head of Product • nurtur.tech T 0344 800 8424 E ***@***.*** W nurtur.tech<https://www.nurtur.tech> A 121 Park Lane, Mayfair, London W1K 7AG [img]<https://www.nurtur.tech/> nurtur.group Limited, company registration number 09210707, registered in England and Wales, registered office 121 Park Lane London W1K 7AG. All rights reserved, intended for the recipient only and not for further distribution without the consent of nurtur.group Limited. [img]<https://www.nurtur.group/> From: Pete Littlewood ***@***.***> Sent: Thursday, April 18, 2024 2:50 PM To: reapit/foundations ***@***.***> Cc: Sidonie Lawrie ***@***.***>; Author ***@***.***> Subject: Re: [reapit/foundations] BYM - Withdrawn Date from Properties (Issue #11013) Caution: This message comes from an external organisation. Please take care when clicking links or opening attachments. Hi Sidonie Unfortunately this isn't something we can introduce at present due to the way the data is stored in our system. The way to get this information is like you have suggested to query the journalEntries API. You could choose to store the withdrawal date in your own system against a property, if desired. I will open a feature request to see if we can store this against the property, however I can't guarantee that it will be implemented. Thanks Pete — Reply to this email directly, view it on GitHub<#11013 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BHG57SBSYDMY5OWCYVK7WN3Y57FQZAVCNFSM6AAAAABGCTX5O6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRTHEYTKMJYGA>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[plittlewood-rpt]

Hi @SLawrie2 that one is still with our internal product team I'm afraid and is unlikely to change in the short term. I'm not sure I understand why you can't use the journal entries API as it is. Are you able to elaborate? Journal entries do not change once they are written so I'm not completely sure I follow why you are finding it difficult to use them. Thanks

[SLawrie2]

Hi Pete, Because journal entries don’t have ids then it is difficult for us to match them correctly - especially if they have previously come through and we need to match it to a previous entry. Thanks, Sidonie Lawrie Head of Product • nurtur.tech T 0344 800 8424 E ***@***.*** W nurtur.tech<https://www.nurtur.tech> A 121 Park Lane, Mayfair, London W1K 7AG [img]<https://www.nurtur.tech/> nurtur.group Limited, company registration number 09210707, registered in England and Wales, registered office 121 Park Lane London W1K 7AG. All rights reserved, intended for the recipient only and not for further distribution without the consent of nurtur.group Limited. [img]<https://www.nurtur.group/> From: Pete Littlewood ***@***.***> Sent: Wednesday, May 1, 2024 8:30 PM To: reapit/foundations ***@***.***> Cc: Sidonie Lawrie ***@***.***>; Mention ***@***.***> Subject: Re: [reapit/foundations] BYM - Withdrawn Date from Properties (Issue #11013) Caution: This message comes from an external organisation. Please take care when clicking links or opening attachments. Hi @SLawrie2<https://github.com/SLawrie2> that one is still with our internal product team I'm afraid and is unlikely to change in the short term. I'm not sure I understand why you can't use the journal entries API as it is. Are you able to elaborate? Journal entries do not change once they are written so I'm not completely sure I follow why you are finding it difficult to use them. Thanks — Reply to this email directly, view it on GitHub<#11013 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BHG57SDQP3NBJ2YCKSQOIOLZAE7DJAVCNFSM6AAAAABGCTX5O6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBYHE4DAMBWG4>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>