Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IPOCC database select

Status
Not open for further replies.

as1981

IS-IT--Management
Sep 28, 2006
394
GB
All,

I'm using a sql query element to execute 'select newid()' from a MS Sql server.

I can see from the TT logs and a text to speech element that the value it's storing is a number instead of a guid. I think IPOCC is treating it as a numeric? Is there anyway to correct this?

I also tried select newid() as uniqueidentifier but that had the same problem.

Thanks
 
Where are you saving it?

If you're saving it to a TaskTag that's a Integer it will be treated as numeric.

"Trying is the first step to failure..." - Homer
 
Hello,

Thank you for your help. Sorry I should have specified that. I'm saving it to a local variable within the IVR script. As far as I saw there isn't a way to specify the data type of a local variable?

Thanks

Andrew
 
I have no issue getting strings from DB.
Attach the IVR TTLog, you might need to add VC_DB to see what's happening.

"Trying is the first step to failure..." - Homer
 
Hello,

Thanks for your help. Please see attached.

I think the problem might be in the line:

DB_Connection::selectRequest_(sqlserver,as,select newid() as uniqueidentifier)=103CEB88)

I think it's saying that the result it's taken from the db is 103CEB88? It should be something like 8DB05D9B-1B2E-495D-96AA-46EAAD8356C8

Thanks

 
 http://files.engineering.com/getfile.aspx?folder=741055ba-edf3-4735-bb15-14fa74f46f9d&file=Trace.txt
I think the issue might be that IPOCC can't handle the result of the statement.
What are you using the newid() for?

If you're storing this in a DB later you should probably insert the newid() first and then select it from there.

"Trying is the first step to failure..." - Homer
 
Hello,

Thanks. I agree it looks like IPOCC can't handle the sql result.

I'll think of a new call flow design. I used new ID like this so that I have a unique reference. If I do an insert and then a select then I won't know which ID relates to which call if we get two at the same time.

Thanks
 
You can use CCKTrackID which is unique for the call.

"Trying is the first step to failure..." - Homer
 
Hello,

Thank you for your help.

Andrew
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top