Sale Data Changes

[Karltatlerdata]

In order to produce effective sale data analysis using Datawarehouse it would be of massive benefit if we could access Offer data inside the Journal of each property instead of just being linked to the offer sections. This would allow for a timestamped log of all offer activity that would be incredibly useful.

Is this a possible addition?

[github-actions[bot]]

The nature of this request requires product direction and therefore we have moved this issue into our ‘Not Ready’ column whilst we obtain the information/direction required. This issue will be updated when a product decision has been made. For more information on our processes, please click here

[HollyJoyPhillips]

Will require further refinement @plittlewood-rpt FYI

[plittlewood-rpt]

Hi @Karltatlerdata

The underlying problem here is that there is no direct link between a journal entry and an offer entity, as you probably already know. This means it's difficult to accurately attach a journal entry to the correct offer as you have to do it based on the offer amount and amount in the journal entry text which will be prone to error, particularly in cases where applicants change their offer amounts and/or submit multiple offers against the same property.

To be able to deal with this properly, the source data would need to change. It's something we are discussing but have no commitment to (and therefore no timescale at present).

If you are wanting to track something specific, can you give us a bit more detail and we can see if there's anything we can do to support you in the interim as any change to the underlying data structure is going to take a long time.

Thanks

[github-actions[bot]]

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

[Karltatlerdata]

Hi Pete,

I may have mentioned before; the key issue I currently have is in the current schema is that there is no efficient way to track sales and net sales as this relies on offer and off status to get the correct financials and timescales. My current form of thinking is that I have a task come through that is then picked up and pulls in financials from the main property cards. Don’t get me wrong, this works it’s just very prone to missing sales and obviously wrong financials.

Do you have any ideas how we can access sale data another way? The most efficient way I can see is through the journal but I appreciate that’s a massive job!

Edward Francis Data Analyst DDI: 0151 342 0458

[signature_1805979853]https://www.karltatler.com/

[signature_1271568633]https://www.karltatler.com/pages/sell?request-valuation

@.***,-3.1687615,12z/data=!4m8!4m7!1m0!1m5!1m1!1s0x487ad7f52a06699b:0x4e232142b9104029!2m2!1d-3.098722!2d53.329358>

[signature_549509221]https://www.facebook.com/karltatler

[signature_1915107555]https://www.instagram.com/karl_tatler/

[signature_21968547]https://twitter.com/karl_tatler

[signature_477271765]https://www.linkedin.com/company/karl-tatler-estate-agents-&-lettings

@.***https://www.youtube.com/channel/UCZsPDw8R8MwnbklZXcEBugA

From: Pete Littlewood @.> Sent: 08 November 2022 13:42 To: reapit/foundations @.> Cc: Edward Francis @.>; Mention @.> Subject: Re: [reapit/foundations] Sale Data Changes (Issue #8052)

Hi @Karltatlerdatahttps://github.com/Karltatlerdata

The underlying problem here is that there is no direct link between a journal entry and an offer entity, as you probably already know. This means it's difficult to accurately attach a journal entry to the correct offer as you have to do it based on the offer amount and amount in the journal entry text which will be prone to error, particularly in cases where applicants change their offer amounts and/or submit multiple offers against the same property.

To be able to deal with this properly, the source data would need to change. It's something we are discussing but have no commitment to (and therefore no timescale at present).

If you are wanting to track something specific, can you give us a bit more detail and we can see if there's anything we can do to support you in the interim as any change to the underlying data structure is going to take a long time.

Thanks

— Reply to this email directly, view it on GitHubhttps://github.com/reapit/foundations/issues/8052#issuecomment-1307241305, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZBEDL7YAIH25DMTLPJKFVDWHJKC3ANCNFSM6AAAAAARWBB3TQ. You are receiving this because you were mentioned.Message ID: @.**@.>>

---

This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com

---

[plittlewood-rpt]

@Karltatlerdata I have raised this with our product team (the inability to associate journal entries directly with an offer) and it is something being considered. I think what we have in the analytics schema right now is about the best we can get it and I would suggest we revisit this once the product team have looked at enhancements to the journal data store. I'll move this to Long Term rather than close it so we can review it periodically.

[github-actions[bot]]

Whilst the nature of this request has been accepted, we are unable to commit to a specified sprint and therefore have assigned this issue to the ‘Long Term’ column (typically completed 9+ months). We will regularly review any issues and where development capacity is available, or work is aligned with our Roadmap, the issue will be updated. For more information on our processes, please click here