Create a receipt number in the form and store the data

Question

Hello,
I want to create an application/reception form for a certain service and record the reception number as a history.If the same person applies multiple times, I want to leave the number without overwriting.I plan to use LocalForm for now.
 
1) What kind of data should be used for the reception number? (Campaign ID + UserID or something?)
2) I would like to store the receipt number without overwriting it, but I am concerned that it will be overwritten if I use a custom field.
 
I would appreciate it if you could tell me the best method.

SanfordWhiteman · Accepted Answer

1) What kind of data should be used for the reception number? (Campaign ID + UserID or something?)
I would appreciate it if you could tell me the best method.

There's no one "best" answer to that question.

Is Campaign ID + Marketo Person ID (not "user" ID) a unique enough identifier for your business?

A given lead doesn't necessarily have the same ID over time, due to merges. So you might end up with value "1234-56789" on a person whose ID is currently 56790 (having been merged w/56789 at some point). But that also means 56789 is gone from the system and, within reason, will not be reused. So it's probably acceptable for this specific, non-cryptographic use case.

However, you can't use the {{campaign.id}} token from JS unless you're on a Marketo LP. So this isn't very scalable. Since browsers are good at creating random numbers, you might as well gen it on the fly:

{
  const formReceiptNumber = new Date().getTime() + "-" + crypto.getRandomValues(new Uint32Array(1))[0].toString()
  MktoForms2.whenReady(function(mktoForm){
    mktoForm.addHiddenFields({
      formReceiptNumber: formReceiptNumber
    });
  });
}

2) I would like to store the receipt number without overwriting it, but I am concerned that it will be overwritten if I use a custom field.

This is not a concern. In Field Management, block updates from form fillouts. Note this isn't any different with standard vs. custom fields.

Darshil_Shah1 · Answer

@kyoko wrote:Hello, 1) What kind of data should be used for the reception number? (Campaign ID + UserID or something?)When you say campaign id, do you mean the Marketo program id or the smart campaign id? With the very limited knowledge of your setup and use case, I'd incline towards using the Marketo program id + lead id as the reception number as the program id is unique for each program and the lead id is unique for all the leads. You could also use the Marketo smart campaign id, but I think program id might make more sense here unless you want to factor in unique ids of multiple smart campaigns in a single program.  Instead of marketo defined program/campaign ids, you could use a self-defined ID for each tactic also. Again, this could change if there are more details to this use case that aren't listed in the question. 2) I would like to store the receipt number without overwriting it, but I am concerned that it will be overwritten if I use a custom field. I would appreciate it if you could tell me the best method.For ensuring the data isn't updated in the custom field, you could easily block the field updates for that respective field from the field management section in Marketo Admin.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded