Custom Object pages deployed in a Community via the Metadata API will route to the wrong object if the source and target orgs are not in sync

API , Metadata , Change Sets , Communities

Last updated 2018-05-05 ·Reference W-3928390 ·Reported By 4 users

Fixed - Summer '18

Summary
Custom Object pages deployed in a community (Site.com site or Lightning) via the Metadata API will route to the wrong object if the source and target orgs are not in sync.

This can be a problem for deployment between various environments e.g. sandbox => sandbox, sandbox => production

Repro
Reproducible in any org by deploying (Metadata API or changesets) for a Site.com or Lightning community from one org to another:
1. In the source org:
a. Create a custom object e.g. ObjectA
b. Create a basic Napili community e.g. TestCommunity.
c. Create salesforce object pages for the object from #1a.
d. Perform a Metadata API (workbench or ant) retrieve of the sitedotcom community. An example package.xml:
<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
<types>
<members>TestCommunity1</members>
<name>SiteDotCom</name>
</types>
<version>39.0</version>
</Package>
2. In the target org:
a. Create a custom object with a different name from the one in #1a (e.g. ObjectB). Create a few records for the purposes of testing the community.
b. Create another custom object with the same name as the one from #1a e.g. ObjectA. Create a few records for the purposes of testing the community.
c. Create a basic Napili community with the same name as the one in #1b e.g. TestCommunity.
d. Deploy the package from #1d to this org via the Metadata API (workbench or ant).
3. Preview the custom object pages and notice that the pages will reference the incorrect object i.e. ObjectB instead of ObjectA.

Other issues can arise due to the reliance on the entity prefix. The object pages may not be visible because an org does not contain a custom object with that entity. When the user attempts to create the pages manually, they may be unable to and received an error that indicates the route already exists.

Workaround
Until the issue is fixed, to limit occurrences of the problem, a customer can take the following steps:

1. Prior to creating any custom object pages in community builder, create the necessary custom objects in the production org, then refresh the sandbox environments. This will ensure that all objects in each environment are utilizing the same entity prefix. They can then create their custom object pages in builder, where deploying them between the environment should

2. If they create a new custom object or new custom setting in the source org, manually create the same one in the target org at the same time. The object/setting they create in the target org doesn't need to be configurable or accessible to any user apart from the admin. It would essentially be used as a placeholder to ensure the sequence of entity prefixes will be the same in both environments.

3. If they install a managed package that contains custom objects or settings, install the same package in the target org at the same time. Again, users don't need to be permitted access to the package, as the installation is simply to ensure the sequence of entity prefixes is maintained in both environments.

4. Similarly, deleting an object or uninstalling a managed package prior to creating a new custom object can also result in the entity prefixes being out of sync between environments. If they delete a custom object or uninstall a managed package that contains custom objects or custom settings, they should also remove those same objects from the target environment prior to creating the new object.

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 CS137 CS138 CS13 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 EU29 EU30 EU31 NA104 NA109 NA100 NA101 NA103 NA102 NA105 NA119 NA116 NA110 NA112 NA111 NA115 NA114 NA113 NA117 NA129 NA124 NA122 NA130 NA136 NA135 NA132 NA131 NA146 NA142 NA141 NA154 NA155 NA196 NA21 NA32 NA37 NA39 NA44 NA45 NA46 NA47 NA49 NA51 NA52 NA53 NA54 NA56 NA57 NA58 NA59 NA60 NA61 NA62 NA63 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.