" /> Mandatory contact info field for Outbound - Genesys CTI User Forum

Author Topic: Mandatory contact info field for Outbound  (Read 2174 times)

Offline PFCCWA

  • Hero Member
  • *****
  • Posts: 655
  • Karma: -7
Mandatory contact info field for Outbound
« on: August 24, 2015, 08:14:13 AM »
Advertisement
Hello,

I am setting up a calling list however want to make it match the customers import file.
All of their fields can be set up as user defined fields within CME/GA except for the one relating to contact info.
The customer has this field set up as PHONE1, whereas Genesys will only allow contact_info or phone as accepted field names.  If I set up PHONE1 field with type=contact_info it does not work stating a db error in finding the names it is looking for.
Can we change this?
Genesys support advise to use contact_info or phone but customer would like to use PHONE1 for this purpose (as it is based on their extract).  We are trying to reduce any additional changes required after the customer has produced this import file and keep it automated so supervisors would just need to import into GA or OCM.

thanks.

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: Mandatory contact info field for Outbound
« Reply #1 on: August 24, 2015, 08:20:38 AM »
For these purposes I am using "journals" which is "shadow" tables, where the data are imported from customer site and after that moved to the original OCS tables - It can be achieved through some trigger or customer stored procedure. On this level you can set the "column-conversion-matrix".

Offline PFCCWA

  • Hero Member
  • *****
  • Posts: 655
  • Karma: -7
Re: Mandatory contact info field for Outbound
« Reply #2 on: August 24, 2015, 08:50:04 AM »
thanks, I thought as much.

I also have another similar question, I cannot import a file which just contains values that are separated by the pipe delimiter because it is missing the '=' character.
is there a way around this?
the customer has supplied the file (without [field]=) so am wondering if it can be used as an import file based on field order in the genesys calling list.

thanks,