Setting newly created attribute using bulk asset action
I have just added a new mandatory attribute to a certain asset type. I believe I've done it correctly because I can now set this attribute on existing assets and also create new assets with this attribute.
However, I am having difficulty in setting this attribute when in "bulk edit" mode. On the drop-down menu of the available attributes to set, I can see many other pre-existing attributes but not the one I just created. Perhaps I have missed a step somewhere. Any help will be greatly appreciated.
Accepted answer
Is your asset type where you configured the attribute an asset type at your community level, or is the asset type configured for the attribute at the master repository level?
It looks like there is a bug for BulkUpdate that it doesn't take the assets community into account for the asset type configuration. So if the attribute was configured at the community level then BulkUpdate won't see it.
It looks like there is a bug for BulkUpdate that it doesn't take the assets community into account for the asset type configuration. So if the attribute was configured at the community level then BulkUpdate won't see it.
Comments
I see what you mean. This is what I did:
- Create the new attribute
- Add the attribute to the attribute constraint list for the asset type at the community level (via the asset type tab in community administration, override must be checked since this attribute was not added to the global asset type)
What I should have done:
- Create new attribute
- Add the attribute to the attribute constraint for the asset type at the global level (via the asset type item in the Repository Administration sidebar, note there is no check box to override global level since this is the global level)
Thank you for your help!
Thanks. Could you please open a defect on this against RAM in Jazz.net? We should be handling community level asset type overrides too.
Defect # 75098