Does anyone have any idea why when we create and process a new order it would be creating a duplicate order with the exact same order number?
This sounds similar to an issue we observed. Tessitura gave this advice:
There is a known issue in V12 where the default Production Season (id 0 in T_PROD_SEASON) and the default Performance (ID 0 in T_PERF) get their season set to something other than 0. It should always be 0 for these two rows. If it gets set to something else it can cause display issues in the client.
If you can fix that yourself you should check it, otherwise open a TASK ticket. What happens is that saving certain changes in production elements will sometimes send you to the default performance or production season (the real source of the bug) and then you might accidentally make edits to those.
Hi Rosa,
Technically speaking I don’t think that it is possible to have two orders with the same order number simply because at the database table level, the order number is the primary key. There cannot exists two records with the same order number. I’m not sure what’s going on with your system but I suspect something else is at play because the database would never allow two orders with the same order number to exist. What happens when you run this query, substituting in the order number in question?
SELECT * FROM T_ORDER WHERE order_no = <insert order number here>
You should only get one row returned, if not then you have a serious problem on your hand and you should contact Tessitura ASAP.
If you get more than one row you can also run this to identify which order numbers have duplicate entries:
SELECT order_no FROM T_ORDER GROUP BY order_no HAVING COUNT(1) > 1
Hope that helps!
Sean
From: "Sean Pinto" <bounce-seanpinto6111@tessituranetwork.com>To: evarro@smm.orgSent: Thursday, June 11, 2015 3:51:13 PMSubject: Re: [Tessitura Technical Forum] Duplicate orders being created
Hi Rosa, Technically speaking I don’t think that it is possible to have two orders with the same order number simply because at the database table level, the order number is the primary key. There cannot exists two records with the same order number. I’m not sure what’s going on with your system but I suspect something else is at play because the database would never allow two orders with the same order number to exist. What happens when you run this query, substituting in the order number in question? SELECT * FROM T_ORDER WHERE order_no = <insert order number here> You should only get one row returned, if not then you have a serious problem on your hand and you should contact Tessitura ASAP. If you get more than one row you can also run this to identify which order numbers have duplicate entries: SELECT order_no FROM T_ORDER GROUP BY order_no HAVING COUNT(1) > 1 Hope that helps! SeanFrom: Rosa Alvarez <bounce-rosaalvarez7844@tessituranetwork.com>Sent: 6/11/2015 4:05:41 PMDoes anyone have any idea why when we create and process a new order it would be creating a duplicate order with the exact same order number? This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you! Spam Not spam Forget previous vote
From: Rosa Alvarez <bounce-rosaalvarez7844@tessituranetwork.com>Sent: 6/11/2015 4:05:41 PM