---
schema_version: "1"
id: 286c407900d07b22acdd40162b5a68e76977230d93039a89916d040fd198b06a
title: sfdcRegister Transformation
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/analytics/264-0-0/bi_integrate_register_transformation.md
canonical_url: https://help.salesforce.com/s/articleView?id=analytics.bi_integrate_register_transformation.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 6676132f8519dbbca0e917aeaf45887a525989a52d34e8c29fdc1d920afaec13
description: The sfdcRegister transformation registers a dataset to make it available for queries. Users can’t view or run queries against an unregistered dataset.
products:
  - CRM Analytics
  - Cross Cloud
release: "264"
---
# sfdcRegister Transformation

The sfdcRegister transformation registers a dataset to make it available for queries. Users can’t view or run queries against an unregistered dataset.

The sfdcRegister transformation overwrites the current version of the dataset.

You don’t need to register all datasets. For example, you don’t need to register an intermediate dataset that is used to build another dataset and doesn’t need to be queried. In addition, you don’t need to register datasets that are created when you upload external data because CRM Analytics automatically registers these datasets for you.

Carefully choose which datasets to register because:

- The total number of rows in all registered datasets can’t exceed 100,000 per platform license, or 250 million per platform license _purchased before_ October 20, 2015.
- Users that have access to registered datasets can query their data. But you can apply row-level security on a dataset to restrict access to records.

![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-analytics-bi-264-0-0-production-enus/ec791473-f5b4-4f64-a656-9104f455d966/images/icon_example.png)

Example Let’s look at an example. You create a dataflow that extracts opportunities from the Opportunity object. To register the dataset, name it "Opportunities," and apply row-level security on it, you add the sfdcRegister transformation as shown in the following dataflow definition file.

```
{
   "Extract_Opportunities": {
      "action": "sfdcDigest",
      "parameters": {
         "object": "Opportunity",
         "fields": [
            { "name": "Id" },
            { "name": "Name" },
            { "name": "Amount" },
            { "name": "StageName" },
            { "name": "CloseDate" },
            { "name": "AccountId" },
            { "name": "OwnerId" }
         ]
      }
   },
   "Register_Oppportunities_Dataset": {
      "action": "sfdcRegister",
      "parameters": {
         "alias": "Opportunities",
         "name": "Opportunities",
         "source": "Extract_Opportunities",
         "rowLevelSecurityFilter": "'OwnerId' == "$User.Id""
      }
   }
}
```

- **[sfdcRegister Parameters](https://help.salesforce.com/s/articleView?id=analytics.bi_integrate_register_transformation_operation.htm&release=264.0.0&type=5)**  
    When you define an sfdcRegister transformation, you set the action attribute to `sfdcRegister` and specify the parameters.