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

Formatting of Headings in DNG messed up when importing from CSV

Hello

I'm trying to import some modules from DOORS to DNG with the required artefact types. A promising method seemed to be via csv format, I am using this article as a guide:

https://jazz.net/wiki/bin/view/Main/DNGCSVImpExp

Works perfectly when mapping levels and artefact types, but there seems to be some weird bug when importing headings. The headings text and levels seem completely correct, the object hierarchy is correct, but the numbering and formatting of the headings is not there. I'm using DNG 6.0.2

So I get

Introduction

Instead of

1. Introduction (in large bold font)

formatting not working on this forum in my browser

What am I doing wrong?

0 votes



2 answers

Permanent link

The answer is here, I think that information should be part of the Excel Import article: -

https://jazz.net/forum/questions/230634/why-wont-the-heading-numbers-show-up-in-the-contents-column-in-a-module-after-import-using-parentbinding

0 votes

Comments

Note that you have to be careful that the isHeading column contains True and not "True", note quotes or it doesn't work

Sorry for the bump in this old thread, but Richard Good's answer is either incorrect, or at least obsolete.

DNG exports the Boolean values as "true" and "false", so I prefer to use lowercase versions. However, I just tested, and the Import process from XLSX (and presumably other input formats) accepts any of UPPERCASE, Initialed, or lowercase.


Quote marks are only a good idea if importing from CSV, and even then they aren't necessary.


Permanent link
 DOORS has a built in method of migration to DNG from version 9.6.1.3 onwards.
The CSV approach can lose a lot of information that you then need to create.
The built in method should maintain module hierarchy and heading numbering etc.

0 votes

Comments

Yes I know all about that, but it does not seem fit for purpose. I do not want a load of superfluous module and object types. I wan to map requirements to requirements not a DOORS object type named after the DOORS module. If there is some issue I want the system to tell me about it and not import it. Designing views in DOOR, mapping attributes I have in DOORS to Attributes I want in DNG and stripping out stuff I don't want seems a much better way of doing things. I fundamentally disagree with the way the DOORS migration has been designed it means you get a whole load of mess in DNG when you migrate. There should at least be a picky mode that doesn't take everything, doesn't create attributes and enumerations for you and reports errors you can then address in DOORS and re migrate

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
× 12,021

Question asked: Mar 22 '18, 6:57 a.m.

Question was seen: 3,226 times

Last updated: Oct 16 '24, 2:17 p.m.

Confirmation Cancel Confirm