2 posts tagged with "Search Layouts"

You give one profile a different set of search-results columns on an object — a profile search layout — and deploy it to another org. On a custom object, Salesforce rejects it:

Profile Search Layout: profile name - Sales User - is not applicable for object

The layout deployed fine where you built it. In the target, the profile isn't "applicable" for that object — and the error doesn't tell you which of the requirements is missing. On a custom object, a profile is only "applicable" when the object has search enabled, has a custom tab, and the profile has read access to the object — miss any one and the deploy fails. mtdt.io fixes this by flagging the missing tab and read access before you deploy, through Impact Analysis and its Profiles & Permissions check.

You edit a search layout — the columns shown in search results, lookup dialogs, and filters — and then try to move it to another org. Salesforce makes it oddly hard: there's no standalone "Search Layout" to deploy, and if you push just the layout, the Metadata API rejects it. That's because a search layout lives inside the object's metadata rather than as its own component, so Salesforce normally forces you to redeploy the whole object just to move one layout change. mtdt.io fixes this by decomposing the object into separate, selectable items, so the search layout deploys on its own without touching the rest of the object.