We are exploring whether we can use flex headers to display preferred pronouns at point of sale. However, we've run into a snag because of the TNEW requirement that all transactions occur at the household level -- households do not have pronouns. So even though the pronouns element is available by default, it doesn't work reliably for people who are part of a household since the household record is substituted for the individual record in quicksale.
This goes to a bigger concern we've had about forcing all transactions to occur at the household level, but we've been told that this is a hard requirement for tnew.
I assume there is a clever way to work around this - probably by concatenating first names and pronouns for all household members into a new flex header element. But before I reinvent the wheel I was curious if anyone else had run into this...
-David DwigginsHistoric New England
Hi David,
I've been working on Flex Headers too, but haven't thought about that problem yet. I've been referencing a powerpoint from TLCC2017 quite a bit and there's an example within (slides 59 and 60) that you might be able to alter to fit your situation. I'll attach screen shots since the powerpoint is too large to upload here.