Skip to Content
avatar image
Former Member

Agentry Flunkies

I'm working through the exercises in MOB30R and on Unit 6, Task 9.4 I'm getting an error where the notification dialog keeps appearing. This is caused by the SycloCustomersExchange table not being populated when a new Customer is added to the Customers table.

The trigger is firing but I'm seeing the following entry in one of the log files:

2014/09/16 11:39:56.100:           + Query=Push "PushCustomers" Read "PushUpdateCustomersExchange"

2014/09/16 11:39:56.100:             : 8 lines, 7 non-printing characters, 199 total characters

UPDATE

  SycloCustomersExchange

SET

  Action = 'R'

WHERE

  UserID = 'Cannot find flunky user.agentryID' AND

  CustomerID = 'Cannot find flunky object.customerID' AND

  ServerID = '############'

What would cause the cannot find flunky statement?

Here is the code for my PushUpdateCustomersExchange:

UPDATE

  SycloCustomersExchange

SET

  Action = 'R'

WHERE

  UserID = '<<user.agentryID>>' AND

  CustomerID = '<<object.customerID>>' AND

  ServerID = '<<server.serialNumber>>'

Any suggestions appreciated.

Thanks,

Dave

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Sep 16, 2014 at 06:38 PM

    Dave,

    When using Push you need to remember that Push is running on the Server on timed intervals.  It usually does not have a user context and as such the <<user.xxxx>> and <<object.xxxx>> flunkies (or SDML tags) will not evaluate when the step is set to run one time.  Even if you switch to run once per user I don't think those tags will evaluate as they are client connection specific tags.  Worth trying.

    The Push steps that have a user context are the Response steps where the data / object is already downloaded to the device an can then update back to the backend based on an object reference tag.

    --Bill

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Thank you Bill. It turns out I had the PushUpdateCustomersExchange step defined as a retrieval step instead of response step. Once I defined it properly it started working.