Import from a spreadsheet - problem with Scope

[stormskipper]

Hi

I'm trying to import some data from an excel spreadsheet which should
be reasonably simple BUT we have a Closed project with the same name
as the project I want to import the data to. (It's a legacy of some
earlier trial with versionOne). It's in the same place on the
heirarchy too. How do I get the import to resolve the Scope properly.

I tried putting the numerical Scope value into the Scope import field
but it didn't like that.

Is there a way to do this - short of importing to a different project
and then moving them all.

Regards
Toni

[Kevin S.]

A hack proposal... reopen the old project... append a character to the
name to change the name... and close. You should be able to do this
quicker than most users can notice.

If the core issue is the similarly named project... then that might
work.

Good luck!

[V. Lee Henson CST]

Or... you could import the items under a project with a new name (one
Character off) and update the name of the new project after the import
is complete. On the flipside, I will point this out to our usability
guy and see what he has as a proposed solution. In the meantime, it
may be quicker to either open the closed project and change one letter
or import the new with one digit changed.

I hope this helps!

V. Lee Henson CST
Agile Professional / VersionOne Product Expert
http://agiledad.blogspot.com

[stormskipper]

Hi

You are assuming that I have the rights to reopen the closed project
or update the name on the new one!!
Which I don't. This makes it a real hassle because I now need to find
someone who has those rights to make the edits for me.

Regards
Toni

[stormskipper]

OK - I've now found someone to rename the original project.

BUT I'm still having problems:
I now get: VersionOne Import Error: Multiple Project assets matching
provided name. Could not resolve value for attribute Scope.Parent.

I'm giving it a Scope of :

Development Project \ MYProject \

I've tried with and without the spaces before the \ characters, with a
\ at the end and without.
There is no other project closed or not called Development Project

But there are projects called Development Project \ MYProject Future

Development Project is a Sub-project of the very top level (called All
Projects)
Do I need to include All projects?

Regards
Toni

Could this be affecting it.

[Luanne]

Toni,

This format should work: Development Project\MYProject (make sure
there are no spaces between the project and at the end)

It does not need the top level of All projects. If this doesn't work,
we can hop on a quick GoToMeeting so I can take a look.

-Luanne

[stormskipper]

Hi Luanne

I've tried that combination:

VersionOne Import Error: Multiple Project assets matching provided
name. Could not resolve value for attribute Scope.Parent.

I've tried the import at a different place in our heirarchy - one that
doesn't have the parent - development Project and that worked fine.
If I look through Admin - there is another project called Development
Project but it's 2 levels down the heirarchy in
Sand Box > Project Template > Development Project

This has no subprojects at all - so the combination of Development
Project\MYProject is unique as a pair.

I don't know how your software works - but is it just parsing the
first level and then dropping out without trying it in combination
with the second level?

(It would be a lot easier if there was an alternative to provide the
numerical scope when importing = would save all this hassle)

Regards
Toni

[stormskipper]

Hi Luanne

I've tried that combination:

VersionOne Import Error: Multiple Project assets matching provided
name. Could not resolve value for attribute Scope.Parent.

I've tried the import at a different place in our heirarchy - one that
doesn't have the parent - development Project and that worked fine.
If I look through Admin - there is another project called Development
Project but it's 2 levels down the heirarchy in
Sand Box > Project Template > Development Project

This has no subprojects at all - so the combination of Development
Project\MYProject is unique as a pair.

I don't know how your software works - but is it just parsing the
first level and then dropping out without trying it in combination
with the second level?

(It would be a lot easier if there was an alternative to provide the
numerical scope when importing = would save all this hassle)

Regards
Toni

On Mar 27, 8:30 pm, Luanne <luanne.cur...@versionone.com> wrote:

[stormskipper]

Aha - I tried renaming Sand Box > Project Template > Development
Project to Sand Box > Project Template > Development Projects

and now it works.

But can you flag it up to your team that this is a real hassle - it
means we can't have any project names anywhere in the heirarchy with
the same names (and we do!)

Regards
Toni

[Maggie Bullington]

When in doubt use the full project path to the project you are looking for. This will always work. Because "Development Project" matched more than one project, your import failed. The import will not try to qualify which project it is by looking at the children, it reads left to right. So it found 2 instances of Development Project and sent the error. If you had included the parent of Development Project, and if necessary the parents on up as far as you have access, then it would have worked.
-Maggie

[stormskipper]

The pArent of the Development Project instance I wanted is All
Projects and that didn't work - I already tried it.

Regards
Toni

On Mar 30, 12:14 pm, Maggie Bullington

[stormskipper]

The pArent of the Development Project instance I wanted is All
Projects and that didn't work - I already tried it.

Regards
Toni

On Mar 30, 12:14 pm, Maggie Bullington
<maggie.bulling...@versionone.com> wrote:

[stormskipper]

Using All Projects/Development project/MYProject as the Scope returns:
VersionOne Import Error: Unable to resolve attribute value for asset
type Project on attribute Issue.Scope.

Unless the root of the Projects isn't called All Projects but then it
doesn't say what it is called?

Regards
Toni

[Maggie Bullington]

Ah, I see the issue. You don't have access to the root level project most likely (All Projects is a pseudo project that is there so users without a natural root project can do roll-up planning and reporting). Sorry for the misinformation!
The other thing you can do, which will be fail-safe, is to use the system ID for the project. You can see this in the VersionOne UI if you click on the name of a project (or hover on the link) - it's the last part of the url and should be formatted like this in the spreadsheet - Scope:1234. You can also get a list of the ids and names together from one api query in the browser that can make this easy: http://servername/v1instance/rest-1.v1/Data/Scope?sel=Name

The name resolution can't conquer all duplicate name scenarios - you can have two sister projects with the exact same name for instance. But using the ID guarantees a unique match.

[stormskipper]

Hi Maggie

Is it possible to use the scope numeric ID in the spreadsheet. I'd
have done this in the first place except I don't know what to call it
on a spreadsheet import.

I know you can do this using the API - but I'm not a programming API
expert so just wanted to use the excel spreadsheet import.

Thanks
Toni

On Mar 30, 12:53 pm, Maggie Bullington

[stormskipper]

Whoops sorry - I didn't see that you'd already told me how to input
the scope numerically.
can I suggest that you add this to a FAQ or somewhere useful on the
website. It would have saved me a lot of time.

Thanks
Toni

[Maggie Bullington]

This thread will now be on the community site as searchable :) We do also have an article on excel import tips and tricks that could be updated (http://community.versionone.com/KnowledgeBase/FAQs/Q11412.aspx). I'll let the product owners know.