DgtAssetMgmtPrvdLghtCpnt Metadata Type in SFDX

Architectural Overview#

The DgtAssetMgmtPrvdLghtCpnt (Digital Asset Management Provider Lightning Component) metadata type associates custom Lightning Web Components (LWC) with an external DgtAssetMgmtProvider. While the provider metadata defines API credentials and endpoints, the user experience of browsing external media—such as filtering by brand campaign, viewing copyright statuses, or selecting asset renditions—requires specialized UI elements.

By deploying DgtAssetMgmtPrvdLghtCpnt metadata, architects replace standard placeholder file selectors with rich interactive LWC modals inside Salesforce CMS content authoring editors, ensuring seamless asset embedding across digital channels.

SFDX Directory and File Suffix#

Key Metadata Fields#

Declarative XML and Package.xml Examples#

DgtAssetMgmtPrvdLghtCpnt Metadata File#

<?xml version="1.0" encoding="UTF-8"?>
<DgtAssetMgmtPrvdLghtCpnt xmlns="http://soap.sforce.com/2006/04/metadata">
    <componentType>AssetPicker</componentType>
    <description>Connects the custom Bynder asset picker LWC to the Bynder DAM provider.</description>
    <dgtAssetMgmtProvider>Enterprise_Bynder_DAM</dgtAssetMgmtProvider>
    <lightningComponent>c:bynderAssetPickerModal</lightningComponent>
    <masterLabel>Bynder Picker Binding</masterLabel>
</DgtAssetMgmtPrvdLghtCpnt>

package.xml Manifest#

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>Bynder_Picker_Binding</members>
        <name>DgtAssetMgmtPrvdLghtCpnt</name>
    </types>
    <version>68.0</version>
</Package>

SFDX CLI Retrieval and Deployment Commands#

Retrieve and deploy component bindings alongside the associated LWC bundle:

# Retrieve all DAM component bindings
sf project retrieve start --metadata "DgtAssetMgmtPrvdLghtCpnt" --target-org cms-dev

# Deploy the component binding, provider, and LWC bundle together
sf project deploy start \
  --metadata "LightningComponentBundle:bynderAssetPickerModal,DgtAssetMgmtProvider:Enterprise_Bynder_DAM,DgtAssetMgmtPrvdLghtCpnt:Bynder_Picker_Binding" \
  --target-org uat-org

# Query registered DAM Lightning components via Tooling API
sf data query --use-tooling-api --query "SELECT Id, DeveloperName, DgtAssetMgmtProviderId, ComponentType FROM DgtAssetMgmtPrvdLghtCpnt" --target-org uat-org

Senior Architect Best Practices and Gotchas#

• Cross-Origin Resource Sharing (CORS): Ensure external asset thumbnail and preview URLs rendered by the LWC are permitted under the target org’s CORS and CSP configurations.
• Graceful Error States: Implement fallback UI states inside the LWC in the event the third-party DAM API experiences transient latency or token expiration during editorial sessions.

Frequently asked questions

What is the function of DgtAssetMgmtPrvdLghtCpnt metadata?

It binds a custom Lightning Web Component to a registered DAM provider, providing a tailored search and asset picker modal inside Salesforce CMS.

Where are DgtAssetMgmtPrvdLghtCpnt components stored in an SFDX project?

They are stored in force-app/main/default/dgtAssetMgmtPrvdLghtCpnts with the file suffix .dgtAssetMgmtPrvdLghtCpnt-meta.xml.

Does DgtAssetMgmtPrvdLghtCpnt require a custom Lightning Web Component?

Yes. The lightningComponent field must reference a deployed LightningComponentBundle designed to interact with the DAM provider adapter API.