We just updated the method for calculating some fields on some of our standard Sales Cloud objects. These have different API names but, importantly for UX, the same label as before.
When these are ingested into the DLO in Data Cloud, the old fields can be disabled in the DLO using their API name, but in the mapping tool on both visual and table views only the label is visible, so it's impossible to know which field you are mapping. There's also no option to edit the label.
My suggestion is that the API name be visible in the table view of the Mapping Tool, or that disabled fields do not appear in the Mapping Tool, or both.
Does anyone have another solution? I've already been through SF support which didn't find one but I'm wondering if there is one you've come across.
Thanks Sandip. Unfortunately the source is Sales Cloud and the original field is now deleted. So there's no way to remove the ambiguity without altering how the new field is displayed to Sales Cloud users, and the labels are identical. I also found that the fields were in a different order when comparing the mapping tool and the DLO view.
