ah ok, we just found it. What I do not like at the current solution is that everybody who sets the employment status needs to know the id for it. We also will need to set it in the linked in Ticket from Willi. So I would like to refactor it a bit. At least some mapping of names to the id, but the own model feels like cleaner for me.... Why do you think that would be harder to handle?