" /> DTS package for Outbound Calling List Import - Genesys CTI User Forum

Author Topic: DTS package for Outbound Calling List Import  (Read 3848 times)

This topic contains a post which is marked as Best Answer. Press here if you would like to see it.

Mark_Jall

  • Guest
DTS package for Outbound Calling List Import
« on: April 17, 2009, 11:38:57 AM »
Advertisement
Hello to All

We have an outbound setup where currently the calling list is being imported manually.We are now planning to automate the calling import process where the input file would be sent as an excel or a flat file as we will have to run scheduled application that would then modify this data and then import into the Genesys Calling List db.We think an SQL DTS package would be the best are way to do this as we currently are using MS Sql db.

But we dont have the expertise to develop a DTS package.If any one can share a sample one I could probably work on it and modify it to suit our requirement

Offline Dionysis

  • Sr. Member
  • ****
  • Posts: 408
  • Karma: 8
Re: DTS package for Outbound Calling List Import
« Reply #1 on: April 17, 2009, 11:44:02 AM »
This is a very straight forward import into an MSSQL database.  The import data wizard should cover everything you need, just follow the bouncing ball.

The only difficult part would be chaining.  Do you have more than 1 phone number per customer?


Mark_Jall

  • Guest
Re: DTS package for Outbound Calling List Import
« Reply #2 on: April 17, 2009, 11:54:40 AM »
yes we do have record chaining aswell ..also iam not sure on how we should insert the data for the mandatory fields like ids,from-to etc ...while import using ocm it is normally taken care by the ocm

tnks..mj

Marked as best answer by on May 05, 2025, 01:29:59 AM

Offline Dionysis

  • Sr. Member
  • ****
  • Posts: 408
  • Karma: 8
Re: DTS package for Outbound Calling List Import
« Reply #3 on: April 17, 2009, 12:10:17 PM »
  • Undo Best Answer
  • You can find the necessary information for these fields in the Outbound manuals.

    record_id can just be an identity seed.
    daily_from and till are set as the number of seconds from midnight, so 10am = 10*60*60

    Chain_id = an id for each customer (doesn't matter what the number is really provided each customer has a unique id)
    Chain_n = number in chain (0 dials first, 1 dials second, and so on)

    tz_dbid = Configuration database id of the timezone you want to apply for the record.

    That's all the mandatory ones I can think of off the top of my head.  Any others you need?