Skip to main content

Hi, 

When creating a can set an auto increment for a PK column; 

However, I still need to write something in the Template to fill this column. It's not generated by the SF(or at least I don't see it). When I set this to for example a row_over value it is unique - but the seed/increment is ignored. 

When I select a fixed value (1) - the view PK is not unique and an error is thrown. 

Is this in any other way usable? I don't understand how this should/could work. 

Thanks, 

Blommetje

​@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.
 

Reply


Terms & ConditionsCookie settings