​@Blommetje Perhaps this information is not entirely up-to-date, but this was the situation the setting needed to be enabled on views.

The “Identity” is obviously enabled on the last column that makes a record unique on PK bases and the underlying tables in the template need to support this key to be creation by the seeded value. If you were to add a record, the IO trigger would do its thing and that is it. Because the setting is enabled, the GUI would also call an SCOPY_INDENTITY() so it could complete the full PK and it would “Jump to row”.

Of course this also meant that the INSERT statement would keep the specific column NULL.

This might not exactly support your situation, but I’d thought I’d share my experience where this became useful/needed.
 

The reason I asked this is a followed. I have a VW that derives info from several table, activity, activity_item, and item. The PK must be unique and is the >table_name_id] per table, or combined. Recently an Import was needed. We use the GUI native import function to import items.

I now use the unique column activity_item_id as PK in the view, which works fine on the gui end. However, when I disable the IDENTITY checkbox for this column, the import fails, stating the mandatory column is missing in the insert. When I do check it as identity, the import works.

In short, this setup is not entirely clear to me.