Solved! Go to Solution.
This is actually a sad story...
But one related question if you don't mind thread necromancy: What is a custom field?
For instance, I see through the API that "MarketoSocialGender" has custom field = true, although that is not a field that any user had created. It's part of Marketo's initial field load. How/why is that "custom"?
When I see issues like these it becomes more and more clear that Adobe views Marketo as a cash cow and has assigned only enough resources to keep it running, rather than actually developing the product and fixing absolute basic UI deficiencies that other product s have had for years.
Marketo is currently a dead product.