I'm using the following displayname_template, which should prefer FullName over PushName:
displayname_template: '{{if .FullName}}{{.FullName}}{{else if .PushName}}{{.PushName}}{{else if .BusinessName}}{{.BusinessName}}{{else}}{{.Jid}}{{end}} (WA)'
When creating a new portal, this works as expected. But when a contacts changes the PushName in whatsapp, this name is taken instead. I tried restarting the bridge and syncing contacts multiple times but it has no effect.
As a workaround, I can change the contact name to something else, wait until the bridge changed it and then change it back. This makes the FullName take precedence over the PushName again.
From my POV, sync contacts should take care of this and follow the priority set in displayname_template
I'm using the following displayname_template, which should prefer FullName over PushName:
When creating a new portal, this works as expected. But when a contacts changes the PushName in whatsapp, this name is taken instead. I tried restarting the bridge and syncing contacts multiple times but it has no effect.
As a workaround, I can change the contact name to something else, wait until the bridge changed it and then change it back. This makes the FullName take precedence over the PushName again.
From my POV,
sync contactsshould take care of this and follow the priority set indisplayname_template