Hi,

I have hit a problem with SQL replication and the Identity primary keys on the security BOs. Is there a way of trapping when a new security record is added and replacing the primary key value in program code. Ideally, I would like to avoid doing this through a SQL default column value and handle it entirely within the application.

Thanks in advance.

Aaron

Yes.  You can set the BO properties as such:

PrimaryKeyIsAutoIncremented = False
PrimaryKeyIsUpdatable = True

If you are using the DDT, you will need to check "Primary Key Is Updatable" flag for that field so that the stored sprocs for the CRUD are created correctly.

Thanks Trent.

If I use the built-in StrataFrame.Security.SecurityDialog, is there a way of intercepting new records (i.e. a permission is assigned to a role) so that I can replace the primary key?

Well....not really on the client side.  You could add a trigger on the SQL table to stuff the new PK into a temp table that you then turn around and query to pull from....but that may be more energy than you are wanting to get into.

How can we adda trigger on the SQL table?

att coupon code