Thanks for jumping in here. @Luke M if you had time to look at this I would very much appreciate it.
I understand that a robust alternative to the approach within the file will take some time but if any of you guys could help it would be awesome. The issue I have is latency, the formulae all work and provide what I need. @Asheesh has done an awesome job so far!
Hi Pitcher,
I think we can reduce a lot of calculations if instead of having all our formula columns figure out where the first touch is, we have a single column do that work. In the attached, I do this in column K. For your final version, you can hide column K so as not to distract user.
Once you know which row to be looking at (found w/o arrays), your other formulas become much less intensive.
The other trick I did was create a lookup helper column in source tables. By concatenating the columns, we no longer need an array in downstream tables.
Appreciate the help, this should hopefully help the latency. Before I load in some more data...
So just two things:
1). there are one or two anomalies, Row 5 (has a first touch date but there are no touches), Row 317 (there are 4 touches but the corresponding activity and time to touch etc was not captured. Can this be resolved?
2). Can you please update the "pushlead Lead" tab as per the "pushlead contacts" tab