It's all about the answers!

Ask a question

How does csv import work for "Planned For" field. Does it consider "Identifier" or "Display Name"?


Varshitha Ramamurthy (11) | asked Oct 27 '22, 6:39 a.m.

 Display Name Hierarchy:                                      Identifier Hierarchy:

 Baseline(root)                                                         rbd.bcm.mqb37w.baseline(root)
  -->Baseline Project                                                    -->BaselineProject
      -->37wBL_VR4222                                                        -->37wBL_VR4222
           -->RB_272_X                                                                -->RB_272_D
            -->RB_272_Y                                                                -->RB_272_X
                 -->RB_272_YA                                                              -->RB_272_YA    
                    -->RB_272_YA_E6_VV_Execute                                 -->RB_272_YA_E6_VV_Execute
                      -->RB_272_YA_F1_VV_Execute_Warmup                   -- >RB_272_YA_F1_VV_Execute_Warmup

                                                                             
While trying to import csv file, the attribute planned for:
    Planned For value in csv                                                                       Imported into Workitem
         1.RB_272_X                                                                                        RB_272_X
         2.RB_272_Y                                                                                        RB_272_X
         3.RB_272_YA_E6_VV_Execute                                                      Blank (No Value)
         4.RB_272_YA_F1_VV_Execute_Warmup                                       Blank (No Value)
         5./Baseline/Baseline Project/37wBL_VR4222/RB_272_X               RB_272_YA_E6_VV_Execute                     
            /RB_272_YA/RB_272_YA_E6_VV_Execute              

Query:
How does csv import work for "Planned For" field. Does it consider "Identifier" or "Display Name". In 1., it is imported using the display name. 
But in other case, only when complete path with identifier is given it works.

One answer



permanent link
Davyd Norris (1.7k115) | answered Oct 27 '22, 10:03 p.m.
You need to use the IDs, not the Names, starting with the timeline ID at the top, so your last examples should work if you map them in the form:

/rbd.bcm.mqb37w.baseline/BaselineProject/37wBL_VR4222/RB_272_D/RB_272_X/RB_272_YA/RB_272_YA_E6_VV_Execute/RB_272_YA_F1_VV_Execute_Warmup

It's hard to see the actual hierarchy in the example above because the indentations aren't clear

Comments
Varshitha Ramamurthy commented Oct 31 '22, 6:35 a.m.

   Planned For value in csv                                                        Imported into Workitem

         1.RB_272_X ( name)                                                                RB_272_X
         2.RB_272_Y(identifier)                                                              RB_272_X
 It's taking a value for X even though the ID'S are not given.(both display name and identifier used separately gives a value), but for others the whole path to be mentioned.
Why is it taking only name or a display to import some values for attribute , but for some the whole path to be mentioned?


Davyd Norris commented Oct 31 '22, 8:37 p.m.
The import tool is pretty smart but you're really making it work hard on this one!

If you go back to the original tree you put up, you do not have an identifier "RB_272_Y" and you have mapped the display "RB_272_Y" to the identifier "RB_272_X", and you have both a name and an identifier "RB_272_X" but mapped to different display values!

The only way to get a consistent result is to explicitly map the entire id path, then the import tool doesn't have to guess what you're doing

Your answer


Register or to post your answer.