Does anyone know why tessitura is trying to insert a number into my table that is set as an id_key IDENTITY (1,1)? This should start at 1 and increment by 1. I am getting an IDENTITY_INSERT error because of this and it therefore is not allowing me to add via my custom tab. Just an FYI, I ran a trace and the number that tessitura is trying to insert is consistently a number in the 9,000 range.
Any thoughts would be helpful and thank you in advance!
Joe
HI Joe,
select * from t_next_id where type='CT'
have fun
Hi Ben
Thank you and one other question, should I keep the id_key as an identity incrementing by one and should I start it at 9131?
Thanks again for your help!
Joe, the id_key column should not be an Identity column because the Tessitura application assigns the primary key when a new row is added in the tab. The reason that the id is greater than 9000 is because all custom tabs use the same incremented key (row in T_NEXT_ID).
-Ryan
Hi Matt
This might seem really basic, but is it possible that in the stored procedure or the select that’s behind the custom screens, there’s a where clause that is a fixed customer_no rather than a variable? I know I will often put in a specific customer_no when I am testing and it is easy to forget to comment it out and uncomment the variable.
Just looking for the mole hill before the mountain ;-)
Regards
Sandra