Skip to Content
0
Former Member
Jun 29, 2015 at 12:38 PM

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

21 Views

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);

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


Regards,

Rajkumar