cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

ContentCenter Propertyset and property IsCustomPart

ContentCenter Propertyset and property IsCustomPart

There is also a Property available in the "ContentCenter" Propertyset with called "IsCustomPart".

For real Content Center Files placed as Standard the Value of IsCustomPart = 0

For real Content Center Files placed as Custom the Value of IsCustomPart = 1

 

This would help us a lot when this would be available to read/map in Vault too!

9 Comments
ihayesjr
Community Manager

@bradeneuropeArthur 

What would this property value help you do if you can read it?

johnsonshiue
Community Manager

Hi Arthur,

 

When a CC part is inserted as a custom CC part, it just behaves like a regular part. Any editing workflow allowed in a regular part will be available to the custom CC part. I am not aware of a workflow locking Part Number or certain properties in a regular part.

I understand this is a wish but I am not sure how it would be fulfilled.

Many thanks!

 

To put them is a specific category "Content Center Custom" this will help for example:

  • With Copy Design you can then easily check that the partnumber is not updated.
  • different Lifecycles
  • etc
ihayesjr
Community Manager

Why not add a custom iProperty to your custom content center parts which will allow you to map that property and assign the appropriate category to it?

Why not let autodesk add the possibility to read all yes all possible properties in Vault.

This would prevent us from unnecessary copying of families!

ihayesjr
Community Manager
Status changed to: Archived

@bradeneuropeArthur 

The IsCustomPart is not an iProperty which is why it cannot be read by Vault. Your idea would have to be first implemented by the Inventor team. Once IsCustomPart is an iProperty, Vault should automatically be able to read it. I am just trying to give you an option to implement to solve your needs now.

 

Please post this idea on the Inventor Ideas board. It has to be implemented on the Inventor side as an iProperty.

@bradeneuropeArthur 

The IsCustomPart is not an iProperty which is why it cannot be read by Vault. Your idea would have to be first implemented by the Inventor team. Once IsCustomPart is an iProperty, Vault should automatically be able to read it. I am just trying to give you an option to implement to solve your needs now.

 

Please post this idea on the Inventor Ideas board. It has to be implemented on the Inventor side as an iProperty.



I know and I appreciate that.

You need to understand that if it is easy to read other i-properties for the Vault team Like "IsContentCenter" than I ask myself the question why is it not possible to read all i-properties that are available.

 

There is a big difference between the Theory and the Practice. In theory it it not needed here but in practice we see different.

It would make so much easier to have the ability to read all than filter things out.

Regards,

If these properties are available in Inventor, I prefer that they can be read easily into Vault properties and mapped, without specialties.

Hope that this general remark will clarify for you!?

Regards,

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

Submit Idea