Community
Vault Forum
Welcome to Autodesk’s Vault Forums. Share your knowledge, ask questions, and explore popular Vault topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Nightmare: spreadsheet driven assemblies in Vault

10 REPLIES 10
Reply
Message 1 of 11
Anonymous
251 Views, 10 Replies

Nightmare: spreadsheet driven assemblies in Vault

Does anyone know if Autodesk is doing anything to resolve the issue of assemblies retaining their links to the original spreadsheet after a copy design?

The inability to have the new assembly reference the new spreadsheet has virtually paralyzed our workflow.

This one glitch is causing me to rethink whether the Vault is even worth implementing.

If you have any insight, I'm all ears.
10 REPLIES 10
Message 2 of 11
Anonymous
in reply to: Anonymous

Hello,

I have the same problem...

Bruno


a écrit dans le message de news:
5074555@discussion.autodesk.com...
Does anyone know if Autodesk is doing anything to resolve the issue of
assemblies retaining their links to the original spreadsheet after a copy
design?

The inability to have the new assembly reference the new spreadsheet has
virtually paralyzed our workflow.

This one glitch is causing me to rethink whether the Vault is even worth
implementing.

If you have any insight, I'm all ears.
Message 3 of 11
Anonymous
in reply to: Anonymous

Hi guys,

I'm trying to reproduce this problem myself... I believe our development
team is aware of the problem, but I'll be following up with them to make
sure we can reproduce this issue and see what can be done to address. Thanks
for reporting this and making us aware of the problem.

Bob

"Bruno MARTIN" wrote in message news:5076811@discussion.autodesk.com...
Hello,

I have the same problem...

Bruno


a écrit dans le message de news:
5074555@discussion.autodesk.com...
Does anyone know if Autodesk is doing anything to resolve the issue of
assemblies retaining their links to the original spreadsheet after a copy
design?

The inability to have the new assembly reference the new spreadsheet has
virtually paralyzed our workflow.

This one glitch is causing me to rethink whether the Vault is even worth
implementing.

If you have any insight, I'm all ears.
Message 4 of 11
Anonymous
in reply to: Anonymous

Could you embed the spreadsheet in an ipt file? I was told to use this method vs. stand alone spreadsheets. Through DA I have been able to copy / rename the ipt file with the spreadsheet without issues. It has even accepted a rename outside of IV.

Pete
Message 5 of 11
Anonymous
in reply to: Anonymous

I would rather LINK all of my parts to the same spreadsheet. If I EMBED them, all of the parts (from what I understand) will no longer be linked to the same parameters. Tell me if I am wrong, but I do not want to have to open each embedded spreadsheet and paste my values each time. I have almost a thousand parts...and I am changing them more than just once.
Message 6 of 11
Anonymous
in reply to: Anonymous

I am assuming you have many files referencing parameters from a common spreadsheet. This is what I have done.

I create the spreadsheet to drive all my parameters, "Skeleton.xls" I then embed this spreadsheet into a blank ipt file, "Seleton.ipt" I set all my embeded parameters for export (check the export box for each). I insert this ipt in all my parts that would have referenced my spreadsheet as a "Derived" part with a plus by "Exported" parameters.

I can still update the spreadsheet to update all the parts by editing the embeded spreadsheet. The only draw back is if you add or insert the parameters they don't show up in order.

Pete
Message 7 of 11
Anonymous
in reply to: Anonymous

Well said Pete...

Never, ever, link 100+ parts to the same Excel file. That's a beginners
mistake. Link the Excel file to one part, and derive that part into the
other parts and assemblies. You will only have one OLE link to manage.

Embedding the Excel file is an option, but I would rather see DA handeling
OLE links.

Cheers!

--
T. Ham
Mechanical Engineer
CDS Engineering BV

Dual Pentium XEON 2.2 Ghz
2 GB SDRAM
NVIDIA QUADRO4 700 XGL (Driver = 77.18)
18 GB SEAGATE SCSI Hard Disc
3Com Gigabit NIC

Windows 2000 Professional SP4
Autodesk Inventor Series 9 SP4
Autodesk Inventor Series 10 SP3a
--

wrote in message news:5078614@discussion.autodesk.com...
I am assuming you have many files referencing parameters from a common
spreadsheet. This is what I have done.

I create the spreadsheet to drive all my parameters, "Skeleton.xls" I then
embed this spreadsheet into a blank ipt file, "Seleton.ipt" I set all my
embeded parameters for export (check the export box for each). I insert
this ipt in all my parts that would have referenced my spreadsheet as a
"Derived" part with a plus by "Exported" parameters.

I can still update the spreadsheet to update all the parts by editing the
embeded spreadsheet. The only draw back is if you add or insert the
parameters they don't show up in order.

Pete
Message 8 of 11
Anonymous
in reply to: Anonymous

And there's a but.....

Copy design can be very very slow if you have a machine referring to a
parameter IPT linked to an Excel. Vault will check back to the excel for
every part and assy which has a link to the parameters, meaning that for a
1000 item assy Vault will check up to 4000 files.... (at least in this
version, dunno about Vault 5).

Workaround: Pack & Go to new workspace location, create new ipj and add
files from new location. It will refer to the copied Excel.

Jerry


"Teun Ham (IV9 SP4 / IV10 SP3a)" nl> schreef in bericht news:5079099@discussion.autodesk.com...
Well said Pete...

Never, ever, link 100+ parts to the same Excel file. That's a beginners
mistake. Link the Excel file to one part, and derive that part into the
other parts and assemblies. You will only have one OLE link to manage.

Embedding the Excel file is an option, but I would rather see DA handeling
OLE links.

Cheers!

--
T. Ham
Mechanical Engineer
CDS Engineering BV

Dual Pentium XEON 2.2 Ghz
2 GB SDRAM
NVIDIA QUADRO4 700 XGL (Driver = 77.18)
18 GB SEAGATE SCSI Hard Disc
3Com Gigabit NIC

Windows 2000 Professional SP4
Autodesk Inventor Series 9 SP4
Autodesk Inventor Series 10 SP3a
--

wrote in message news:5078614@discussion.autodesk.com...
I am assuming you have many files referencing parameters from a common
spreadsheet. This is what I have done.

I create the spreadsheet to drive all my parameters, "Skeleton.xls" I then
embed this spreadsheet into a blank ipt file, "Seleton.ipt" I set all my
embeded parameters for export (check the export box for each). I insert
this ipt in all my parts that would have referenced my spreadsheet as a
"Derived" part with a plus by "Exported" parameters.

I can still update the spreadsheet to update all the parts by editing the
embeded spreadsheet. The only draw back is if you add or insert the
parameters they don't show up in order.

Pete
Message 9 of 11
Anonymous
in reply to: Anonymous

Jerry,

What about if you have an ipt with an embedded spreadsheet vs linked.

I have been trying a Copy Design on an assembly with 128 referenced files, and 412 parts. I think the derived part is linked to about 15 parts.

So far its been an hour and Vault is about 4% complete on a Dual processor machine, however with just Vault running the processor bare jumps off idle on occasion.

I completed the SAME task with DA including about 30 more idws and manually changing names in about an hour.

Pete
Message 10 of 11
Anonymous
in reply to: Anonymous

Your right...I have just been doing it that way for the past year. I hadn't heard about the derived part method. Actually, I haven't got a clue how to work with derived parts...sounds like I have some studying to do.

Dan
Message 11 of 11
Anonymous
in reply to: Anonymous

Check out the tutorials at www.sdotson.com

--
T. Ham
Mechanical Engineer
CDS Engineering BV

Dual Pentium XEON 2.2 Ghz
2 GB SDRAM
NVIDIA QUADRO4 700 XGL (Driver = 77.18)
18 GB SEAGATE SCSI Hard Disc
3Com Gigabit NIC

Windows 2000 Professional SP4
Autodesk Inventor Series 9 SP4
Autodesk Inventor Series 10 SP3a
--

wrote in message news:5079449@discussion.autodesk.com...
Your right...I have just been doing it that way for the past year. I hadn't
heard about the derived part method. Actually, I haven't got a clue how to
work with derived parts...sounds like I have some studying to do.

Dan

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report