CURIOUSRUBIK
Let’s talk about your next move ↗View complete sitemap
Back to the blog

Make custom record available for Import Assistant

If a custom record type is missing from the CSV Import Assistant for your role, check both CSV-import permission and access to that specific custom record type. Available imports also depend on enabled features. See Oracle’s CSV import requirements.

Oracle documentation reviewed. Validate the change using the affected role and your account’s access model.

Check the importing role

  1. Ask an administrator to open Setup > Users/Roles > Manage Roles and edit the custom role used for the import.
  2. Under Permissions > Setup, check Import CSV File. Oracle requires Full access for the Import Assistant. Follow the CSV-permission setup instructions.
  3. Check the target record type’s Access Type at Customization > Lists, Records, & Fields > Record Types before changing custom-record permissions.

Match the record’s access model

  • Require Custom Record Entries Permission: Review the role’s Permissions > Lists > Custom Record Entries level. This is a broad custom-record permission; approve its scope before granting it.
  • Use Permission List: Grant the role access to the intended type through the record type’s Permissions subtab, or the role’s Permissions > Custom Records subtab.
  • No Permission Required for Internal Roles: Internal roles already have access under this model, subject to any additional custom controls. Do not switch a restricted type to this mode merely to make an import work.

These are different permission models. The record-type owner also has special access, so test using the affected user’s role rather than relying on the owner’s result. See Oracle’s custom-record permission models.

Choose the level for the intended operation

Under Oracle’s general access-level definitions, Create permits new records but does not permit editing existing records; Edit permits both. Create alone must not be treated as sufficient for an import that updates existing entries. Have the administrator validate the required record access for Add, Update or Add or Update, using the least access needed. See access levels for permissions.

After approved permission changes, save and have the affected user sign out and back in. Oracle documents this refresh step in Setting Permissions for Custom Records.

Verify availability before importing

Return to the Import Assistant and choose the Custom Records import type. Confirm that the intended existing record type appears and that your selected operation matches the authorized work. The Import Assistant imports entries into an existing custom record type. See Custom Records Import.

If the type is still missing, ask the administrator to review the enabled Custom Records feature, record-type configuration and restrictions. Test any approved change with a small, reviewed file in a safe environment before importing production data.

What’s on your mind?

A little context is all it takes to begin.

Please leave out passwords, payment details and confidential account data.