Project

General

Profile

Bug #4896

When exporting multiple runs only 1 ROML is placed in KAR

Added by Derik Barseghian over 9 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
reporting
Target version:
Start date:
03/19/2010
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
4896

Description

If you export multiples runs that have different report designs and instances from the Workflow Run Manager, you only get one ROML in the KAR.

I'm also seeing errors like the below, but I'm not sure if they're related:

ERROR (org.kepler.objectmanager.library.LibraryManager:assureTreeItem:308) Error while adding Tree Item

History

#1 Updated by Derik Barseghian over 9 years ago

It looks like this is occurring because ReportLayout lsids don't change when they're modified, so when the KAR is built the second roml isn't added to the KAR because of the lsid collision. I think the proper solution here is to update the revision of a report layout any time it's modified. I see there are ReportChangeObserver and ReportChangeObservable classes, but they're not being used.

#2 Updated by debi staggs over 9 years ago

(In reply to comment #1)

It looks like this is occurring because ReportLayout lsids don't change when
they're modified, so when the KAR is built the second roml isn't added to the
KAR because of the lsid collision. I think the proper solution here is to
update the revision of a report layout any time it's modified. I see there are
ReportChangeObserver and ReportChangeObservable classes, but they're not being
used.

If we did this, then would that eliminate the need for the solution described in Bug 4923 ?

#3 Updated by Derik Barseghian over 9 years ago

No, doing this (which I think we should), won't solve the issue in bug #4923.

#4 Updated by Derik Barseghian over 9 years ago

reassign to debi. She has listeners that can be used to updateRevision on the lsid

#5 Updated by Derik Barseghian over 9 years ago

It seems like this may also cause problems when there are two different ROMLs in different KARs in your local repository, but each ROML has the same lsid. I imagine there are problems with the core DB, object manager, etc being able to distinguish between the two during various functions.

#6 Updated by debi staggs over 9 years ago

Have LSID revision number incrementing now. However, if the user opens a saved archive, and then opens a different saved archive, then all windows are updated to show only the archive that was opened last.

#7 Updated by debi staggs over 9 years ago

Report Layout lsid's are now changed whenever a report layout is modified.

#8 Updated by Derik Barseghian over 9 years ago

Don't forget changing textfields, title, images, or Properties - when I make changes to these things the ROML LSID doesn't change.

#9 Updated by debi staggs over 9 years ago

I was getting to that, should have left the bug open though until it was done.
Now is complete. lsid's changing after any and all changes in the report including layout changes, changed to the textfields, text areas, title, images, and Properties. Bug should be officially closed now.

#10 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 4896

Also available in: Atom PDF