Runtime Event-Attachment BC and a Strange Problem

(2 votes, average: 5.00 out of 5)

 Loading ...

Siebel is full of strange problem and for many of them there is no logical explanation of problem (may be there is but we just don’t know). In this post I will discuss a strange problem that I faced few days ago. I was able to solve the problem but unfortunately I was not able to completely figure out the reason why it happened in first place. So, putting it out here so if anybody out here has a reason or has faced similar problem then he can share it with us.

We did the following configuration in Opportunity Attachment BC for a requirement:

• Created 2 new joins 1 with S_OPTY table and 2nd with S_ORG_EXT Table
• Created 3 new field using the above created joins with following naming convention
  Oppty XXXX XXXX

Till now everything was fine. Next Step was

• Setup a Runtime event on Write Record of Opportunity Attachment BC.
• Associate an Action Set with this Runtime Event.
  
• Used newly created fields to set some profile attributes in action set.
  

Now, as soon as we used newly created fields in Action Set to set some profile attribute, Siebel started giving below mentioned error on Opportunity attachment write record.

—————————
Siebel
—————————
No field matches identifier ‘Oppty Customer Name’.
Please ask your systems administrator to check your application configuration.(SBL-DAT-00416)

Old fields were working fine this problem was only with new fields that we had created.

I tried everything I could do such as:

• Compile the BC again.
• Double check if I am compiling in same SRF
• Wrote a business service that would get field value for these fields and it was working fine.

Error was coming only when I used that field in Runtime events. After some R&D I noticed a User Property “DefaultPrefix” on Attachment BC that has value “Oppty” and searching bookshelf give me cryptic line or two about this user property.

What I understood from it is that, there is relation between field names and this prefix and using this prefix for custom fields can have side effect.

So, I removed this prefix and tried but error was still coming but by now I was pretty sure that there is something wrong with the fields that we had created. In the end I had to delete new fields and recreate them again with a different name (without Oppty prefix) to make it work.

I will be doing some more R&D when I get some time to find out if DefaultPrefix was the only reason for this behavior or was there something more to it. In the mean time you can post your suggestion/solutions/reasons about this problem via comments.