Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Duplicate records in RELM view

 Hello Team,


Duplicate records shown view container in Engineering Lifecycle Manager (relm)

  1. I have created view using global configuration context using one requirement project, when I drag and create requirement container it always shows duplicate records and even if we try to add condition using refine container content it shows multiple attributes.

Can you Please suggest .

Thanks

0 votes

Comments

Seems like you do have multiple requirement project areas and you are seeing those duplicate records from different project areas.

You could try applying the project scope by selecting the applicable project areas only.

Thanks Rahul.


In project scope , I have selected only on project area. still its showing multiple records. For example , see i have one module with 10 Req  as type " System Requirements".

But when i have select container Requirement and type System Requirement , then i check for count the its showing 20 counts.

Please suggest.
Thanks 

Is the container linked with some other container? If yes, can you please share the details?

Hi Rishikesh


We are using single container ( its not linked with any other container)  . we are using Datasource as " LQE with Configure scoped " as we are using GC for our  project with RM and QM.

Do you have any clue why its showing duplicated records?

Thanks



One answer

Permanent link
It seems that all the Resource Nodes(Artifacts) listed in the Node Container have different URLs, even if their Title/Summary/Description is same.

RELM discards the Resource Node with same URL from the Node Container. So if the same artifact have two different URLs, then that will not be treated as duplicate entries.

In your case, the artifacts are from Requirement Management(RM). And the following might be the cause to your problem:
  • Requirements in RM can exist independently(without being member of any Module or Collection).
  • Requirements in RM can also exist as a member of any Module or Collection.
  • So, if any of the Requirement Artifact is added as the member of any Module or Collection, a copy of the Artifact is created with different URL.
  • Lets consider the following example:
    • A Requirement Artifact exist independently with following details
    • When the same requirement is added as a member of a Module or Collection; a copy of it is created. The copied artifact will have following details:
    • From the above two points, we can see that the Title remain same, but the resource URL changes. And thus two different resources(artifacts) for the RELM Views.

You can verify the same in your case by opening the duplicate artifacts in separate tab and check whether they point to same or different resources(URL).

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 113

Question asked: Feb 13 '20, 7:01 a.m.

Question was seen: 1,360 times

Last updated: Feb 14 '20, 3:24 a.m.

Confirmation Cancel Confirm