Is it possible to have a validation process with an email before updating a field from an eloqua form into the eloqua database ?
ex: my form integrates a field called "Persona" . This field is an important information so I want to be able to collect it in all Eloqua forms I produce. However, if I have already collected this information from a contact and this contact is entering a data in a new form which is not consistent from previous data stored I would like to be able to send him an email to ask him if he/she really wants to validate this new value before updating it? Is it possible to do this ? Has anyone done this in practice already ? Any feedback ?
Rgds
Xavier
Ps: prefilling is not always possible because some form respondents might come from social media and not be recognized by a cookie
Pss: once updated the field is updated once a night with Website contact database. An alternative is to capture this field from eloqua form only if this field was empty in eloqua. If not then a user needs to go to website contact database with password-based login to change the value. The drawback is that you have to create a web contact for each persone filling in an eloqua from and this may require minimum level of information you would not have asked in some of the eloqua forms otherwise
You could prefill the data by performing a data lookup on the contact's email address (cookie or not). When the user completes their email address, use a script to lookup against the Eloqua contact database, and return the field values in the background. Upon submission of the form, do a diff check on the values entered vs the values you retrieved from the database. Output the result and submit that in another field through the form, then use that data after the fact. Maybe you could create an algorithm that sets a threshold for a significant change, set a boolean to true when that threshold is met, then trigger a campaign to send an email with their new values in the body, confirming if that is correct.
Related
I am trying to make a Google form in which I want a field "username" where users can enters their username and submits the form but when they try to submit again using the same username the form should not be submitted and displays error message "You have already submitted"
at the moment there is no way to allow restrictions for unique answers per specific questions, however, you can restrict one response per Google Account by going to settings on the form, clicking responses and collecting email responses along with "Limit to one response".
In Laravel Spark you can set the option that when the customers creates their account the system show them the form to fill the billing address & VAT no.
Unfortunately to have the correct data on the invoice they have to go to /settings#/invoices to fill in the data after finish all the registration process, confirming their email and log-in.
This is very inconvenient as nobody understand this step and there where 0 (zero) customers of over 500 we have until now who actually find this field and filled it up. They just complain that the invoice is incorrect and we have to send corrections.
So my question is:
Is there a way to put the "Extra billing information" field which is here /settings#/invoices on the registration front so the customer will be able to fill it in during the registration process?
I needed to follow the same steps like with adding any other field to the registration form because the company data are stored in extra_billing_information column in users table.
Reference: https://www.core45.com/en/blog/how-to-add-customera-company-data-for-invoice-on-the-registration-form-in-laravel-spark
don't know if this is the right place to ask for this:
I'm currently working on a in-house control system in Google Sheets. Everytime a sales rep enters a work order, this work order with info filled in the form needs to be send to the designer team via email.
The form contains a field for the designer's ID (The form is here).
I've got two problems, first the designer's emails are in a different sheet and the email must be send to the designated designer each time a response is submitted.
This is the spreadsheet I am working on this link.
The email must contain all the fields in the form.
Thank in advance.
In Access there is a feature called "Create email" whereby you can select a table and send rows to users to fill in data.
When they reply to the email, Access automatically updates with the data they have entered.
Thats great if each user only has one or two rows of data to fill in, but if they need to fill in a large quantity of data, they might only get round to filling in a few records at a time, and potentially not in the same order as is in the database.
How can users keep track of what they have updated and what they havn't?
Does this functionality exist or is this something that Access can't handle?
Many thanks
John
Hardly anything can handle this, because you have no control of what the user may do with your e-mail. Further, you often have to rely on one e-mail client only like Outlook which never will be true in real life where people read mail on all sort of devices.
The best option is to forward a link to a site where the user can input data and where you have full validation of these, and where the collected data are ready for import in your database in a controlled manner.
From PayPal's documentation:
"PayPal returns related variables for each kind of IPN message. Not all variables are returned for each type of transaction."
I was initially planning to create a table in the database with the message fields but now after I read this it doesn't seem like a good a idea anymore (esp. that I see a lot of fields in their IPN documentation).
I have a few ideas (e.g. using tabs and new lines character separate fields and values. Or, saving the the whole thing in XML in the database) but just wondering how you handle logging IPN messages?
What I do is save it to a database table with columns for information that is important to me along with a "raw" column. I take the form parameters collection and serialize it like a query string and push it in. That way all of the original information is available if I should need it but my database schema remains simple and reflects the information that is important to me.
I'd agree with the previous comment. IPN messages can be quite variable, and can be about 40-50 fields per submission. Just pull the few fields you need for your application (amount, customer info, etc) and drop the rest into an XML or TEXT field just in case you need it later.
I faced the same challenges when I integrate PayPal adaptive Payment. The fastest way I did is to store the IPN details (when PayPal calls the IPN handler that I did) to static variable so that the values can be shown regardless of browsers I used.