Requirements and restrictions for case attachments in a file storage repository

You can configure your application to store case attachments in a repository. Consider the following requirements and restrictions to ensure that your attachments are stored and retrieved correctly from a repository.


  • You must use the D_pxGetFile API to access the contents of an attachment.
  • Your email listener service package must enforce basic authentication.
  • Your email listener must be configured with an operator whose primary application uses the repository that your application uses.


  • Repositories support file attachments only. All other types of attachments are stored in a database.
  • You cannot change the content storage type from repository to a different type.
  • Once you switch from database storage to repository storage, you cannot switch back to database storage without losing access attachments stored in the repository.
  • You cannot modify the configuration of a repository after the repository is in use.
  • Application attachments that you provide on the application form are always stored in a database.
  • Because the application pulse gadget cannot prompt for authentication details, pulse attachments that you provide on the Application Overview landing page are stored in the repository only when your session is already authenticated or when the repository supports non-interactive authentication. If neither of these conditions is true, then an error occurs and the operation fails.

Difference between database storage and repository storage

When using database storage, you can attach multiple files with the same name to the same case. For external storage, you cannot attach multiple files with the same name to the same case because storage providers treat the file name plus the path as a key. Attempting to attach more than one file with the same name to a case results in an error. You can, however; attach files with the same name to different cases.