You can modify the data of the underlying base table through the view as long as the following conditions are true:
1. Any modifications (including UPDATE, INSERT, and DELETE statements) can reference only one column of a base table.
2. Columns that are modified in the view must refer directly to the underlying data in the table column. These columns cannot be derived in any other way, as in the following ways:
1) Aggregate functions: AVG, COUNT, SUM, MIN, MAX, GROUPING, STDEV, STDEVP, VAR, and VARP.
2) calculation. The column cannot be evaluated from an expression that uses a different column. Columns formed using the SET Operator Union, UNION ALL, CROSSJOIN, EXCEPT, and INTERSECT are counted in the calculation and cannot be updated.
3. The modified column is not affected by the GROUP by, having, or DISTINCT clauses.
4. TOP is not used anywhere in the view's select_statement with the CHECK OPTION clause.
The above restrictions apply to any subquery in the view's FROM clause as if it were applied to the view itself. Typically, the database engine must be able to explicitly track modifications from a view definition to a base table
Modifying table data in a SQL database with a well-created view