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
Trailblazer Community

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

Custom Object pages deployed in a community ( 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

Reproducible in any org by deploying (Metadata API or changesets) for a 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="">
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.

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 AP24 AP25 AP26 AP27 AP28 AUS14S AUS18S AUS16S AUS13 AUS11 AUS1 AUS28S AUS20S AUS27 AUS26S AUS25 AUS24S AUS23 AUS22S AUS2S AUS36S AUS38S AUS3 AUS4S AUS47 AUS43 AUS5 AUS58 AUS6S AUS64 AUS62 AUS60 AUS7 AUS77 AUS75 AUS9 BRA1 BRA2S BRA3 BRA4S BRA5 BRA6S BRA8S CAN1 CAN17 CAN11 CAN25 CAN2S CAN20S CAN29 CAN28 CAN27 CAN26 CAN34 CAN4S CAN6S CAN8S CS1 CS2 CS4 CS5 CS6 CS100 CS109 CS108 CS107 CS106 CS105 CS102 CS101 CS115 CS119 CS110 CS117 CS114 CS113 CS112 CS111 CS116 CS123 CS122 CS121 CS126 CS127 CS129 CS128 CS125 CS124 CS137 CS138 CS133 CS132 CS14 CS148 CS142 CS159 CS152 CS151 CS15 CS162 CS167 CS166 CS169 CS165 CS160 CS173 CS17 CS172 CS170 CS171 CS174 CS189 CS194 CS192 CS193 CS190 CS191 CS199 CS197 CS19 CS198 CS196 CS195 CS20 CS209 CS200 CS202 CS201 CS203 CS21 CS219 CS218 CS217 CS216 CS215 CS214 CS213 CS212 CS211 CS210 CS22 CS220 CS226 CS224 CS222 CS225 CS223 CS221 CS237 CS234 CS238 CS23 CS24 CS242 CS248 CS247 CS241 CS245 CS244 CS243 CS249 CS246 CS252 CS250 CS25 CS251 CS26 CS264 CS263 CS27 CS28 CS29 CS308 CS31 CS32 CS33 CS34 CS35 CS364 CS36 CS365 CS37 CS40 CS41 CS42 CS43 CS44 CS45 CS47 CS57 CS58 CS59 CS60 CS61 CS62 CS63 CS67 CS69 CS72 CS73 CS74 CS75 CS76 CS77 CS78 CS79 CS80 CS81 CS84 CS86 CS87 CS88 CS89 CS92 CS94 CS95 CS96 CS97 CS98 CS99 DEU10S DEU13 DEU11 DEU1 DEU16S DEU14S DEU12S DEU2S DEU20S DEU25 DEU36 DEU3 DEU38 DEU46 DEU4S DEU48S DEU5 DEU52 DEU50S DEU6S DEU8S EU16 EU17 EU18 EU19 EU25 EU26 EU27 EU28 EU29 EU30 EU31 EU32 EU33 EU34 EU35 EU36 EU37 EU38 EU39 EU40 EU41 EU42 EU43 EU44 EU45 EU46 EU47 EU48 FRA12S FRA19 FRA1 FRA11 FRA24S FRA2S FRA32 FRA36 FRA34 FRA4S FRA5 FRA6S FRA7 FRA8S FRA9 GBR1 GBR2S GBR4S IND14S IND17 IND19 IND18S IND16S IND15 IND13 IND11 IND1 IND12S IND10S IND20S IND27 IND25 IND21 IND23 IND2S IND28S IND26S IND24S IND22S IND37 IND3S IND39 IND41 IND47 IND4S IND43 IND54S IND5 IND6S IND7 IND8S IND9 JPN18S JPN12S JPN10S JPN1 JPN19 JPN17 JPN20S JPN2S JPN21 JPN28S JPN24S JPN22S JPN3 JPN4S JPN5 JPN6S JPN7 JPN8S KOR1 KOR2S KOR4S NA104 NA107 NA109 NA100 NA101 NA103 NA102 NA105 NA119 NA116 NA110 NA118 NA112 NA111 NA115 NA114 NA113 NA117 NA125 NA124 NA122 NA120 NA126 NA127 NA123 NA129 NA121 NA128 NA138 NA134 NA133 NA136 NA135 NA132 NA131 NA130 NA137 NA139 NA140 NA142 NA141 NA149 NA146 NA147 NA148 NA154 NA158 NA159 NA153 NA151 NA155 NA152 NA150 NA156 NA161 NA163 NA167 NA160 NA166 NA165 NA169 NA164 NA168 NA162 NA172 NA170 NA174 NA171 NA173 NA196 NA207 NA204 NA206 NA208 NA209 NA21 NA218 NA214 NA217 NA215 NA211 NA212 NA213 NA210 NA219 NA223 NA226 NA224 NA225 NA70 NA71 NA75 NA80 NA81 NA82 NA83 NA84 NA85 NA89 NA90 NA91 NA92 NA93 NA94 NA95 NA96 NA97 NA98 NA99 SGP10 SGP1 SGP2S SGP3 SGP4S SGP6S SGP8S SWE1 SWE2S SWE4S UM1 UM2 UM3 UM4 UM5 UM6 UM7 UM8 UM9 USA194S USA13 USA198S USA196S USA1 USA19 USA17 USA15 USA20S USA26 USA28S USA2S USA222S USA220 USA22S USA3S USA32S USA30S USA36 USA34 USA59 USA60S USA61 USA62S USA7 USA8S

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.