Applies to:
Siebel Tools - Version 8.0.0.9 SIA[20433] and laterInformation in this document applies to any platform.
""Checked for Relevance on 23-Jan-2014""
Symptoms
Siebel Version: 8.0.0.9 SIA
Statement Of Issue: When trying to export many records from a VBC based grand child applet error is thrown. The same is working fine when exporting single record.
Steps to Reproduce:
1. Go to Accounts screen
2. Drilldown on record to go to Invoices history
3. Export All rows in Query.
Error Thrown: No rows returned by current BusComp query to export (SBL-UIF-00146)
Cause
Bug 10498588 [CR#12-ZD6UFU][FR#12-ZUKWOM] EXPORT ON 4TH LEVEL APPLET BASED ON VBC RAISES AN E has been reported for the issue.
Solution
1. Create a button called "Custom Export" Method:"MyExport"
2. Query Business component for records and write to a file, record by record.
Snap shot of sample code:
function WebApplet_PreInvokeMethod(MethodName)
{
If (MethodName == "MyExport")
{
// Logging
fp = Clib.fopen("export.txt",'a');
// Get the Account business object
var AccountBO = TheApplication().GetBusObject("Account");
// Get the Account business component
var AccountBC = AccountBO.GetBusComp("Account");
with(AccountBC)
{
var Record;
// Clear to query
ClearToQuery();
// Set the required search specification
SetSearchSpec("Id",TheRequiredAccountId);
// Execute query
ExecuteQuery();
if(FirstRecord())
{
// Do while loop scrolling along the records
do
{
Record = GetFieldValue("Id") +","+ GetFieldValue("Name")
Clib.fprintf(fp,"%s\n", Record);
}
while(NextRecord());
Clib.fclose (fp);
}
}
}
{
If (MethodName == "MyExport")
{
// Logging
fp = Clib.fopen("export.txt",'a');
// Get the Account business object
var AccountBO = TheApplication().GetBusObject("Account");
// Get the Account business component
var AccountBC = AccountBO.GetBusComp("Account");
with(AccountBC)
{
var Record;
// Clear to query
ClearToQuery();
// Set the required search specification
SetSearchSpec("Id",TheRequiredAccountId);
// Execute query
ExecuteQuery();
if(FirstRecord())
{
// Do while loop scrolling along the records
do
{
Record = GetFieldValue("Id") +","+ GetFieldValue("Name")
Clib.fprintf(fp,"%s\n", Record);
}
while(NextRecord());
Clib.fclose (fp);
}
}
}
References
BUG:10498558 - [CR#12-ZD6UFU][FR#12-ZSQ5UW] EXPORT ON 4TH LEVEL APPLET BASED ON VBC RAISESApplies to:
Siebel Financial Services CRM - Version: 8.0.0.1 SIA [20408] and later [Release: V8 and later ]Information in this document applies to any platform.
Symptoms
I am trying to export all Activities rows and all columns to Excel. The systems issues the following error message:"No rows returned by current BusComp query to export!(SBL-UIF-00146)".
It works fine when exporting only visible columns.
There are no problems when exporting all Accounts or All Contacts.
Cause
Menu Export of All Activities (Columns to Export: All) returns error message only happening in version 8.0. and CR 10534861 has been raised as Product defect .
This was found to be a configuration defect in Siebel SIA
Solution
This issue tested with standard srf , able to reproduce the issue in in-house testing.Bug has been raised the Bug#10534861Issue will be fixed in Siebel version 8.0.0.12. The fix request for this matter is addressed in: BUG 11798902 - MENU EXPORT OF ALL ACTIVITIES (COLUMNS TO EXPORT: ALL) RETURNS ERROR MESSAGE
workaround
1) Display all column in list applet - select all columns in visible by using column display then Export. I have tested with this.This is working fine.
This was found to be a configuration defect in Siebel SIA :
Business component 'Action' has a join 'S_INCIDENT' for which the Outer Join Flag is not set. The field 'Incident Name' is based on this join.
So what is happening is the following:
- when you are going to the applet, the field Incident Name is not exposed, so this join is not used for the query and you will find activities.
- likewise if you export with the visible columns only, since this field is not visible the join will not be added and you will still find all activites.
- but if you export with all columns, you will ask for this field 'Incident Name' too, so the join will be added to the query and as it is not an outer join it will lead to an inner join. Since the activities don't have matching incidents, the query returns no row and this explains the error observed.
In order to correct this defect, please open Siebel Tools against your repository and change the configuration as follows:
1. Go to the Join definitions below business component 'Action'.
2. Select join 'S_INCIDENT' and set the Outer Join flag.
3. Compile the change.
This will eliminate the error on the file export in a standard Siebel SIA environment.
No comments:
Post a Comment