SBL-UIF-00230

For Service Request Business Component, I have added the "Deep Copy n" user property in order to copy child attachments of a copied SR. However, for the new-copied SR, I cannot open the attachments and the following error appears:

SBL-UIF-00230: The file performance.txt could not be found on any specified file system.

The cause of this issue is custom configuration. In custom environment, Deepcopy functionality configured on "Product Defect" & "Related Service Request" BCs. In Standard environment, Product Defect & Related Service Request BCs have parent-child relationship as many-to-many(M:M). As per Bookshelf note, Do not use Deep Copy when the parent-child relationship is many-to many (M:M). Because of the configuration, when user tried to open the attachments, the "SBL-UIF-00230" error occurred.

There are two ways to "Deepcopy" child BC records:
(1) By setting "No Copy" of the MVL to child BC to FALSE
(2) Using "Deep Copy" BC user property

1) By setting "No Copy" of the MVL to child BC to FALSE:
With this configuration, the record being copied but "SAF" file is not generating in FS folder, so when we try to open the attached file it will give an error message. This is because the copy is done at the DB level, and since the file is in the files system, and not the DB, then the file itself is ignored. {Please check the Note: 1061595.1 }

2) Using "Deep Copy" BC user property:
To configure Deep copy functionality refer Bookshelf: Siebel Developer reference>> User Properties >> Business Component User Properties>> Deep Copy n 
Additionally for Service Request Attachment" BC >  set ActivityFileName  field property Nocopy=N .

In customer environment, after disabling the Custom BC user properties (Deep copy3 (Product Defect), Deep copy4 (Related service request BC)) and correcting configuration settings the issue got resolved. Customer is able to open attached document without an error.

Siebel Applications - Version 8.1.1.11.5 [IP2013] and later
Information in this document applies to any platform.

When Attachments are copied as child objects during the copy of a parent Project,the copied attachment is not accessible on the file system.

STEPS
1. Launch application.
2. Navigate to Site Map > Projects > List.
3. Create a new Project.
4. Drill down to the created Project Name.
5. Create an attachment at the child applet Attachments view tab.
6. Return to previous Project list applet.
7. From the applet view, select Menu item: Copy Record.
8. Provide a new name for the new record.
9. Drill down on the new record to the Attachments child applet.
10. Verify that a copy of the Attachment also exists.
11. Select the attachment file with mouse by clicking on the hyperlink.

Result: The following error message displays:

The original attachment can launched, when selected; however, the copied Prpject's attachment is not accessible.

The following bug was created to address this behavior:

BUG 19022954 - WHEN COPYING PROJECTS CHILD RECORDS GET COPIED BUT NOT POPULATED PROPERLY
 

BUG 19022954 "WHEN COPYING PROJECTS CHILD RECORDS GET COPIED BUT NOT POPULATED PROPERLY"  is being reviewed by Engineering.

Siebel System Software - Version 7.5.3 [16157] and later
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3 [16157]
Database: Microsoft SQL Server 2000
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: Microsoft Windows 2000 Server SP 3

This document was previously published as Siebel SR 38-1166698961.

The customer was importing a text document as an attachment to a Service Request, the document being part of a MIME Hierarchy. The attachment was imported and could be seen in S_SR_ATT and existed as an saf in the file system. When the attachment was selected in the client application by clicking on the hyperlink in the Service Request > Attachments, the following error was received:

The behavior was re-produced. Change Request 10474909 was logged as a Product Defect. This is described as "Importing MIME documents via workflow doesn't allow attachment to be opened in client."

The reason the error is generated is because the FILE_REV_NUM is not being used correctly in the saf naming (the naming convention should be: <Table Name> + Attachment Row Id + <File_rev_num>.SAF)

The workaround is to inactive the component field: activityfilerev in the Service Attachments integration object.