Skip to main content
A
Anonymous
January 8, 2013
Question

Normalizing Industry Values

  • January 8, 2013
  • 4 replies
  • 1627 views
I'm trying to normalize industry values in a Marketo account that is not synced to any CRM. I've gone through and ensured that all of the values in the database are normalized, however I'm finding that there are still some old values in the drop down list that have no records in the database.

Does anyone know how to delete those old values? In my previous experience, when there are no more records with a certain value, that value disappears from the drop down - however that does not seem to be happening in this case.

Any suggestions?
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

4 replies

A
Anonymous
January 8, 2013
Good question, that I've wondered myself, but I don't know the answer, so I am subscribing.
A
Anonymous
January 8, 2013
Could you check:

1. Anonymous leads
2. Field Mapping and data in Admin
A
Anonymous
January 8, 2013
Neither one of Josh's suggestions will help. This has been something I created a ticket for years ago and has never been resolved. It is something that plagues my staff as they get confused and continually reinput fake values. It's a strong place for improvement. 

It isn't linked to cookies, it's like an internal marketo cookie that contains the potential field values. But the first time someone types in junky data it's saved forever! Very great place for improvement!
A
Anonymous
January 8, 2013
Josh, I had already checked the anonymous leads as I thought the values must exist SOMEWHERE in the database. That wasn't the case.

Adam, you know what is bizarre is, when I was normalizing the values last night, some of the 'junky' values were disappearing as I went along and normalized, and some where not. Couldn't figure out what was cuasing the ones to disappear though.

What I'm thinking at this point is to create the proper list of industry values and make them all have an asterisk in front of the value. That way, those will appear first on the list, and it would be unlikely that someone would enter an incorrect value with an asterisk at the beginning. It's a workaround for now anyways...
Terms & ConditionsAccessibility statement

Loading footer...