Impossible to SetMemberStatus complete singles Cloud Connector

We are trying to build a simple Cloud for Eloqua connector.  Our connector updates the Contact objects that flow into it with additional information.

The logic is simple.  In a loop:

  1. ListMembersInStepByStatus through the cloud connector API (aka ExternalActionService.svc) to get the maximum of 1,000 members with status "AwaitingAction."
  2. Retrieve matching items of Contact via the API (aka Service.svc) normal data.
  3. Update Contacts via the normal data API.
  4. SetMemberStatus through the API of connector of Cloud to mark them as "Complete".

To test our output connector, we tried using the time (in 9 Eloqua) builders program and (E10PartnerPlayground) campaigns to create super-simple workflows that just pump a few contacts in a cloud connector.

We can successfully do steps 1-3.  However, our SetMemberStatus calls fail to change the status of a member to 'Complete' - everything "AwaitingAction."  We see this in both contexts program Builder and campaign.

We waited hours for the changes to take effect, but no difference.

Thanks in advance for any help.

Python examples to help illustrate this issue:

from foam import WSSE, customer

def mkclient (wsdl, org, user, password):

CLI = customer. Customer (WSDL)

Security = WSSE. Security()

Token = WSSE. UsernameToken ('% s\\ %s "% (org, user) password")

Security.Tokens.Append (Token)

CLI.set_options (wsse = Security)

return of cli

def main():

# connect to eloqua API

org, user, pw = open('/home/yang/.eloqua.auth').read().split)

svc = mkclient ("https://secure.eloqua.com/API/1.2/Service.svc?wsdl', org, user, pw")

ccs = mkclient ("https://secure.eloqua.com/api/1.2/ExternalActionService.svc?wsdl', org, user, pw")

While True:

# 1. the extraction of the queue of the cloud connector

MS = ccs.service.ListMembersInStepByStatus (5013, 'AwaitingAction', 0, 50). Members

Print "got members:'"

print ms

# 2. extract the matching contact entities; are not suitable to reproduce the problem

# type_contact = svc.client.factory.create ('EntityType')

# contact_type.ID = 0

# type_contact. Name = "Contact".

# type_contact. Type = 'Base '.

# cs = svc.service.Retrieve (...)

# 3. update of contacts in eloqua

# ...

# 4. Mark members as complete

RES = ccs.service.SetMemberStatus (ms, 'Complete')

Print "authorized members:'"

print resources

# in all our tests, this loop really only runs once

breaking

If __name__ == "__main__":

main()

The problem was that demand for SetMemberStatus was not correctly under construction.  We should have wrapped up the list of members in an ArrayOfMember element:

NS = ccs.factory.create ('ArrayOfMember')

NS. Member.extend (MS)

RES = ccs.service.SetMemberStatus (ns, 'Complete')

Foam too bad is not automatically catch this malformation.

Tags: Marketers

Similar Questions

  • Why my Cloud connectors expire with Eloqua password?

    I recently added some calculator cloud connectors to my innate program date. Then my Eloqua password expired recently. Apparently, this caused all my Cloud Connector passwords also expire.

    1. Why did I not receive an email notice that all these connectors cloud has expired and therefore caused my stall programs?
    2. How can I prevent my cloud connectors to exhale with my password? It is such an inconvenience to have to go back in every single program and re - enter new password Eloqua.

    Hi Krista, Eloqua our peeps can correct me if this is not correct, but I think that the solution for this is to set up a new user in Eloqua with access to the API. The value that the user so that they do not have to change the password, then press the shoulder of your support rep first to make sure this password does not expire. At least that's what (I believe) we come to one of our cloud connectors that we have put in place the week last with the help of our representative.

  • Question about cloud connectors

    We try to create a cloud to Eloqua connector. I read the CloudConnectorSampleGuide. I have a few questions about the expected data models and models of general implementation.

    Configuration of the connector of the cloud

    • The CC stores the identification information for each configured CC step Eloquya Eloqua?
      • What are the guidelines for the safe password storage? (I can't store the passwords as dirty one-way-hash that I need the password during execution.  The two-way hash gives an illusion of security but is not better than the plaintext).
    • When the CC is configured, where credentials should take place between the 1st and the 2nd screen? (i.e. as a hidden form field, session cookie cookie/etc.)
    • Eloqua warns the CC when a step is deleted?

    Cloud connector performance

    • What is the average number of steps configured Single that manages the CC?
    • Is it possible for a CC to have 1000 s and unique not configured to query?
    • What are the guidelines for scalability when the connector has to travel 1000 steps configured and survey? The CC requires a worker architecture to manage a large number of configured steps?
    • Are there best practices around the CC recovery hangs
      • For example: CC acquires the State waiting for members and moves to the current State. The CC blocks before the end of the stage. What is the approach suggested for

    recovery of the tasks in the current handling during recovery state? (assuming I have multiple instances of CC of the Eloqua poll). Is the connector of cloud supposed to maintain States of WIP to manage recovery correctly?

    Dmitry, once again, it is entirely to the developer.  When you add contacts to a stage, they will be processed in batches.  There is no limit to how much you add, and since they are left to step up to that dealt with by the connector, how long they sit depends on how long your connector takes to do its job.  Expectations, of course the faster you can deal with the best.

  • Questions of the ON24 cloud connector

    You have some questions, little that can actually be applicable and able to answer by people using connectors of cloud by other Webinar providers too...

    (1) by using the register cloud connector, I notice more often, he can send that ON24 data once a day. Anyone know what time of the day it does this?

    (2) associated with #1, what happens to people who register at the last minute? They are not if is going to be in the system at the time where the stats Webinar, won't be able to connect.  I remember when I saw a demo of ReadyTalk cloud connectors, they talked about this question and said they send a different email to these people, with a direct link to the webinar, without having them to connect.  Other people do it too, or is it better to maually run the connector cloud just before the start of the event, to push these people of last minute?

    (3) I'm not the admin of On24, so this question may be basic and I hope easy to answer - the landing page on On24 standard where the connection of people and you register has the form of ON24. Obviously, I don't want to replace this form with form Eloqua? Or so people otherways to go about this?

    Thank you

    Eytan

    Cloudfeeder really does not fit in your use case. It is used when someone wants to transfer those who are not registered channel Eloqua in the system.

    It seems that On24 CloudConnector registry has a single drop further down to the amount of time that should not be in step. We feel that deleted. For now, just leave it at once a day. He will speak in the regular time.

  • Cloud connector - Contact in Eloqua is created

    I'm building a new cloud connector. I have reviewed the following doc http://img.en25.com/Web/Eloqua/EloquaCloudConnectorSampleGuide.pdf

    In the above example, the doc assumes that the e-mail address already exists in Eloqua. The cloud connector is used to get the name, the name of the database to Hoover and update Eloqua with her.

    I'm working on a connector Cloud will be slightly different from the example above.

    Cloud connector will create new contacts in Eloqua.

    The use case is as follows. (I call our environment, DB like Hoover)

    1) clients will set up a Webcast directly into our Hoover environment.

    .

    (2) links are sent directly to potential viewers by using Outlook.

    (3) viewers, will register for the event by using the sent URL. They will not go through the Eloqua Reg form.

    (4) customer will execute the webcast.

    Note: Eloqua was not used in all cases follow the steps above.

    Now in Eloqua

    (5) customer will create a program generator No. This step would use the cloud connector I build who would get a list of all users who attended the event.

    Because Eloqua was not used to send links to the Viewer, the information of Contact/emails from viewers are not present in Eloqua.

    Cloud connector will be used to create the contact information of all viewers in Eloqua uses information from Hoover.

    My questions are these.

    1. Can the connector Cloud to create a new contact in Eloqua using data since the Hoover database?
    2. Because the contact does not exist in Eloqua, should I create the contact in Eloqua and define its status as 'Complete' directly?

    Thank you

    This will help you answer your questions building Cloud connectors: what type should I build?

  • Is someone using the data cloud connector Melissa with Eloqua

    We are in the middle of our integration and try to make calls from Melissa Data of our Eloqua forms.  Anyone out there who did or can provide an overview?

    I understand that if someone used this service in real time - if a person completes a form and between a postal code invalid - in real-time we ping Melissa Data to know it is a zip code not valid, and the person filling out the form receives a message that is not valid the data.  Our territory lead routing depends on ensuring that we correct geographic information if we want the data validated in real time.  Thank you!

    Post edited by: Maia Tihista

    Maia,

    I could be wrong, but I'm not aware of a Melissa data cloud connector which was built immediately.  From what I know, I think that David York (on this thread) may be closest on that.  There are other people interested too, can't wait to see it built.

    Steve

  • The Action status external cloud connector

    By writing my cloud connector, I came across a few inconsitencies dealing with the status of a Contact in a stage of program generator.

    1. when a contact is added to a stage and I click 'View the Contacts' in the program generator, the contact's status said "pending Action".  When I use my connector cloud to call ListMembersInStepByStatus, however, there is no contact of the AwaitingAction ExternalActionStatus.

    2. after 15 minutes, the program is evaluated for the first time and the status of the contact in the said program generator now "Action underway or planned".  Now when I call ListMembersInStep, he finds the contact in the AwaitingActionStatus.

    3. I use my connector cloud to call SetMemberStatus to set the status of the external action in full contact.  The status of the contact in the program generator still says "Current or planned Action" until the program is evaluated again contact moves this step.

    What is the desired behavior?  I think I should be able to get the contact in the State of AwaitingAction as soon as it is added to the stage and under 'View the Contacts' status would take into account the ExternalActionStatus.

    See also here:

    http://topliners.Eloqua.com/community/do_it/blog/2011/11/19/building-cloud-connectors-timing

  • Delay with Gotowebinar cloud connector records? Where is the problem?

    Hi all

    I ran a number of campaigns of Webinar recently and every time there was a delay with contacts once they land on the connector of cloud on the canvas of the campaign. In my last campaign, there was a delay of two hours. In the end I had to manually register a certain number of contacts they complained.

    Would be - anyone know if there is a failure with gotowebinar or connectors of clouds are sometimes known to do this. Also are there tricks to try to minimize the delay.

    If I can't solve this problem, I sued a different Webinar provider that cannot be a bad thing.

    Thank you

    HEY Kevin,

    (Full disclosure: I work for ReadyTalk we have our own connector).

    There are several ways that a delay may be introduced in the whole process. Without seeing your campaign, I'll just comment all.

    1. The use of the program generator will set up and artificial deadlines. If you are in normal mode, it's 15 minutes a step. I would recommend the canvas of the campaign to eliminate this type of delay.
    2. Have your segment on the campaign will cause a delay also because they need to cross a decision rule of "They did sign up?" before you get on the cloud connector. The answer here is that the form processing stage put them to a waiting time before the connector. (The step of waiting is configured pour.01 mins) It will also take forward invite since they would not be part of the initial segment.
    3. The cloud connector itself can be slow depending on the number of API calls it undergoes. W
    4. You may also have the form post directly on cloud connector, which eliminates a lot of #1 and #2 using the Repost at server stage in the stages of processing of forms. TJ fields has a document circulating here describing how to do so.

    Using our own in-house cloud connector and avoiding the #1 and #2, we see coming in under 3 minutes quite systematically confirmations. Faster if you use the post to the step of the server in the form.

    Hope that helps. Let me know if have any other questions.

  • How was easy to use Cloud connector?

    I'm still a novice intermediate - I will try to use the cloud connector - if you have some experience and suggest you do anything for this either an easy process - I would appreciate it a lot? on

    One of the best things to do is to check here in Topliners. There is a lot of documentation on how to install and use different cloud connectors.

  • Between in contact with Stuck in Cloud connectors (update: no more)

    We have expereiced a number of issues today where contacts were stuck in cloud connector program steps, for an unusual amount of time.  Someone has seen something similar?

    By using the form submit CC, there were about 63 stuck (at least 8 hours and at a time of Contact data normalizer, there are thousands, blocked for more than 12 hours.

    Problem seems to be resolved. Members are moving now.  I'll return when they all went through stages of cc.

    Can someone tell me what went wrong, and how the Eloqua production solved?   If anything, I would like to know how to quickly fix in the case where it recurrs.

  • Send a reminder 15 minutes SMS via dialogue (or any provider) Cloud Connector in the program generator?

    Someone has understood how to send a text message reminder minutes before an event? Make a SMS on the day of the event, it's easy, but up to the minute? What did you do to achieve this?

    Basically, the connector of cloud for this provider can not being planned, which is fine, I guess, me personally, I want to as the connectors of clouds dynamic and able to have many programs, not specific to a program.

    I found a work around for this (sort of). You can set default step action time restrictions allow this step to work for some time. With this, just hope he wasn't lag when the cloud connector spoke to the third-party. I would recommend the notification SMS to allow more space buffer window and the same for the duration of validity of restrictions on the action of default step setting value.

  • Get an Association of Eloqua data profiles in a cloud connector

    Hi Topliner!

    First question and first post so apologies if the wording is a little weak. Anyway,.

    I am developing a new connector of Cloud and Cloud component for Eloqua for my business.

    I want to data of my company in the Eloqua system database. the issue is that im not sure how I would map the data of a Contact. The proof of identity, I can draw from my database is the eloqua of the visitor cookie, but how would approach I mapping to the Eloqua contact in a cloud connector?

    Thanks for the time!

    You have the e-mail address of the contact in your system?  It is the way I see used most often.

    Another way would be to have your cloud component ask the contact ID of the frame.  When your component is rendered, you can use the substitution of parameters, as described here http://topliners.eloqua.com/community/do_it/blog/2012/02/28/building-cloud-components-the-endpoints--renderinstance.  The framework will pass the ID of the Contact (if known) to the person accessing the page.  You'll then have something to put a link on your update of the data.

    Make sense?

  • Function Math cloud connector

    Hi all

    Can I use text fields and large text fields in the field of digital mathematics and function in string manipulation (find and replace) cloud connector?

    Thank you

    Rama

    I did a few tests, work of manipulation of String on Test, great text and numeric fields, but Math function only works on numeric fields.

    If anyone can confirm this?

  • Progressive profiling on website of the company using the cloud connector

    We would like to start building a progressive profiling on our companies website and I wanted to see if its possible for us to use a form created in Eloqua using progressive profiling cloud connector to do this? I'm not sure if this feature works when you put a form on the Web site of our society rather than using a landing in Eloqua page.

    Did anyone else with progressive profiling their companies outside Eloqua Web site? If so, how it was handled?

    Thanks in advance.

    Hi Robert,.

    This can be done - you can also find these son deserves to be read for some ideas:

    http://topliners.Eloqua.com/thread/2842

    More advanced:

    http://topliners.Eloqua.com/community/do_it/blog/2011/08/03/progress-Pro--JavaScript-for-advanced-progressive-profiling-in-Eloqua-10

  • Demandbase Cloud Connector

    Has anyone use demandbase in E10 cloud connector?

    Please correct the following if I'm wrong, but the search for data based on the ip address. In E9 ip addresses are stored in a profile field where we can move in a contact field. Now we can use the ip address in the cloud connector for the search.

    In E10 profile fields go away, so the only way to capture ip addresses would be via a front-end script when shipping form.

    Here is a bit of redundancy - if we can get only the ip of a contact address in Eloqua via a form submission, then we probably already have the data of demandbase who were seized by scripts API demandbase front-end on the page of the form.

    The main objective of the cloud connector seems to be connections that have not submitted a form. I don't see how this is possible if we can only get an ip address in a contact field via a form in E10 submission.

    I would like to know if anyone has experience in this and can confirm/debunk what I just wrote.

    Thank you

    More information is here: what is the difference between Appcloud.eloqua.com and Cloudconnectors.eloqua.com?

Maybe you are looking for