Import Management with Access Groups

When you import business objects to use with access groups, for objects that have child objects, you can either import both parent and child objects together, or import them separately.

Examples of objects that have child objects are opportunities and accounts. Whether you import the parent and child objects at the same or separately depends on your business needs and the volume of records you're importing.

Low-Volume Import Use Case

For low-volume imports you can import objects as a single object or as hierarchical records (for example, parent-child records) and you – as the importer – get immediate access to the records, without needing to run the Perform Object Sharing Rules Assignment process.

Note: Only the user performing the import gets immediate access to the records in the UI. Other users still must wait until the Perform Object Sharing Rules Assignment process runs to see the records in the UI.

To use this method where you get immediate access to the records, the Real-Time Transaction Tracking Enabled (ZCA_TRANSACTION_TRACKING_ENABLED) profile option must be set to Yes at site level (which it is by default). See About Setting the Profile Option in this topic for more information.

High-Volume Import Use Case

For high-volume imports, you import parent and child objects separately. To get access to the records in the UI, you need to run the Perform Object Sharing Rules Assignment process.

With this approach, you:
  • Import the parent objects so that the parent records exist before you import the child object records.
  • Run the Perform Object Sharing Rules Assignment process to make sure the parent records are correctly assigned and available.
  • Import the child objects.

About Setting the Profile Option

To set the profile option, navigate to the Manage Administrator Profile Values task in Setup and Maintenance and search for the profile option, Real-Time Transaction Tracking Enabled (ZCA_TRANSACTION_TRACKING_ENABLED).

You can set the profile option at site level or at user level. By default, the site value is Yes. This means that any user who imports single-object records or hierarchial records (in low-volume import only) gets immediate access to those imported records and there's no need to run the Perform Object Sharing Rules process. Other users still must wait until the Perform Object Sharing Rules Assignment process runs.

Also see Profile Option Settings and Need to Run the Process.

Profile Option Settings and Need to Run the Process

Depending on how the profile option, Real-Time Transaction Tracking Enabled, is set at site or user level, you may or may not need to run the Perform Object Sharing Rules Assignment process.

This table describes some possible combinations of profile option settings and whether or not you need to run the Perform Object Sharing Rules process:

Profile Option Settings and the Need to Run the Process

Profile Option Setting at Site Level Profile Option Setting at User Level Run Perform Object Sharing Process Before Importing Child Records?
Y N Yes
N N Yes
Y No record present Not required
N No record present Yes
Y Y Not required
N Y Not required