Idea: Expland 'Search for a Constituent' to Include Partial Records

Austen Brown

I have a flow to bring information from a third-party form directly into NXT. I have gone through many iterations trying to figure out the best way to locate and match the information to an existing constituent record with Power Automate using this API. The problem I kept running into is if a spouse were to fill out the form with their name instead of their HOH/Spouse's name, the flow would return a result of ‘no record found’, leading to additional searches and complexity to try to locate the matching record. I ultimately decided to search first on email, and name second only if the flow returns zero or many results.

Ben Lambert

Austen - can you elaborate on what you mean by “partial records”? Do you mean “partial matches” or “non-constituent” records? Any details on how you'd ideally like this to work? Sounds like you've found a reasonable solution using the existing mechanisms, but it would be good to hear how we could improve this for you.

Austen Brown

Hi Ben - By partial records I mean non-constituent records. Ideally, I would like to see the search also include spouse information attached the full record. This would reduce many subsequent conditionals required to locate a match.