
Hi, everyone. I'm new to OTRS and the list. I'm setting up an OTRS installation that will use an MS SQL backend for CustomerUser. So far, so good. However, I'm mystified about the CustomerValid / validID / valid_id field. I'm clear on the other mappings (unique, customer name, etc), but I have no idea what to map this valid thing to, if anything. I have googled and RTFM'd, but can't find any reference to the thing. Please advise! -b

Hi, Talley, Brooks wrote:
Hi, everyone. I'm new to OTRS and the list.
Nice to meet you. .-)
I'm setting up an OTRS installation that will use an MS SQL backend for CustomerUser. So far, so good. However, I'm mystified about the CustomerValid / validID / valid_id field. I'm clear on the other mappings (unique, customer name, etc), but I have no idea what to map this valid thing to, if anything. I have googled and RTFM'd, but can't find any reference to the thing.
The option CustomerValid for a CustomerUser config option is to define a column in your MS SQL customer table where you have a info if this customer user is valid or not (1 = valid, all other = invalid). -=> It's also possible that you don't use CustomerValid in your CustomerUser, so all CustomerUser are valid.
Please advise! -b
Martin Edenhofer -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Manage your communication!

Talley, Brooks schrieb:
I'm setting up an OTRS installation that will use an MS SQL backend for CustomerUser. So far, so good.
Really? Please search this list's archive for notes about MSSQL and it's failing tries to get into OTRS. If you manage to get OTRS going on MSSQL to full extent, the community will durely be intertested in the database scheme used, and if you had any adaptions to do to the source code. With kind regards, Robert Kehl
participants (3)
-
Martin Edenhofer
-
Robert Kehl
-
Talley, Brooks