Content version for CAD

[Former Member]

hi all

As Daniel has explained

content version will retain the files in same doc.

How the content version will work for assemblies

i mean

if i create an assembly asm/iam/000/01

it will take the activated content vesion of individual parts.

Now lets create a normal version of assembly as asm/iam/000/02

im not able to understand how it ll pick the files...

can anyone has any document or can guide me on this..

my mail id is niranjandandekar@hotmail.com

thanks

Niranjan

[daniel_huber · Accepted solution]

Hi Niranjan,

it works as well for assemblies. You need the same setting for the assembly file (the assembly has probably a different document type).

The thing that might happen is that for a specific assembly there is no content version available with the same time stamp. So it checks out those parts that are valid at this date.

I don´t think this works well with different versions. But imagine you start your work in version 1, the assembly is not released and you want to get back to the state from 3 weeks ago... What you can do as well with this functionality is to set an older content version active.

Regards,

Daniel

[sdalmaso · Accepted solution]

Hi Daniel,

I'm looking for more detailed info on content versions and this old thread is the best I find!

I hope you all will apologize me if a little off topic.

There is a way to limit the number of content versions stored to the last n? Is it achievable by customizing or some code should be written?

Second question, how to delete some content versions if required?

Wish you find the time!

Thanks in advance

Samuele

[se_kie]

See also https://answers.sap.com/questions/13478192/management-of-originals-content-versions-in-dmsect.html?c... .

[daniel_huber]

Ni Niranjan,

the difference between versions and content versions is simple:

Every new version has an independent meta data record (DIR), so you can have different meta data, status, classification data, object links for different versions.

If you work with content version then for example content version 3 has the same meta data as content version 5.

It is correct that you can define - depending on your document status - if content versions are created for your document. In most cases you define that status 'in work' or in your example 'in preparation' has content versions, the others probably not. So, your example would make sense but it is not necessary to change the version when status is changed from 'in prep' to 'for review'.

Best regards,

Daniel

[Former Member]

Ya

thanks

thats cool

i just forgot @ Meta Data

u r absolutely right sir.

Niranjan

[daniel_huber]

Hi Niranjan,

sorry that I confused you. Now I got a better understanding of your question. I assume most cases will work well even if you mix versions and content versions.

So basically if you create and check in a new version of an assembly a Bill of documents is created in the background.

e.g. asm1/iam/000/02 contains

- part1/ipt/000/01

- part2/ipt/000/01

- part3/ipt/000/01

Even if you create a new content version of one of the parts always the latest content version is loaded when you check-out the assembly. But you have the possibility to check-out an earlier content version as well.

For the other example (versioning) you have the possibility to use 'Display options -> last versions' to load the assembly with the new version of the part but basically it depends on your development process if you should create a new version of the assembly as well.

Regards, Daniel

[Former Member]

Thanks for explaining Daniel.

However i have 1 more Question for u

What is the exact difference in version and content version

for <b>Part1/ipt/000/01</b> and <b>part1/ipt/000/02</b>

and content version of part1

i mean the content version is like Version during specific Status of a document.

Can we say that

During Status --- <b>In Preparation</b>

we can use content version

and

when we want to change the status of

<b>part1/ipt/000/01</b> to <b>For Review</b>

we change version to part1/ipt/000/02

<b>for this status <i>(For Review)</i> we will not put content version active.</b>

can we use this feature this way?

Niranjan

Points awarded

[Former Member]

Thanks

but then why the versions are used?

<b>part1/ipt/000/01

part2/ipt/000/01

part3/ipt/000/01</b>

and an assembly

<b>asm1/iam/000/01</b>

Now whenever i change my part (part1/ipt/000/)

i can save it as new version or content version.

like

part1/ipt/000/<b>01</b> -

---

> part1/ipt/000/<b>02</b>

or part1/ipt/000/01 with content version.

now when i change part i have to update asm aswell

what should i do for asm for both cases

im totally confused.

Thanks

Niranjan