nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Update of csv/excel imported requirments in RequirementsModel

medini_1063548292

Hi, Can you please advise on how to perform and update of requirements imported into Medini using "Import Requirments from CSV/Excel" ? I have not been able to find any function similar to push/pull if RequirementsModel is linked with external RMS. When I tried to perform import from csv/excel N times of the same file on the same requirements model package it created 2Nx identical requirements for each import operation. I expected similar feature whenever elements in systemModel are imported form CSV. And after the very first excel import is completed another contextual menu feature is shown ( "Update elements from CSV/ Excel.."). Thanks & Regards, Marian

Find more posts tagged with

medini

medini legacy

Accepted answers

All comments

medini_1023909254

Hi Marian, the import/update capability for requirements from Excel is not supported as Excel is not really a requirements management system. Therfore only an import is available (usually intended for a one-time import). For a full exchange of reuirements a direct connection to a requirements management system (e.g. DOORS NG, Jama, Pollarion ...) is required or ReqIF must be used. Best regards, Eckhardt

medini_1063548292

Hi Eckhardt, Thanks for the background information. The reason behind decision to use excel to import requirements was because of issues we encountered trying to get requirements from JAMA/ReqIf. For JAMA we used Mapping file with filtering as described in the scripting forum but failed. Reagrding the Reqif we could not even find a way how to modify criteria for import from ReqIf file ( most likely not supported). We had a very large ,hierarchical DB that contained various types of items ( Requirement,Information.Heading,...) and we wanted to only select Requirements that were relevant for the DFMEA/FuSa analysis carried out in Medini. After couple of failed trials we decided to export filtered set of requirements from JAMA -> to Excel and then import it into Medini. However now the requirements were updated in JAMA and we were thinking about a way how to "Update" information in Medini without customized "Update" script. Best Regards, Marian

medini_1059007410

Hi Marian, Which problems did you encounter with the mapping files for Jama? Selecting certain requirements for an import should be doable with mappedSelectors. Maybe I can try to help on that. Regards, Nils

medini_1063548292

Hi Nils, Yes indeed the mappedSelector worked perfectly no issue there. But long story short .. here is a simple test case: if the matched item was inside the hierarchy while the parent did not match the criteria then the final step failed because it could not find a way to the root. I tried to manipulate the filtered items during the import inside of mappedSelector to flatten the hierarchy so all matched items would have "root" as a parent but unfortunately did not succeed. If needed I can perhaps create a thread in the scripting forum or maybe a ticket? Regards, Marian

medini_1059007410

Hi Marian, Ah, that one. Another customer had the same issue (with DOORS) a while ago and indeed it didn't work. Since then we improved the behavior and since 2022 R2 it should work (also with e.g. Jama). Can you try your import with 2022R2 again, is that possible? The option for the force at root should be as follows (last line): Regards, Nils

medini_1063548292

Thanks Nils! I issued IT ticket to install the 2022 R2 release. Once installed I will try and let you know the outcome! PS: Is here a plan in the future to document some mapping features, similar to metamodel guide, or the only place is to discuss related topics in the Scripting forum thread by Jan ! Regards, Marian

medini_1059007410

Hi Marian, Ok, good. Regarding documentation: There are a lot of variations across the different requirements management system integrations (different APIs/behaviors of the other systems), so it's difficult to cover all. We have the idea to not just document (like here) , but also ease configuration by some tool help. Not sure when this will be possible - if it takes too long, we'll go the document way. Until then we're always here to help :-) Regards, Nils