How to promote a Crystal Reports with Dynamic Cascading Prompts in BI4

This (and most probably some future) blog post will detail on my experience using Promotion Management (LCM) in BusinessObjects release 4.0. The following explanations are mostly based on the description I’ve just handed in to SAP support. I will do my best to keep this post current regarding answers from SAP support…
Infrastructure: I did all my testes on Cloudshare (see my blog here). Currently using BI 4.0 SP4 Patch 4.

Source-Sytem: Cloudsrv012
Target-System: Cloudsrv016

Promotion Management is primarily used on the Source System.

Update from SAP support

SAP support was quite quick and told me that the issue described in this post will be fixed in patch 4.7 (including the problem of promoting BusinessViews residing in subfolders)

Terms

Dynamic Cascading Prompt (DCP): A parameter object in Crystal Reports 2011 which contains a dynamic list of value (LOV).

List of Value (LOV): List of Value object based on a Business View (BV). Can be created manually in the BV-Manager.

Business View (BV): Business View’s are created in the BV-Manager (which is part of the Client Tools setup of the BI Platform). BusinessViews are based on Business Elements. Business Elements are based on Data Foundation objects. And Data Foundation Objects are based on Data Connection objects. These items are generally considerd as “Repository Objects” (at least in XI 3.1 Import Wizard this was the case).

Initial Setup

Create a LOV with its underlying BVs based on the Xtreme database (using ODBC-Connection to local Access file). Save them in a subfolder (in my example “rbra_Test”):

Create a simple Crystal Report (in CR 2011) containing a parameter with a DCP:

Save this report in the source system. In the BI Launchpad the parameter looks like this:

Problem Description

Goal: Simply promote the above created report from source to target system using promotion management.

Steps taken:

Create new promotion job in Source System including all dependencies:

Then promote:

Result: Partial Success:

My guess: The problem is that the BV-objects are in a subfolder. Therefore, I move the BV-objects in source system to root folder:

Report still works in source system:

Take the same Promotion Job as before and refresh dependencies – no Sub Folder in Business View Branch is shown anymore:

Promote again:

^

Now it shows Success:

It looks like a success in BV Manager too:

and also in Crystal Reports:

BUT: If you open report in BI Launchpad, you don’t see any List of Values:

Tested Workarounds

Promote BusinessViews separately (not working)

I tried to promote BusinessViews and LOV objects separately from the report. I have the same issue regarding storing repository objects in subfolders. Besides this I found the following:

  • Just promoting the BusinessView and underlying objects works fine according to Promotion Management. But if you look into BV-Manager you’ll get errors like this
  • Promotion Management doesn’t allow to select LOV objects separately.
  • If you then promote the same Crystal Reports containing the DCP but do NOT select the dependencies, all the BusinessView objects (and LOV objects) are promoted anyway and break the functioning of the BusinessView and LOV in the target system. Currently we couldn’t find a way to promote a Crystal Reports with DCP without automatically promoting all dependencies and therefore break the target system.

Remove DCP, export / import LOV using BV-Manager (not working)

In order to escape the circumstance that Promotion Management automatically promotes DCP objects etc. (see point above) I tried the following:

  • In the source system, set the Crystal Reports parameter to a Static list of value and save the report.
  • Promote it – no repository objects are promoted.
  • In order to “promote” LOV objects independent from report we used the option to export BV and LOV definitions in the BusinessView Manager.
  • We imported the LOV object into the target system using the import option of the BusinessView Manager.
  • Reset the static prompt to the imported LOV.
  • Result:

    The LOV of the second level doesn’t work.

Remove DCP, export / import BV, recreate LOV (working)

  • In the source system, set the Crystal Reports parameter to a Static list of value and save the report.
  • Promote it – no repository objects are promoted.
  • Promote BusinessView only using export / import in BusinessView Manager
    Using Promotion Management doesn’t work properly! (see errors in BV-Manager above)
  • Recreate LOV objects manually in target system
  • Reset the static prompt to the newly created LOV.

Although this is NOT what I expect from SAP in terms of a properly working software – at least these final steps lead to a working solution without too much of manual recreation of repository and report objects!

For all SAP internal guys if you want to track (and support me ;-): The message number with the same case description as above is 971741 / 2012. I will open up some more cases as the things shown above is just the top of the iceberg of what doesn’t work properly in Promotion Management.