ZipSupport In Apex

-

The ZIP Support (Developer Preview) feature is currently available as a Developer Preview. You can create and extract ZIP archive files using the classes and methods in the Compression namespace. 

However, this feature is not yet generally available unless Salesforce announces its general availability in documentation or public statements. 

Features, commands, and parameters may change or be removed at any time without notice. Salesforce recommends avoiding the use of compression methods in a production environment.

With this feature, you can compress multiple attachments or documents into an Apex blob that contains the ZIP archive. You can also extract specific data from the ZIP archive without having to uncompress the entire archive. To optimize compression, you can specify a compression method and compression level.

This feature is available in scratch orgs where the ZipSupportInApex feature is enabled. If the feature isn’t enabled, Apex code with this feature can be compiled but not executed.

You must enable support for zip file processing by adding ZipSupportInApex to the features property in your scratch org definition. "features": ["ZipSupportInApex"]

Sinppet of a Location Records

File Name - LocationB2B.csv





Here's an Example

Zip a File

ContentVersion cv = [SELECT PathOnClient, Versiondata, Title

                           FROM ContentVersion
                           WHERE Title = 'LocationData' Limit 1];

Compression.ZipWriter writer=new Compression.ZipWriter();
    writer.addEntry(cv.PathOnClient,cv.versiondata);
    Blob zipFile=writer.getArchive();
 
    ContentVersion contentVersion = new ContentVersion(
        VersionData =zipFile,
        Title = cv.Title,
        PathOnClient = cv.Title+'.zip'
    );
Insert contentVersion;

UnZip a File

ContentVersion cv = [SELECT PathOnClient, Versiondata, Title
                           FROM ContentVersion
                           WHERE Title = 'LocationData.zip' Limit 1];

Blob zipBody = contentVer.VersionData;
    Compression.ZipReader reader = new Compression.ZipReader(zipBody);
    Compression.ZipEntry csvEntry = reader.getEntry(cv.Title+'.csv');
    Blob csv = reader.extract(csvEntry);
 
    System.debug('Location CSV body = ' + csv.toString()); // Retrive content of Locatin CSV File

Comments

Post a Comment

Popular posts from this blog

Introduction to Salesforce Agent Script: Build Predictable AI Agents

-
Image
Please visit here for more details - https://ayaninsights.com/guestblogs/introduction-to-agent-script/ In my latest blog, I introduce Salesforce Agent Script and explain how it helps teams build AI agents that are more predictable, controlled, and aligned with business processes. Large language models are flexible, but relying only on natural-language instructions can sometimes produce inconsistent results. Agent Script addresses this challenge by combining the conversational capabilities of an LLM with structured business logic. The blog explains how developers can use conditions, variables, actions, topics, and transitions to control how an Agentforce agent behaves. Agent Script supports familiar logic such as if/else conditions, value comparisons, sequential actions, and checks for missing data. I also cover its core structure, including system settings, configuration, global variables, languages, connections, and topic blocks. The start_agent topic acts as the entry point for each...
Read more

Anti-Patterns in Salesforce Agentforce: What to Avoid When Building AI Agents

-
Image
Salesforce Agentforce is powerful because it allows teams to build AI agents that can understand user intent, retrieve grounded information, execute actions, and support business workflows across Salesforce. But like any powerful platform, the quality of the implementation matters. A good Agentforce implementation does not start with “How many things can the agent do?" It starts with “What problem should the agent solve reliably?” That is where anti-patterns come in. Anti-patterns are common implementation habits that look useful at first but eventually create confusion, poor user experience, inconsistent answers, or hard-to-maintain agents. Below are some of the most common Agentforce anti-patterns and how to avoid them. 1. Trying to Build One Agent That Does Everything One of the biggest mistakes is designing a single agent to handle every business process, every department, and every possible customer question. At first, this feels efficient. One agent, many use cases. Bu...
Read more

MCP vs. Traditional APIs: Choosing the Right Integration Approach

-
Image
Enterprise integration has traditionally been built around APIs. Applications send structured requests, services process them, and predictable responses are returned. This model has supported everything from payment processing and customer portals to mobile applications and large-scale system integrations. The rise of AI agents introduces a different integration challenge. An AI agent does not always follow a fixed sequence designed in advance. It may need to determine which system to use, discover the operations available to it, gather relevant context, and select the appropriate action based on a user’s request. This is where the Model Context Protocol, or MCP, becomes relevant. MCP and traditional APIs are related, but they solve different problems. APIs expose system capabilities. MCP provides a standardized way for AI applications to discover and use those capabilities as tools and contextual resources. Understanding this distinction is important when designing enterprise AI solut...
Read more