1 of 1 people found this helpful
it is not easy to provide a complete answer without have the dataset to work on
YOu were going down a good track with rank but Index() would have been better - setup on person/date to restart every person
but bear in mind you are now using table calculations - they can be used in conditional (if/then type)like if Index()=5) , statements but you will need to use other table calculations to further aggregate then
If this posts assists in resolving the question, please mark it helpful or as the 'correct answer' if it resolves the question. This will help other users find the same answer/resolution. Thank you.
Thank you for the feedback. I will start looking at Index(), but I wanted to clarify something. I was originally thinking that I should create a calculated field for this so that I could analyze patterns across people based on that distinct order field. Are you saying that the only (or at least preferred) way to handle this would be to do so in the table calculations? I am still learning the limitations of each route.
Actually I am saying that Rank and index are table calculations - they are on the bottom of the order of operation - but that's OK you just have to know that there are some types of calculated fields like LOD expressions that are higher on the order of operation that you will not be able to use with Index()
Nothing wrong with if index()=5 then [something] end