IO Exception: Exceeded max size limit of 6000000

[axelmdq]

Hi,
Im getting this error when I try to open the Custom metadata Loader application.

IO Exception: Exceeded max size limit of 6000000
Error is in expression '{!checkMdApi}' in component apex:page in page custommetadataloader: Class.MetadataService.MetadataPort.listMetadata: line 9218, column 1
Class.MetadataUtil.checkMetadataAPIConnection: line 30, column 1
Class.CustomMetadataLoaderController.checkMdApi: line 16, column 1

An unexpected error has occurred. Your development organization has been notified.

Do you have any solution for that?
Regards.

[jjurisch]

We are running into this in our org now as well. Has anybody found a solution? Appears to be whatever is being called in
WebServiceCallout.invoke( this, request_x, response_map_x, new String[]{endpoint_x, '', 'http://soap.sforce.com/2006/04/metadata', 'listMetadata', 'http://soap.sforce.com/2006/04/metadata', 'listMetadataResponse', 'MetadataService.listMetadataResponse_element'} ); response_x = response_map_x.get('response_x');
is possibly too large of a file for the Apex heap?

[rachel-cmc]

I am seeing this as well. Any work arounds? My file is 5000 records, and I've been doing individual uploads of batches of this size. This would be my third fourth upload, if I could get it to work.

[jjurisch]

@rachel-cmc - the Custom Metadata tool is no longer supported as of a couple of Salesforce releases - so we were never able to find a workaround and this error. However, using SFDX and Visual Studio code it works much better anyway and doesn't require installing anything on your org - but there is a little bit of a learning curve.

It took us a bit to create our job aid - and can't easily copy here in entirety - but here is hopefully a decent guide to using it. Once it's set up and you've done it 1-2x it becomes much easier.

Pre-Requisites
• Visual Studio Code installed on your local machine
• Salesforce Extensions for Visual Studio Code installed
• SFDX Project Created and Open in Visual Studio
• Org where Custom Metadata Object is deployed is connected as default org
• Customize Application system permission on target org

Installation of Salesforce CLI
Open your browser and navigate to https://developer.salesforce.com/tools/sfdxcli
Download the corresponding version for your operating system
Once downloaded, open the installation file
Install with all of the default options

Installation of Visual Studio Code
Download VSCode at https://code.visualstudio.com/download. Choose the appropriate edition for your computer's operating system - typically Windows.
Install with all default options

Installation of Salesforce Extensions
Launch VSCode
In the App icons, select Extensions icon
Search for Salesforce Extension Pack in the search box

Select and choose "install"
Wait for the installation to complete. This may take some time as it is installing multiple extensions behind the scenes.
Restart VSCode.

Create a SFDX Project
Launch Visual Studio Code (if necessary)
Open the Command Pallette by either using keyboard shortcut of CTRL+SHIFT+P or View > Command Pallete
Enter SFDX to see the commands available

Choose SFDX: Create Project
On the next screen you can choose either Empty or Standard, depending on your preferences. it may be faster to use Empty.
Enter project name. This could be anything, but recommend to use something meaningful to your task at hand.

You'll be prompted to choose a folder where the project should be created. This will create a sub-folder with the project's name. Recommended that you create a folder in your C: drive with C:\sfdx to store all of your projects in one centralized location.

Select the folder you wish to create your project within. This will create the sub-folder and project contents.

Continue on to Authorize a Salesforce Org.

Authorize a Salesforce Org
Launch VSCode if needed.
The org your IDE is connected to will be listed at the bottom status menu. By default if you haven't connected one, you will see 'No Default Org Set'.

Don't see this option? Make sure you have installed all of the needed pieces from SFDX CLI Setup and Installation and Created a SFDX Project. It also sometimes takes a while to activate all of the extensions installed.

Open the Command Pallette
Method #1
Click on the Org name in the Status Bar (or No Default Org Set) as indicated in the screenshot above.
This will automatically open the Command Palette with Authorize an Org options selected.
Select SFDX: Authorize an Org

Method #2
Open the Command Palette by either keyboard shortcut CTRL+SHIFT+P or View > Command Palette.
Enter search term 'Authorize' and select SFDX: Authorize an Org

Configuring A New Org
Choose the type of org you wish to connect to - either Sandbox or Production
Enter an alias you wish to refer to the org by in the UI and future commands.
This will open the Output tab in the IDE with the commands for the CLI. In a moment, this will open a web browser to either login.salesforce.com or test.salesforce.com.
Log in to your org - either using direct login or using 'Use Custom Domain' and entering the name of the org and using SSO.
Once you're logged in, you should see that VSCode now shows the org name you entered in the place for the org. A new icon will also appear named Org Browser in your extensions toolbar.

Creating Your Load File
Use Excel to ensure you don't have any duplicate values. This will save you from errors on future steps.
Create a CSV with the following columns
• Name: This will be used for the DeveloperName as well as the Label. It is not possible to have separate API name from Label in current versions.
• One column for each field using the field API name as the header
o Example: Item__c

• Save this file and place in your SFDX project folder's root.

Download the Custom Metadata Definition Metadata
Use the Org Browser extension of Visual Studio Code to download the Custom Metadata object definition XML file.

Convert the CSV into Custom Metadata Records
• Open the Terminal tab of the console within Visual Studio Code
• Can't see the terminal tab? Press CTRL+` or use View > Terminal to re-display it
In the terminal enter, the following command - replacing the relevant portions with your load file and metadata object name (file name goes AFTER the ".\ and ends at the closing ". Replace the "CaseBroken__mdt" with the metadata table you are referencing in your load. Leave the -t).

sfdx force:cmdt:record:insert -f ".\BC Flag Load FULL_10.20.20.csv" -t CaseBroken__mdt
Explanation
o sfdx force:cmdt:record:insert is command to insert/create new metadata records
o -f flag is the name of the file in quotes
o -t is the API name of the custom metadata. If you omit __mdt it will automatically add it for you

• Once satisfied, hit the enter key.
• If successful, you should see a folder in your project named customMetadata and an XML file for each record.

Deploying Custom MetaData Records to Sandboxes
• Make sure your default org is selected to the right org you want to deploy to
• Right click on the customMetadata folder and choose SFDX: Deploy Source to Org

Doing the folder level will do all files at the same time and either pass/fail together. Even if you have all files selected - if you right click a specific file it will only deploy that 1 file.

Deploying Custom MetaData Records to Production
• Deploying to production is a little more complex, but not impossible.
• You must run all local tests when deploying to production using SFDX CLI. Depending on your org setup/validation rules/test classes, etc you may need to authorize the org as the same user who normally does your production deployments.
• Using the terminal within VSCode, enter the following command

sfdx force:source:deploy --sourcepath c:\metadataLoad\metadataLoader\force-app\main\default\customMetadata --json --loglevel warn -l "RunLocalTests" --wait 120

Explanation of Command
o sfdx force:source:deploy is command to do a deployment
o --sourcepath c:\metadataLoad\metadataLoader\force-app\main\default\customMetadata is the artifact to deploy (entire folder)
o --json is to return response as JSON
o --loglevel is only to display warnings and above
o -l is test parameter to run, specifying to run all Local tests
o --wait is how long it should wait before timing out on waiting for results

You can navigate to the target org's setup area and monitor the deployment by going to Setup > Deployment Status

Troubleshooting
Do your future self and coworkers a favor. Run into an issue that you've solved related to this page? Add the error message and fix/workaround here. You may save countless hours of frustration.
• ERROR running force:cmdt:record:insert: The column Label is not found on the custom metadata type CaseBroken.
o This happens if you have extra columns in your CSV file. Remove any columns that are not directly mapped to a field or used as the name of the metadata.
• sf:INVALID_OPERATION: INVALID_OPERATION: testLevel of NoTestRun cannot be used in production organizations
o This happens if you try to deploy to production org and do not use the terminal to enter the manual commands to specify testing levels. Unsure if there is a shortcut to specify test levels via the UI.

[rachel-cmc]

Thanks for the insight, @jjurisch - I've never used SFDX and am not a developer.... so will definitely be a learning curve! I appreciate your response!