I am experiencing a similar issue. The insert of a new record with the same values in the #unique fields as an existing record fails. Which would make #Unique more or less useless, if I have to check for existence of the same combination of values before anyway.

Thanks for the reply. Indeed, not only Stanford design like that, there are many others who I would rate quite experienced who create separate view models. Main reason in most cases (and I agree with it) is to keep the view clean of complex computations and data manipulation and have an abstraction layer between user oriented information and model data in the backend. Any other views out there?