After deploying a customized version of a screen (where the underlying form name changes, for example from frmXXXXX to frmXXXXX_Cust), users with a Base Profile that has layout entries still referencing the OLD form name see the standard, non-customized form load instead of the new customized one — removing the Base Profile entirely lets the customized form load correctly. Is there a fix that doesn't require abandoning the Base Profile?

Question

After deploying a customized version of a screen (where the underlying form name changes, for example from frmXXXXX to frmXXXXX_Cust), users with a Base Profile that has layout entries still referencing the OLD form name see the standard, non-customized form load instead of the new customized one — removing the Base Profile entirely lets the customized form load correctly. Is there a fix that doesn't require abandoning the Base Profile?

Accepted Answer

This is a real limitation rather than a misconfiguration — a Base Profile (or Personal Profile) with layout/configuration entries recorded against the OLD form name doesn't automatically get updated to reference the new customized form name after deployment, since the profile's stored entries are keyed off the specific form name they were originally saved against. The confirmed workaround: export the affected Base Profile, and any affected Personal Profiles, as XML, find-and-replace every occurrence of the old form name with the new customized form name directly in the exported XML, and re-import it. Alternatively, if the specific customized screen's existing profile settings aren't critical to preserve, simply delete the old form-name branch from the profile instead and let a fresh configuration be created going forward for that screen.

Answer