Metadata Deployments do not correctly prevent the removal of LookupFilters on managed-released Custom Fields

Apex , API , AppExchange , Metadata , Eclipse IDE

Last updated 2014-12-23 ·Reference W-2257558 ·Reported By 5 users

Fixed - Winter '15

Summary
Metadata Deployments do not correctly prevent the removal of LookupFilters on managed-released Custom Fields.

It is possible using Eclipse/ANT to remove lookup filters on managed released components, which then causes an error on package upgrades.
The package upgrade process tries to delete the lookup filter but cannot.

The expected behaviour should be the same as when using the UI, i.e. the deletion should be blocked.

Repro
1. In a clean DE org, add a custom lookup field on Contact related to Account
2. Define a Lookup Filter for the field (e.g. Account:IsActive = true)
3. Upload a managed released package that contains the field.
4. Through the UI, try to edit the field and remove the lookup filter (note the message 'Cannot Delete Managed Component' which is expected).
5. Now try an ant deployment which contains the Contact.object metadata with the <lookupFilter/> removed.
6. Note that you can successfully remove the filter via the ant deployment.
7. The impact here is that there is an 'Orphaned' LookupFilter in the org.

If you attempt to add the lookup filter back in by editing the custom field through the UI, you will get a Unique Constraint Violation.

The implications are also seen by customers upgrading to a new version of the package with the filter removed:
- During package upgrade if we detect deleted components we delete them from the org.
- The problem here is that lookup filters are not supported by managed component deletion, so we get error.

Workaround
As a workaround, contact Salesforce Support/R&D so that we can resolve the issue for you.

After that, you will be able to edit the Custom Lookup Field from the UI and add the LookupFilter back in.

You will then need to upload a new released version of the package to be installed by your customers.

Partners should be advised that until this issue is resolved, they should be careful when deploying components via ant or Force.com IDE, to ensure they do not remove any existing lookup filters from their lookup fields.

Is it Fixed?

AP0 AP3 AP4 AP5 AP6 AP7 AP8 AP9 AP10 AP11 AP12 AP13 AP14 AP15 AP16 AP17 AP18 AP19 AP20 AP21 AP22 AP28 CS1 CS2 CS3 CS4 CS5 CS6 CS7 CS8 CS9 CS10 CS109 CS108 CS107 CS106 CS105 CS102 CS101 CS100 CS115 CS110 CS117 CS114 CS113 CS112 CS111 CS11 CS116 CS12 CS129 CS128 CS125 CS124 CS123 CS137 CS138 CS13 CS133 CS132 CS14 CS148 CS142 CS15 CS152 CS151 CS16 CS17 CS18 CS19 CS20 CS21 CS22 CS23 CS24 CS25 CS26 CS27 CS28 CS29 CS30 CS31 CS32 CS33 CS34 CS35 CS36 CS37 CS40 CS41 CS42 CS43 CS44 CS45 CS47 CS50 CS51 CS52 CS53 CS54 CS57 CS58 CS59 CS60 CS61 CS62 CS63 CS64 CS65 CS66 CS67 CS68 CS69 CS70 CS71 CS72 CS73 CS74 CS75 CS76 CS77 CS78 CS79 CS80 CS81 CS82 CS83 CS84 CS85 CS86 CS87 CS88 CS89 CS90 CS91 CS92 CS93 CS94 CS95 CS96 CS97 CS98 CS99 EU7 EU8 EU10 EU12 EU13 EU14 EU15 EU16 EU17 EU18 EU19 EU25 EU26 EU27 EU28 EU29 EU30 EU31 EU32 NA104 NA107 NA109 NA100 NA101 NA103 NA102 NA105 NA119 NA116 NA110 NA118 NA112 NA111 NA115 NA114 NA113 NA117 NA121 NA124 NA122 NA120 NA126 NA129 NA130 NA134 NA136 NA135 NA132 NA131 NA146 NA142 NA141 NA154 NA155 NA171 NA174 NA196 NA21 NA32 NA37 NA39 NA44 NA45 NA46 NA47 NA49 NA52 NA53 NA54 NA57 NA58 NA59 NA60 NA61 NA62 NA64 NA65 NA66 NA67 NA68 NA69 NA70 NA71 NA72 NA73 NA74 NA75 NA76 NA77 NA79 NA80 NA81 NA82 NA83 NA84 NA85 NA86 NA87 NA88 NA89 NA90 NA91 NA92 NA93 NA94 NA95 NA96 NA97 NA98 NA99 UM1 UM2 UM3 UM4 UM5

Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.