Hi there. We are seeing some strange behavior with the

Patient.active

search parameter. We are creating patients via the

/admin/projects/:projectId/invite

API. It seems that when we invite patients through this API, even though

Patient.active = undefined

, the search parameter column in the database is being set to

FALSE

. If you then set and unset

active

, the

active

column in the database is properly set to

null

. I have been digging and cannot understand why this is happening. This is making filtering for for active/inactive users very difficult. Any help/guidance.

What version are you running? I had a [PR](https://github.com/medplum/medplum/pull/8009/changes) that may have addressed this in the [5.0.9 release](https://github.com/medplum/medplum/releases/tag/v5.0.9). Although since you're able to set it to

null

at all that might indicate it's elsewhere, can't remember.

Ahh, we just upgraded to 5.1.1. All of the cases where

undefined

went to

false

were from the older version. I will re-review

Nice, I believe you should be good after reindexing Patient's from the

SuperConfig

page in order to apply that change to the resources created before upgrading.

Ahah! Yep this is solved now. And that also explains why I was seeing such weird behavior b/c I didn't reindex Patients