- Shipped
- September 2, 2026 at 5:05 PM UTC
- Author
- Kamo
- Commit
- 906a42c
LeadDTO carried neither Lead.country, Lead.subdivision nor Lead.timezone, so the three fields were write-only: UpdateLeadRequest accepted them and LeadService wrote them, but the very next read came back without them and the CRM drew its em-dash placeholder over a populated column. A member who set them, saved, and looked again saw no change and concluded the save had failed. Populate all three from the entity, as name strings like the language field beside them. They are deliberately left readable by maskContactInfoFromOthers(). Each is coarser than the addressMailing.subdivision that mask already chooses to disclose, so withholding them protects nothing; and the Primary Contact editor round-trips them, so a restricted member opening that card would post the blanks back and erase the real values.