The Data Wizard only displays objects that meet specific visibility and accessibility criteria. The most common reason an object doesn't appear is that it lacks an associated tab. The Data Wizard filters objects based on tab visibility. Objects must have a tab configured and visible to the current user's profile or app to appear in the object selection list.

How do I make an object appear in the Data Wizard?

Follow these steps in Salesforce Setup:

Step 1: Create a Tab (if one doesn't exist)

1. Go to Setup → User Interface → Tabs
2. Click New in the Custom Object Tabs section
3. Select your object from the dropdown
4. Choose a tab style and click Next
5. Set visibility for profiles (or make visible to all)
6. Choose which apps should include the tab
7. Click Save

Step 2: Verify Tab Visibility

1. Go to Setup → Users → Profiles
2. Find the user's profile (or Permission Set)
3. Click Edit or Object Settings
4. Find your object in the list
5. Ensure Tab Settings shows "Default On" or "Available"

Step 3: Add Tab to App (if needed)

1. Go to Setup → App Manager
2. Find the app the user is working in
3. Click Edit
4. Add the object tab to Selected Items
5. Click Save

Step 4: Refresh the Data Wizard

1. Log out and back in (or refresh the browser)
2. Navigate back to the Data Wizard
3. The object should now appear in the dropdown

What other reasons might cause an object to not appear?

1. Permission Issues

The user must have Read access to the object:

• Check Profile → Object Settings → [Your Object] → Read permission
• Check Permission Sets assigned to the user
• Verify Field-Level Security (FLS) allows access to fields

2. Object Not Queryable

Some objects cannot be queried via SOQL:

• System objects with restricted access
• Objects marked as not queryable in metadata
• Objects without any accessible fields

3. Managed Package Objects

Objects from managed packages (like sfLma__License__c) may not appear if:

• The package isn't fully installed
• The namespace isn't accessible
• Package licenses or permissions aren't assigned
• The package admin hasn't exposed the object

4. API Accessibility

The object must be accessible via the Salesforce API:

• Check if the object is marked as "Available for API" in metadata
• Some deprecated objects may have limited API access

5. Object Type Restrictions

Certain object types are intentionally filtered:

• System or administrative objects
• Objects without email fields (for email marketing integrations)
• Objects that don't support list views
• Objects marked as hidden or deprecated

Why doesn't the LMA "Licenses" object (sfLma__License__c) appear?

The License Management App (LMA) Licenses object is an administrative object that typically doesn't have a tab configured by default. This is intentional because:

1. Administrative Purpose - It tracks license usage and is meant for vendor/ISV use, not end users
2. No Default Tab - The LMA package doesn't create a tab for the Licenses object
3. Not Designed for Data Import - License data isn't typically imported into email marketing platforms
4. Security - Exposing license information broadly could create security concerns

If you need access to License data:

• Consider if this is the right use case for your email marketing integration
• Create a custom tab for sfLma__License__c if absolutely needed
• Explore alternative solutions like Custom Reports or Flows to extract license data

Can I bypass the tab requirement?

No. The tab requirement is built into the wizard's object filtering logic for good reasons:

1. User Experience - Ensures users only see objects they actively work with
2. Security - Respects Salesforce's permission and visibility model
3. Relevance - Filters out system/administrative objects not suitable for data imports
4. Performance - Reduces the object list to a manageable, relevant set

Alternative Approach: If you need to import data from an object without a tab, consider:

• Using Custom SOQL option in the wizard (if available)
• Creating a List View first, then using the List View import option
• Using Reports to filter and import the data you need
• Building a Flow or Process Builder to move data to a more appropriate object

How do I troubleshoot object visibility issues?

Troubleshooting Checklist: