Bringing old values back

Highlighted
Level 2

Bringing old values back

Hi guys! We had a problem where MSD was removing existing fields after they were filled out in a form.

for example, in a form, a lead is filling out the city and phone number fields and a few minutes later, MSD turns their value to "null"

We have fixed this issue but we do have quite a lot of leads without phone number and city.

How can I find or change the new value (null) back to the old value?

Scrolling through leads activity log, I can actually see the old value and the time it was changed to null and doing it manually isn't an option since we have so many of them.

Thanks!

Tags (2)
5 REPLIES 5
Highlighted
Level 10 - Community Moderator

Re: Bringing old values back

Can you move the thread to Products ? This space is for discussing the Champs incentive program, not support. There should be a Move link at the right.

Highlighted
Marketo Employee

Re: Bringing old values back

If you use the bulk activity extract API you'll be able to generate a CSV file of the Change Data Value activities, which would include the new value and the old value.  If you do some Excel magic you could most likely get all the old values into a column and import them back into Marketo.  http://developers.marketo.com/rest-api/bulk-extract/

Highlighted
Level 10 - Champion Alumni

Re: Bringing old values back

If it's a simple mixup like you know people with Country=Namibia got the Country=China, you can easily roll that back with the Was Data Value Changed filter.

otherwise, you would have to do some variant of the above.

Highlighted
Level 2

Re: Bringing old values back

That was country=China and then changed to country=null. So are we talking about the simple roll or the bulk activity extract API?

If the roll, would you mind showing how to do it?

Thanks!

Highlighted
Level 10 - Champion Alumni

Re: Bringing old values back

You can do

Smart List:

Data Value Was Changed: Old Value=China, New Value IS EMPTY

Flow:

CDV: Country=China

but if it's more complex than that, you need to look at other options. If SFDC is tracking that field, you can also try to use SFDC's power to  better identify the problem there and roll it back in SFDC instead.