After being away from GEP for a few months, I'm back working with this and have a few updates and another question.
The process RJ referred to above in Ben Saunder's blog works very well. From what I can tell, it can be a perfect solution in some cases depending on your source data.
If your data feed updates a record for a feature from a status of 'Open' to 'Closed' (just for example) you are good to go.
However I have a situation where the source data will create a brand new row, for the same 'event' when that event changes status (our statuses are 'New', Updated' and Closed) - so we end up with a situation where the same event ends up in our output feature class many times, and the process mentioned above will delete 1 record, for the one where the status is closed, but the 'New' and 'Updated' versions of the event still are present, even though as a whole the event can be considered 'closed' and all records of it need to be removed from the output feature class.
So my question is - how to get around this. My thinking is that we need to use a date-time stamp, where only the most recent record for an event makes it's way into the output, and use this in conjunction with the Ben's method of deleting closed records.
I'm working on this now, but any suggestions are welcome.
Thanks -
Allen