There have been a number of times where we've wanted to modify how an interface looks and/or functions based on if a person has interacted with a piece of content, prayer request, person, etc in some way in the past.

Currently, there doesn't seem to be a simple way of getting to interactions tied to CurrentPerson for a given entity.

AppendInteractions Lava Filter

One of the ideas that we came up with was to add a "AppendInteractions" lava filter that works similar to how the "AppendFollowings", "AppendWatches" and "AppendSegments" filters do, but just for interactions. We realize that there are exponentially more interactions in the typical database than followings/watches/segments, so performance could be a challenge with this. Having parameters in place to reduce the load of the query/amount of data that comes back.

At minimum, it would be helpful to specify how far back to get interactions, as well as the ability to get the "Operation" back so they could be filtered upon (viewed vs prayed etc).

Entity Properties for Interaction Channel/Component Ids

Another challenge with working with interactions is being able to quickly access the properties related to a given entity that are necessary to write interactions – InteractionChannelId and InteractionComponentId. If there were a way to add properties (non-database values) to entities that correspond to interaction components to quickly access this data, that would be very helpful.