If you are unable to create a new account, please email support@bspsoftware.com

Author Topic: LCM 11.0.5 and Layout Component References  (Read 5541 times)

Offline IndyBob

  • Full Member
  • ***
  • Join Date: Oct 2013
  • Posts: 7
  • Forum Citizenship: +0/-0
LCM 11.0.5 and Layout Component References
« on: 05 Mar 2017 04:56:41 pm »
It seems to me that Layout Component References on my reports are preventing LCM from processing the report correctly. I have a layout component reference on all reports that serves the purpose of a header. It is a table containing a logo, and cognos functions to display ReportName() Today() and Now() along with some text. Capturing prompts is working on but when I try to run a task it fails.  If I remove the layout component reference from the prompt page and leave it on the report pages then LCM runs the report.

does anyone have any idea on how I can maintain this functionality and still use LCM?

Offline MFGF

  • Never knowingly correct
  • Super Moderator
  • Statesman
  • ******
  • Join Date: Jul 2005
  • Posts: 11,705
  • Forum Citizenship: +677/-10
  • Cognos Software Muppet
Re: LCM 11.0.5 and Layout Component References
« Reply #1 on: 06 Mar 2017 02:37:00 am »
It seems to me that Layout Component References on my reports are preventing LCM from processing the report correctly. I have a layout component reference on all reports that serves the purpose of a header. It is a table containing a logo, and cognos functions to display ReportName() Today() and Now() along with some text. Capturing prompts is working on but when I try to run a task it fails.  If I remove the layout component reference from the prompt page and leave it on the report pages then LCM runs the report.

does anyone have any idea on how I can maintain this functionality and still use LCM?

Hmmm. That sounds like something you should log with IBM. I assume the LCR is pointing to an object in a different report? What happens if you change the 'Embed' property to "Copy" rather than "Reference"? Do you still get the error? If not, a quick-and-dirty workaround would be to temporarily change this setting in each report then change back again once Lifecycle Manager processing is complete.

MF.
Meep!