The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
Importing Tickets using Transformation Toolkit![Your last visit to this thread was on 1/1/1970 12:00:00 AM](/images/forumimages/new.gif)
Posted: 29 Jan 08 8:33 AM
|
What is the best way to import tickets using the CFX Transformation Toolkit? I guess my biggest question is how do I go about creating new alternatekeysuffix values? Not sure where to start....do I need to create a new function to call via the view?
Thanks! |
|
|
|
Re: Importing Tickets using Transformation Toolkit![Your last visit to this thread was on 1/1/1970 12:00:00 AM](/images/forumimages/new.gif)
Posted: 01 Feb 08 10:36 AM
|
Any suggestions for this? I need an answer as soon as possible...Thanks!
We have a portion of our company that stopped using SLX in December. So, we are trying to get them back into using SLX. In order to do that we have to import their tickets that they logged into their old system. Anyway, any help would be greatly appreciated! |
|
|
|
Re: Importing Tickets using Transformation Toolkit![Your last visit to this thread was on 1/1/1970 12:00:00 AM](/images/forumimages/new.gif)
Posted: 01 Feb 08 4:47 PM
|
Hi Sarah,
The Transformation Toolkit does not have anything built in to create ticket numbers. You will need to create something that runs as a task in the DTS package after the ticket data has been imported. You'll import the ticket data normally and just not populate the ticket number. Towards the end of the package you'll have to do something like either 1) Create a VBScript task in the DTS package to run through the newly imported data in the ticket table and create a ticket number for each (I can point you to some postings on saleslogixblog.com that will get you started with creating ticket numbers in VBScript) or 2) Create something in .NET that you can kick off from the end of the package to run through them and create the ticket numbers.
Does that make sense?
-Ryan |
|
|
|
Re: Importing Tickets using Transformation Toolkit![Your last visit to this thread was on 1/1/1970 12:00:00 AM](/images/forumimages/new.gif)
Posted: 04 Feb 08 11:52 AM
|
Thanks Ryan...yes, that does make sense and I kind of figured that that would be the case. If you could point me to the postings that you referenced it would be greatly appreciated.
Thanks... |
|
|
| |
|
Re: Importing Tickets using Transformation Toolkit![Your last visit to this thread was on 1/1/1970 12:00:00 AM](/images/forumimages/new.gif)
Posted: 05 Feb 08 8:18 AM
|
My manager brought up a point that I need to pursue a minute....
Since this is a one time only deal and when we initially converted the data via the upgrade we skipped a bunch of numbers, what would the ramifications be for us to go back and use 3300 of those skipped numbers? I would just figure out the numbers and put them into the access database that I am using to import the data. Would that mess up a whole bunch of stuff? That way we don't have to spend a whole lot of time worrying about getting the alternatekeysuffix populated via a script, etc.
It was just a thought and I said I would look into it a bit more....any thoughts on that? Or should I just persue trying to get the scripting to work?
Thanks.... |
|
|
|
Re: Importing Tickets using Transformation Toolkit![Your last visit to this thread was on 1/1/1970 12:00:00 AM](/images/forumimages/new.gif)
Posted: 08 Feb 08 10:38 PM
|
Hi Sarah,
If this is just a one time import, you could even just load in all the ticket data and then run a script inside of SLX to populate the ticket numbers using the built-in PrettyKey functions. That would make this a very easy task.
I wouldn't worry about the skipped numbers. The SITEKEYS table liklely has a value set above those since you've been creating ticket entries along the way and it will just keep going. I wouldn't attempt to use the skipped number range, but it wouldn't hurt if you did (but would be unneccessary)
-Ryan |
|
|
|