
thanks.
thats what I thought, just did want to go forward on the assumption that it
only had to be changed in one other table if I decide that I want different
customer ids.
as a feature request it would be good to have a customer id asa numerical
value with a separate table presenting a user friendly value. Then agents
would know easily tht customer id 1 = company 1 and customer id 2 = company
2.
just some thoughts
"Tyler Hepworth"
On Sun, 3 Oct 2004 12:59:01 +0100, Des Quinn
wrote: Hi,
Is it intentional that if you have an existing user with tickets that if you change the cstomer id that they appear to have no tickets associated with them the next time they log in.
Yes, this will happen If you change the customers id in the database where customer id is drawn from (because all tickets have a customer id associated as well to be able to match up customer with ticket).
Scenario. Customer with id 1 creates a ticket. Ticket also has customer id value of 1.
Customer ------------ cust id = 1 A Match! Ticket ------------ cust id = 1
If you change the Customer's cust id to 2, then you have:
Customer ------------ cust id = 2 No Match! Ticket ------- cust id = 1
if you change the customer id back to its original value then the tickets reappear. I am guessing that this is relating to the customer_id value in the ticket table.
Yep, exactly. See above.
If I wish to change the customer ids in use can I just ho thru the ticket table and change the customer_id to the new values and the tickets should retain their association with the user?
Exactly. If you change the customer's id, you also have to change the cust id of all the tickets.
Hth,
Tyler Hepworth _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support oder Consulting für Ihr OTRS System? => http://www.otrs.de/