---
schema_version: "1"
id: 8d7bdd429ddf94060ab3d549d84efbd861c9a4590fbc0c3b72372842f934a067
title: Update LifeSciConfigRecord Files for New Profile Naming Format
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/262-0-0/rn_lsc_customer_engagement_update_profile_assignments_config_deployments.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_lsc_customer_engagement_update_profile_assignments_config_deployments.htm&release=262.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 520faf419d897eb759d381f2efd9695d23b9403c1bc8668d4306cd50bb5c3525
description: LifeSciConfigRecord metadata files now use human-readable file names instead of org-specific profile IDs for profile-level and user-level configuration records in hierarchical categories. Records that follow the [CategoryName]_[ProfileId or UserId] naming convention, such as those created through the Admin Console, are affected. The assignedTo field on LifeSciConfigRecords with a custom profile assignment also includes a Custom- prefix. These changes prevent duplicate record errors and failed deployments when you move configuration records between orgs.
products:
  - Cross Cloud
release: "262"
---
# Update LifeSciConfigRecord Files for New Profile Naming Format

LifeSciConfigRecord metadata files now use human-readable file names instead of org-specific profile IDs for profile-level and user-level configuration records in hierarchical categories. Records that follow the `[CategoryName]_[ProfileId or UserId]` naming convention, such as those created through the Admin Console, are affected. The `assignedTo` field on LifeSciConfigRecords with a custom profile assignment also includes a `Custom-` prefix. These changes prevent duplicate record errors and failed deployments when you move configuration records between orgs.

**Where:** This change applies to Lightning Experience in Enterprise and Unlimited editions with the Life Sciences Cloud license and the Life Sciences Cloud for Customer Engagement add-on license, and where the Life Sciences Cloud for Customer Engagement managed package is installed.

**Who:** This change affects admins and developers who retrieve and deploy LifeSciConfigRecord metadata between orgs by using Metadata API or Salesforce CLI.

**Why:** Previously, LifeSciConfigRecord files for hierarchical-type categories with profile or user assignments included org-specific profile or user IDs in the file name, for example, `AccountSearchSettings_00eXXXXXXXXXXXXYAE`. Because IDs differ between orgs, deploying these files to another org created duplicate records or caused validation errors instead of updating the existing configuration.

**How:** When you retrieve LifeSciConfigRecord metadata for hierarchical-type categories from a Summer '26 org, file names use this format:

- Standard profile: `{Category}-{ProfileName}.lifeSciConfigRecord`
- Custom profile: `{Category}-Custom-{ProfileName}.lifeSciConfigRecord`
- User-level: `{Category}-User-{Username}.lifeSciConfigRecord`

For any LifeSciConfigRecord with a custom profile assignment, the `assignedTo` field also includes a `Custom-` prefix, for example, `Custom-Medical Sales Representative`. Standard profiles don't require a prefix.

To update existing files, rename the files to match the new format and add the `Custom-` prefix in the `assignedTo` field as applicable. Or, retrieve the metadata from a Summer '26 org to get files in the correct format automatically.

During deploy, Salesforce detects the marker in the file name and resolves the profile or username to the correct ID on the target org. If a matching record exists, it's updated. If no match exists, a new record is created.

#### See Also

- [_Life Sciences Cloud Developer Guide_: LifeSciConfigRecord](https://developer.salesforce.com/docs/atlas.en-us.life_sciences_dev_guide.meta/life_sciences_dev_guide/meta_lifesciconfigrecord.htm)