1. Plum Voice
  2. Community
  3. Legacy: Plum Fuse Q&A
Answered

Differentiating for a table post

Avatar
Andrew V.
Follow

Differentiating for a table post

Sun Jun 13, 2010 11:15 am

In an inbound call app, where we post a number of identical call campaigns, each of which requires a person to validate with two separate digital entries. So, any person with both codes can create a message which is later used as part of an outbound campaign. My issue is that, although I ask for the 1st row of matching variables to be used, the results will go to all or any of the matching rows. How do I get the results to go to only one of the rows?
0

Comments

6 comments
Sort by Date Votes
  • Official comment
    Avatar
    Andrew V.
    (Edited )

    Re: Differentiating for a table post

    Mon Jun 14, 2010 4:39 pm

    Hi,

    To avoid the possibility of multiple matches in your table, you should structure your table in such a way that each entry has a corresponding random generated number (thus always allowing for only one row to update).
    Comment actions Permalink
  • Avatar
    Andrew V.

    Re: Differentiating for a table post

    Mon Jun 14, 2010 2:07 pm

    Hi,

    Could you please clarify what you mean by where the results will go to?

    Are you using the "Update Row" module, using post-call processing, or using the outbound campaign result column?
    0
    Comment actions Permalink
  • Avatar
    Andrew V.

    Re: Differentiating for a table post

    Mon Jun 14, 2010 2:30 pm

    I may be mixing things up. I am using the update row and will be pushing the data back to our servers. From there, we manipulate some data and create an outbound campaign. At the moment I am trying to assure myself that if we post 50 call campaigns to table we use for inbound calls, that each of the 50 inbound calls will only write to one row. Does that help explain the issue?
    0
    Comment actions Permalink
  • Avatar
    Andrew V.

    Re: Differentiating for a table post

    Mon Jun 14, 2010 4:45 pm

    Thanks. Will do.
    0
    Comment actions Permalink
  • Avatar
    Andrew V.

    Re: Differentiating for a table post

    Fri Jun 25, 2010 12:45 pm

    Thought I understood how to do this. We generate a unique serial number to accompany the campaign number and pin. When an inbound call is received, I select the 1st row. How would I select that unique row? The caller would not know that key. Any suggestions? Down to some of my final issues before field testing on your new app.
    0
    Comment actions Permalink
  • Avatar
    Andrew V.

    Re: Differentiating for a table post

    Fri Jun 25, 2010 3:34 pm

    Hi,

    About your post, would it be possible for the caller to know some unique combination of information that would only select one row (i.e. customer ID and PIN).

    Also, could you further specify what you're trying to do with your application for the caller?
    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post