Since this is part of the name of the language, I think that it would be best practice for you to include it in the ViewModel, populate it when you first grab the data in your controller and just donβt do anything when you return to the controller to save it.
The only thing close to what you are describing is the NotMapped attribute for the Entity Framework, which will know that it does not create a column for this field or does not save anything in the database for it. But usually they are used only for pre-calculated properties (i.e. you want to quickly request a sum of three fields).
source share