Set parameters for the statement within the new publication threw exception.

[Former Member]

Hi,

With regards to the Upgrade of our business objects platform from version 3.0 to version 4.1.

Our .net application allows scheduling publication reports using the BI PLATFORM .NET SDK RUNTIME and we were referencing below dll’s in our application for business object 3.0

• BusinessObjects.Enterprise.Desktop.Publication                 version 12.0.1100.0
• CrystalDecisions.Enterprise.Desktop.Calendar                               version 12.0.1100.0      
• CrystalDecisions.Enterprise.Desktop.Report                                   version  12.0.1100.0
• CrystalDecisions.Enterprise.Dest.DiskUnmanaged               version 12.0.1100.0
• CrystalDecisions.Enterprise.Framework                            version 12.0.1100.0
• CrystalDecisions.Enterprise.InfoStore                                            version 12.0.1100.0
• CrystalDecisions.Enterprise.PluginManager                                    version 12.0.1100.0

After installing the BI Platform 4.1, we have added BI 4.1 DLLs in our project and updated the references as below

• BusinessObjects.Enterprise.Desktop.Publication                 version 14.0.2000.0
• CrystalDecisions.Enterprise.Desktop.Calendar                               version 14.0.2000.0      
• CrystalDecisions.Enterprise.Desktop.Report                                   version  14.0.2000.0
• CrystalDecisions.Enterprise.Dest.DiskUnmanaged               version 14.0.2000.0
• CrystalDecisions.Enterprise.Framework                            version 14.0.2000.0
• CrystalDecisions.Enterprise.InfoStore                                            version 14.0.2000.0
• CrystalDecisions.Enterprise.PluginManager                                    version 14.0.2000.0

We are getting a successful build after updating the dll’s however during runtime below highlighted code is throwing ‘Unable to get SI_KIND property value’ error.

formatInfos = mainRepTemplReport.FormatInfos;

formatInfo = formatInfos.Add();

1. formatInfo.SetSourceDocumentKind(InfoStore.CeKind.CRYSTAL_REPORT);

ReportFormatOptions formatOptions = (ReportFormatOptions)formatInfo.GetFormatOptionsObject();

1. formatOptions.Format = GetReportFormat(schedulerInfoEntity.ReportFormat);
2. 
   

Could you please let us know if we have missed any configuration or if we have any work around on this issue ?

Regards,

Rajkumar

[Former Member]

After upgrading BI XI 3.1 to BI 4.1 SP5, the following line of code is failing

ReportFormatOptions formatOptions = (ReportFormatOptions)formatInfo.GetFormatOptionsObject();

It throws the error:

Unable to get SI_SPECIFIC_PROGID property value

or

Unable to get SI_KIND property value

Tried using setFormat method - same error.

After some investigation, found what appears to be the issue:

In java, the method GetFormatOptionsObject has been modified to take a

parameter: getFormatOptionsObject(java.lang.String kind)

While in .Net the method remains the same and doesn't take any parameters. It is bug in the .NET SDK for BI 4.1.

Until this method get fixed, BI 4.1 .Net SDK can not be used to create dynamic publication report.

Regards,

Rajkumar

[former_member183750]

Hi Rajkumar

Are you able to get the SI_KIND property value using the Query Builder? E.g.; What ever the SQL you are using in the app to get the report ID (or SI_KIND property value), try it in the Query Builder.

If in your code you are using variables, for testing purposes don't. Find out the value in Query Builder, then hard code that in your app.

- Ludek

Senior Support Engineer AGS Product Support, Global Support Center Canada

Follow me on Twitter

[Former Member]

Thanks Ludek for quick response on this query. We have ran the following query and it returns properly without any issues.

Below is the query which we are using in our code and we were able to run these queries successfully in Query Builder.

Publication Query:

==================

SELECT * FROM CI_INFOOBJECTS WHERE SI_KIND ='PUBLICATION' AND SI_PARENTID =160352  AND SI_NAME = 'Member Statement' AND SI_INSTANCE = 0

Select * From CI_INFOOBJECTS Where SI_KIND ='CRYSTALREPORT' AND SI_ID = 160399 AND SI_INSTANCE = 0

Select SI_ID From  CI_INFOOBJECTS Where SI_KIND ='CRYSTALREPORT' AND SI_NAME = 'Demo Member Statement'  AND SI_INSTANCE = 0

Just want to confirm that, the query and code was working fine with BI 3.1 version. After upgrading the BI 4.1, the following highlighted code throwing exception.

formatInfos = mainRepTemplReport.FormatInfos;

formatInfo = formatInfos.Add();

formatInfo.SetSourceDocumentKind(InfoStore.CeKind.CRYSTAL_REPORT);

ReportFormatOptions formatOptions = (ReportFormatOptions)formatInfo.GetFormatOptionsObject();

formatOptions.Format = GetReportFormat(schedulerInfoEntity.ReportFormat);

Please could you let us know if anything wrong with our BI publication report in Version 4.1.?

Please let me know if you need any further information required?

Any help much appreciated?

Regards,

Rajkumar

[former_member183750]

Not sure. AS long as you are using the latest updates for BI 4.1, there should not be an issue. It may be an idea to create a phone incident in the SAP Service Market Place, get a support engineer to have a closer look(?).

- Ludek

[Former Member]

Thanks Ludek. i gone through all the forum about issue, no one had come across this issue. Actually when have removed the below code and directly assigned the report format, we are able to generate the PDF files from BI 41. and while opening those files, we are getting below mention exception.

ReportFormatOptions formatOptions = (ReportFormatOptions)formatInfo.GetFormatOptionsObject();

PDF throws below exception.

Adobe Reader could not open 'XXXX.Pdf' because it is either not a supported file type or because the file has been damaged (for example, it was sent as an email attachment and wasn't correctly decoded).

We were able schedule to Normal report and generate successfully the PDF and we were able open those (Nomal report) file without any issues.

Please could you help us, Is there any setting to be done in BI to get this working?

Meanwhile we will raise an Incident ticket with SAP Service Market Place to look into this issue?

Regards,

Rajkumar