Skip to main content
SFDC Developers
DevOps

Property 'encrypted' not valid

Vinay Vernekar · · 1 min read

Recently while deploying the metadata of custom object from RQA sandbox to UAT sandbox, compiler threw following error:

Property 'encryption Scheme' not valid in version 45.0

Upon researching I found, if you are deploying to an instance that's still on v43.0 (on summer 18) then remove the line that has encryption scheme property.

Following markup threw an error while deployment through Ant:

<?xml version="1.0" encoding="UTF-8"?>
<CustomObject xmlns="http://soap.sforce.com/2006/04/metadata">
<fields>
        <fullName>DueDate__c</fullName>
        <deprecated>false</deprecated>
        <encrypted>false</encrypted>
        <externalId>false</externalId>
        <label>Due Date</label>
        <required>false</required>
        <trackFeedHistory>false</trackFeedHistory>
        <trackHistory>false</trackHistory>
        <trackTrending>false</trackTrending>
        <type>Date</type>
</fields>
</CustomObject>

Just remove the "encrypted" tag from markup, so new markup looks like:

<?xml version="1.0" encoding="UTF-8"?>
<CustomObject xmlns="http://soap.sforce.com/2006/04/metadata">
<fields>
        <fullName>DueDate__c</fullName>
        <deprecated>false</deprecated>
        <externalId>false</externalId>
        <label>Due Date</label>
        <required>false</required>
        <trackFeedHistory>false</trackFeedHistory>
        <trackHistory>false</trackHistory>
        <trackTrending>false</trackTrending>
        <type>Date</type>
</fields>
</CustomObject>

Hope this resolved your issue.

Share this article

Vinay Vernekar

Vinay Vernekar

Salesforce Developer & Founder

Vinay is a seasoned Salesforce developer with over a decade of experience building enterprise solutions on the Salesforce platform. He founded SFDCDevelopers.com to share practical tutorials, best practices, and career guidance with the global Salesforce community.

Comments

Loading comments...

Leave a Comment

Trending Now