When an SFM does a check for duplicate fields being used it doesn't consider the Namespace of the field. So it will see the following two fields as duplicates:
This has caused multiple customers problems, some with multiple fields on multiple objects.
The duplicate match should consider the namespace.
Nick Sauer Michael Majerus Anita D'Souza Tony Herrington Lauri Mäkinen Sonia Genesse
Spoke with Support last night and this is being looked at currently by SMAX.
Thanks Sonia Genesse, let us know how you get on please.
Latest update from Sonia:
For the short term this is what is being proposed, though they're still looking at other options and involving SF in the conversations.
While the workaround below may work for some, I have integrations setup using Dell Boomi for which SF is integrated to two other applications. This would cause more significant updating on my end, if I where to modify the API names only in SF it wouldn't be as much as a pain.
Change the custom field API name to different from installed package custom field API name
More details on this here: https://success.salesforce.com/answers?id=90630000000DNMeAAO
Proceed with Caution: https://help.salesforce.com/articleView?id=000247975&type=1
Sounds like it was never a "best practice" to create a custom field/label with an already existing SVMXC field. Though in my case, a SMAX Developer created these before my time here.
It has happened to us the other was round, we had custom fields in Salesforce before we has Servicemax, and Servicemax just happened to use the same name.
Hi Richard Lewis
The update I received today from my open Support Case this afternoon.
Engineering has advised they are unit testing a possible fix and verifying the impacted areas. I'll keep you posted with further updates I receive.
Thanks Sonia Genesse, do you have any further updates from Support on this? Can you share your support case number of this so we can push for an update from our side as well?
Hi Richard Lewis
Happy to share the Case # with you all: Case# 00071908.
I asked for an update today, and below is what I received:
"Engineering is in the process of verifying the impacted areas. We are expecting an update tomorrow so I'll be sure to share that with you once I receive it".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.