locked
attachments architecture in crm? RRS feed

  • Question

  • Hello - I'm currently trying to debug an attachments issue in my company's CRM implementation.  To do so it will be helpful for me to understand the architecture of the CRM attachments functionality. There are 2 most likely approaches:

    1. The file is saved as a byte[] to the database. The file is returned to the client as a byte stream.
    2. The file is stored on the file system and a pointer to the file is stored in the database.  When the file is requested a lookup is performed in the database to get the pointer and then the file is returned directly from the server filesystem.

    Can anyone here validate which approach CRM 2011 uses as its architecture for managing system attachments?

    Tuesday, January 22, 2013 11:20 PM

Answers

  • It is closer (but slightly different) to (1).

    Uploaded files are converted from a Byte Stream into a Base64 encoded string.  That string is stored in the Body attribute of the ActivityMimeAttachment entity.

    Downloaded files are converted back from Base64 into a Byte Stream before being sent to the client.


    --pogo (pat) @ pogo69.wordpress.com

    Wednesday, January 23, 2013 1:06 AM

All replies

  • It is closer (but slightly different) to (1).

    Uploaded files are converted from a Byte Stream into a Base64 encoded string.  That string is stored in the Body attribute of the ActivityMimeAttachment entity.

    Downloaded files are converted back from Base64 into a Byte Stream before being sent to the client.


    --pogo (pat) @ pogo69.wordpress.com

    Wednesday, January 23, 2013 1:06 AM
  • Hello dotnetteramg123,

    Hope this might be helpfull.


    Thanks and Regards. Make sure to "Vote as Helpful" and "Mark As Answer",if you get answer of your question.

    Wednesday, January 23, 2013 4:52 AM
  • thanks pogo - that was educational
    Wednesday, January 23, 2013 6:21 PM