Project

General

Profile

Bug #5009

Opening two KARS that have the same Workflow, but that have different report layouts, will make the first layout refresh itself with the layout from the KAR that was opened most recently.

Added by debi staggs about 9 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
Normal
Category:
reporting
Target version:
Start date:
05/13/2010
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5009

Description

If you open two KARS associated with the same Workflow, but that have different report layouts, the report layout is the first workspace will change to the one that is in the most recently opened KAR file.

Is related to Bug #4977

History

#1 Updated by debi staggs about 9 years ago

This is because there can be multiple KARS that depend upon the same workflow, but have been saved with different report layouts. When a report layout is opened, it currently only looks up the workflow lsid and nothing else, and has no way to associate an array of reports with a single workflow, and know which one should be used for the currently selected frame.

#2 Updated by Derik Barseghian about 9 years ago

Retargeting - this seems like something we should fix for wrp-2.0. It's possible to open a KAR, redesign the report, and then open another KAR and lose the redesigned report when it's refreshed.

#3 Updated by Derik Barseghian about 9 years ago

I spent a bit looking into this last night. I was able to keep the report layout from refreshing in the window in which it shouldn't, but this isn't enough. When you execute, the old report layout is still used (instead of the one shown) -- so this ends up being more confusing/worse. To really solve this problem, some refactoring needs to be done in a few places for Workflow to truly be keeping track of different report layouts per workflow. This isn't hard. However, there are places, like in the reporting kar entry handlers, where reporting only has a workflow lsid to work with, but additional context is needed to be able to know which report for this workflow to use. This might mean keeping a mapping of reportlayout to frame/window/whatever. Doing this, and in a way that works for both gui and headless, might be non-trivial, and seems likely to introduce bugs along the way. At this juncture we may want to leave this bug in, and retarget to wrp-2.x.y....

#4 Updated by debi staggs about 9 years ago

Based on Deriks comments, re-targeting to wrp-2.x.y for now.

#5 Updated by Derik Barseghian about 9 years ago

retargeting

#6 Updated by Derik Barseghian about 9 years ago

Should be fixed in 2.0 now at r25056. Needs to be merged into trunk.

#7 Updated by Derik Barseghian over 8 years ago

I merged a long time ago, just tested on trunk and works.

#8 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 5009

Also available in: Atom PDF