Siebel File System – Common mistake made

It is a common mistake that we make, not a problem because of not understanding the File System properly. You can read the following post to get the basic idea of File System.


You are testing on dedicated client and you try to query on Attachment BC or you try to download a file attached in the attachment applet and you get an error “File could not be found on file system”. But you can see that the attachment record is present and it works fine if you access the record through thin client.


As I already mentioned this is a mistake not a problem so, I am just giving the reason.


You are trying to test it on dedicated client and the CFG of your dedicated client refers to files system of you local PC. Where as the record was created via thin client and then CFG of server was referred and file was stored in the path mentioned in the CFG of server.

So, you need to create a attachment record in dedicated first before you can successfully query or download it.

Don’t delete an attachment record created via web client from a dedicated client as the record from the attachment BC will be deleted but the file from file system will not be deleted, as CFG points to a different files system. It will result in an Orphaned file on file system.

5 Responses to Siebel File System – Common mistake made

  1. Hello Neel- Thanks for that very useful information. How about attachment deletes from the attachment table? Will that still leave an orphan records in the SFS?

    • yes.. it will leave orphan records in SFS. The only way Siebel deletes the complete file and record is if done from business layer…
      Scripting,UI,EAI everything else will leave an orphan record.

  2. Neel,
    I am coming to this post late so I hope you’ll see this:
    I am working on a project right now where I need to send a filename to BIP so that the image the file contains can be displayed in a BI report.
    My plan was to read the attachment information, and use the BC method GetFile to extract the file and write it to another location and then write this file name and location to a record that will be sent as part of an IO to BIP. This must work both locally and on the server.
    An administrator would add these image files via a thin client connection. So, obviously, the local users would have to sync before they’d have the images available locally. Correct?
    Also, is it true that there is no local file system as such? I can’t find an entry for local file system in the config file so I’m assuming the attachments must be stored in the local dbf.

Leave a Reply