Allow fieldmaps to be enabled/disabled

Is this duplicate of my #976862: Add the ability to mark fieldmaps as disabled?

I guess that one's newer, but it has more detail.

Here's my text from that issue. Flagged it as duplicate:

This is actually both a UI and API request. I have noticed now that the default fieldmaps are showing up for Salesforce API (they weren't before), that I have a bunch of fieldmaps that I don't want to use for my exports. I would like to be able to set certain ones (such as the defaults) to be disabled.

disabled would be a boolean property of the $fieldmap object, i.e., $fieldmap->disabled.

When disabled, fieldmaps would appear on the fieldmaps tab to be greyed out until reenabled, and when salesforce_api_salesforce_field_map_load_all() was called, they would not be returned unless the optional $show_disabled parameter was passed, set to TRUE.

This would also help me in my work with uc_sf_order.module since the dropdowns can get confusing if there a lot of different choices for field mapping. I'm writing a patch today that will mitigate this issue by including part of the user-provided description for each fieldmap in the select box, but it could still be improved by letting people disable fieldmaps entirely.

If I have time, I may write a patch for this, if you think it is a good idea.

Sorry I haven't worked on this yet. Maybe we can get it into D7 soon, and then backport.

subscribe. also i think this is useful for the (default) fieldmaps examples for the Basic Page and User

Let's get this into 7.x-3.x once #1439400: Provide enabled/disabled state handling in Entity API is resolved.

I don't believe this request actually makes sense anymore with the 7.x-3.x version. There's also been no further interest in it. Closing.