Hi,
We've got a slight problem with our customer ID format.
We have customers with branches, so in OTRS we created customer IDs such as "Customer1 (NY)", "Customer1 (LA)", and so on and so forth. This is all working, we can create tickets, run reports, and etc.
However the parentheses in the customer IDs break one function: in Customers > Customer Information Center, the "Company Status" widget shows the total number of tickets (total, open, closed, escalated), and clicking on the numbers is supposed bring up a list of tickets, but query doesn't work due to the parenthesis in the customer ID (system log shows there is an error the SQL syntax).
This is something that we totally missed during trial, and would rather not go back to correct all the customer IDs (think OTRS does not retroactively update old tickets if we update a customer ID). Can this problem be remedied by updating the pearl code? Can anyone help us locate the piece of code responsible and make needed changes?
Thanks!
A slight problem with Customer ID
Moderator: crythias
A slight problem with Customer ID
OTRS 3.2.6
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: A slight problem with Customer ID
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Re: A slight problem with Customer ID
Thanks crythias!
We'll definitely try this out on our test server. The only downside is that we have ~100 CustomerIDs that need to be corrected, would've been great if a relatively simple change can be made to the pearl code to remedy this problem.
Thanks again
We'll definitely try this out on our test server. The only downside is that we have ~100 CustomerIDs that need to be corrected, would've been great if a relatively simple change can be made to the pearl code to remedy this problem.
Thanks again

OTRS 3.2.6