Customers with no policies

[Andrew Carrick]

Just done a clean-up check and found some TAM client records which I guess failed during the creation process. The report lists the TAM ref, but shows name as "~NEW" and has Agency and Branch blank. They don't appear in Client List in TAM. I thought I would add agency and branch codes and they would magically appear in TAM but they don't.

I could just delete them directly from the database, but I'd like to understand what else they need to become visible. Anybody know?

[GeorgeW]

I've always just deleted those from the database.

[Lance Bateman]

Yes, either you could delete, or support could - they are not good records.

[Andrew Carrick]

I think I sussed it, you need to change ~NEW to something real. I changed one to "New client" and lo and behold it appears in TAM. Andrew 1, Computer 0.

[Alice Mooney]

Andrew - how did you find these? Did they show up in the results of a Tam report?  And ^5 on the find to fix it!

[Andrew Carrick]

Just run the canned report "Customer List" with criteria set to "customers with no policies". Send it to excel and you can spot the crappy ones easily.

Next task is to hound the CSRs who set up the other clients but no policies!

[Ian Blundell]

Do you have to go into the database directly to delete these records?  What happens if you set up a new customer and tell it to use one of these codes?  Would that let you get into the code and then delete it from within TAM?

[brinkerdana]

Just run the canned report "Customer List" with criteria set to "customers with no policies". Send it to excel and you can spot the crappy ones easily.

Next task is to hound the CSRs who set up the other clients but no policies!

You don't use cross references for those corp v. DBAs?

[Lance Bateman]

We try to avoid XR files - for your question, we do the following:

1. If a person only doing business (person's name) - first four of last name, first initial, dash and number.  That way it shows near or next to personal lines files also.

2. If person or corporate, with a dba - name line is the dba, attention is the person's or corporate name.  E.g. Lance Bateman dba Hopeless Romantic would have Hopeless Romantic in the "name" field, Lance Bateman dba in the "attention" field.  Numbered according to the name field.

Just run the canned report "Customer List" with criteria set to "customers with no policies". Send it to excel and you can spot the crappy ones easily.

Next task is to hound the CSRs who set up the other clients but no policies!

You don't use cross references for those corp v. DBAs?

[Andrew Carrick]

Sorry, dba = ?

Ian, I tried that but it doesn't let you do it.

[Alice Mooney]

dba = doing business as

[Andrew Carrick]

Ah OK thanks. Over here we'd say "t/as" = trading as.

[Alice Mooney]

so...you guys still "trading" over there across the pond, eh? Come to 'merica and we'll show ya how da bizness is run 
(sorry. couldn't let that one go for some reason)

[Andrew Carrick]

fugeddaboudit (as I believe the phrase goes) 

[Conan_Ward]

Do you have to go into the database directly to delete these records?  What happens if you set up a new customer and tell it to use one of these codes?  Would that let you get into the code and then delete it from within TAM?

EDIT: this doesn't actually work, see Alice's post later
Generally it should tell you that the code has been previously used and won't let you directly create it in customers...however, you can create a prospect with the same code, move it to customers and it'll attach to that code...for a non-database workaround. Otherwise, going into the database or contacting support to have us do it will work.

[Andrew Carrick]

I did try the Prospect to Customer fix as that's solved other issues in the past but didn't do it this time. Thanks anyway. Have now edited the DBF and then deleted the client records.

[Alice Mooney]

Do you have to go into the database directly to delete these records?  What happens if you set up a new customer and tell it to use one of these codes?  Would that let you get into the code and then delete it from within TAM?

Generally it should tell you that the code has been previously used and won't let you directly create it in customers...however, you can create a prospect with the same code, move it to customers and it'll attach to that code...for a non-database workaround. Otherwise, going into the database or contacting support to have us do it will work.

Edit / KB55371...nevermind
Conan - just tried what you suggested and received an error and locked up my Tam.  Not doing anything different and all required fields are completed. Had to close Tam w/Task Manager.

EXCEPTION DETAIL REPORT

Title      : ClntMove
Error Text : An error occurred while running main move.

Process          : C:\WINTAM\AppliedSystems.TAM.Client.General.ClientMove.exe 10.0.1.0
ASTamSvr Version : 10.4.0.6
Computer Name    : CIT25000016013
User Name        : amooney
Time/Date        : 12:50:30 05/22/2012
Operating System : Windows XP Professional Build 2600 Service Pack 3
CPU              : Intel FUTURE Lev[15] Rev[4303] Num[2]
Physical Memory  : 82% free of 3275016 KB
Paging File      : 89% free of 5204980 KB

Sequence of Preceding Exceptions

  Source : MoveClientValidateNewClientCode
  Number :   2147746792 (Decimal)   800403E8 (Hex)
  Desc   : "/Agency/" is not a recognized access name.

  Source : .frmMove.MoveProspect
  Number :   2147746792 (Decimal)   800403E8 (Hex)
  Desc   : "/Agency/" is not a recognized access name.

  Source : AppliedSystems.Tam.Client.General.ClientMove
  Number :   2147746792 (Decimal)   800403E8 (Hex)
  Desc   : "/Agency/" is not a recognized access name.

[Conan_Ward]

doh
my mistake, correction, don't do what I said, they do have to be removed in the database after all :/

[Alice Mooney]

not to worry. it's all good