Project bug?

[Anonymous]

C3D 2007 SP1A

Create a drawing, drawing1.dwg
Create an alignment in the drawing "alignment1"
Add the drawing to the vault and share alignment1 to the project.
Check out drawing1.dwg
create a profile for alignment1 and give it the same name as the alignment,
alignment1.
check the drawing back in to vault and share the new profile to the project.
the profile is not added to the project, and no warning or error message is
presented to the user.

I presume that this happens because the shortcuts are always named
"FileName:ObjectName" but the user should be made aware of this conflict
when it happens. This will be especially problematic when checking in
profiles that were created in land desktop if more than one alignment and
profile exists in the same drawing. All imported FG profiles are called
"FG" and Civil 3D allows this name conflict to exist, even though it is
impossible to create the same scenario via the UI.

Jon Rizzo
Langan Engineering and Environmental Services, Inc.

[Anonymous]

Jon Rizzo wrote:
> C3D 2007 SP1A
>
> Create a drawing, drawing1.dwg
> Create an alignment in the drawing "alignment1"
> Add the drawing to the vault and share alignment1 to the project.
> Check out drawing1.dwg
> create a profile for alignment1 and give it the same name as the alignment,
> alignment1.
> check the drawing back in to vault and share the new profile to the project.
> the profile is not added to the project, and no warning or error message is
> presented to the user.
>
> I presume that this happens because the shortcuts are always named
> "FileName:ObjectName" but the user should be made aware of this conflict
> when it happens. This will be especially problematic when checking in
> profiles that were created in land desktop if more than one alignment and
> profile exists in the same drawing. All imported FG profiles are called
> "FG" and Civil 3D allows this name conflict to exist, even though it is


From what I've found, profiles can only live in the same drawing that
the parent alignment lives in. For example, I can create an alignment
and profile in drawing1, add the info to the project, and try to
reference in the profile to drawing2 - won't work.

--
Jason Hickey

Civil 3D 2007, SP1A
Dell Precision M70
2 GIG RAM, 256 MB nVidia Quadro FX Go1400
Intel Centrino 2 gHz Processor

http://beneaththelines.blogspot.com

[Anonymous]

Right - that's why this is a problem. If the user gives the profile the same
name as the alignment (although they probably shouldn't anyways) it will not
be checked in to vault and they will not be prevented from trying, or warned
that it won't work.

"Jason Hickey" wrote in message
news:5258315@discussion.autodesk.com...
Jon Rizzo wrote:
> C3D 2007 SP1A
>
> Create a drawing, drawing1.dwg
> Create an alignment in the drawing "alignment1"
> Add the drawing to the vault and share alignment1 to the project.
> Check out drawing1.dwg
> create a profile for alignment1 and give it the same name as the
> alignment,
> alignment1.
> check the drawing back in to vault and share the new profile to the
> project.
> the profile is not added to the project, and no warning or error message
> is
> presented to the user.
>
> I presume that this happens because the shortcuts are always named
> "FileName:ObjectName" but the user should be made aware of this conflict
> when it happens. This will be especially problematic when checking in
> profiles that were created in land desktop if more than one alignment and
> profile exists in the same drawing. All imported FG profiles are called
> "FG" and Civil 3D allows this name conflict to exist, even though it is


From what I've found, profiles can only live in the same drawing that
the parent alignment lives in. For example, I can create an alignment
and profile in drawing1, add the info to the project, and try to
reference in the profile to drawing2 - won't work.

--
Jason Hickey

Civil 3D 2007, SP1A
Dell Precision M70
2 GIG RAM, 256 MB nVidia Quadro FX Go1400
Intel Centrino 2 gHz Processor

http://beneaththelines.blogspot.com

[Anonymous]

Jon Rizzo wrote:
> Right - that's why this is a problem. If the user gives the profile the same
> name as the alignment (although they probably shouldn't anyways) it will not
> be checked in to vault and they will not be prevented from trying, or warned
> that it won't work.
>
> "Jason Hickey" wrote in message
> news:5258315@discussion.autodesk.com...
> Jon Rizzo wrote:
>> C3D 2007 SP1A
>>
>> Create a drawing, drawing1.dwg
>> Create an alignment in the drawing "alignment1"
>> Add the drawing to the vault and share alignment1 to the project.
>> Check out drawing1.dwg
>> create a profile for alignment1 and give it the same name as the
>> alignment,
>> alignment1.
>> check the drawing back in to vault and share the new profile to the
>> project.
>> the profile is not added to the project, and no warning or error message
>> is
>> presented to the user.
>>
>> I presume that this happens because the shortcuts are always named
>> "FileName:ObjectName" but the user should be made aware of this conflict
>> when it happens. This will be especially problematic when checking in
>> profiles that were created in land desktop if more than one alignment and
>> profile exists in the same drawing. All imported FG profiles are called
>> "FG" and Civil 3D allows this name conflict to exist, even though it is
>
>
> From what I've found, profiles can only live in the same drawing that
> the parent alignment lives in. For example, I can create an alignment
> and profile in drawing1, add the info to the project, and try to
> reference in the profile to drawing2 - won't work.
>


I agree. I think it's a Vault issue, myself.

--
Jason Hickey

Civil 3D 2007, SP1A
Dell Precision M70
2 GIG RAM, 256 MB nVidia Quadro FX Go1400
Intel Centrino 2 gHz Processor

http://beneaththelines.blogspot.com

[kspear]

Sorry Jon, Jason's right. Profiles can be referenced into separate drawings, but the original object HAS to live in the parent alignment drawing. This came to light for a few of us back in May when trying to put Vault through scenarios (XREF / Sharing / etc) that firms tend to create for production sets. The clue is that in the prospector, profiles are not a separate entity but subentity to the alignment....

Sorry dude.

Kevin

[Anonymous]

I realize that the profiles have to live in the same drawing. I'm just
pointing out a bug in the check in procedure...


wrote in message news:5258359@discussion.autodesk.com...
Sorry Jon, Jason's right. Profiles can be referenced into separate
drawings, but the original object HAS to live in the parent alignment
drawing. This came to light for a few of us back in May when trying to put
Vault through scenarios (XREF / Sharing / etc) that firms tend to create for
production sets. The clue is that in the prospector, profiles are not a
separate entity but subentity to the alignment....

Sorry dude.

Kevin

[kspear]

Eh... I new that. 🙂

I gotta get a better newsreader that updates more often....

Kevin

[Anonymous]

Confirmed.

"Jon Rizzo" wrote in message
news:5258322@discussion.autodesk.com...
C3D 2007 SP1A

Create a drawing, drawing1.dwg
Create an alignment in the drawing "alignment1"
Add the drawing to the vault and share alignment1 to the project.
Check out drawing1.dwg
create a profile for alignment1 and give it the same name as the alignment,
alignment1.
check the drawing back in to vault and share the new profile to the project.
the profile is not added to the project, and no warning or error message is
presented to the user.

I presume that this happens because the shortcuts are always named
"FileName:ObjectName" but the user should be made aware of this conflict
when it happens. This will be especially problematic when checking in
profiles that were created in land desktop if more than one alignment and
profile exists in the same drawing. All imported FG profiles are called
"FG" and Civil 3D allows this name conflict to exist, even though it is
impossible to create the same scenario via the UI.

Jon Rizzo
Langan Engineering and Environmental Services, Inc.

[kspear]

However, I did discover that the naming conventions are case sensitive. So, maybe your alignments are Title case and profiles are lower case... if they need to be named identically.

This would be a workaround of course. Part of the problem is that in the landxml spec, profiles are sub-entities to alignments and apparently this carried over into C3D.

[Rebecca Ferguson]

You may have already seen this, but I'm just curious if this has anything to do with this thread....what does this setting do exactly?
-in vault explorer>tools>administration, what does it mean to check or uncheck "Enforce Unique File Names"? would this help you guys?