Bypass Operating Model with import?

We are on 2023.8 and have noticed we can upload attributes to an asset that do not exist in that asset type’s assignment (via the import function and rest api). For example, we can add the Note text field on a Column asset - though that attribute is not available on Column and does not appear in the ‘add characteristic’ dialog. The Note attribute does not appear on the Column asset page, however it will show the values if you create a view and expose that attribute.

We’re told this is intentional - this bypass of the operating model. Would like to know the community’s thoughts as to advantages of this - we can think of plenty of disadvantages - esp in our federated model.

Elizabeth Amorosi

Posted 2 years ago · Edited 2 years ago·Last reply 2 years ago

2 comments

iljatarans

·2 years ago · Edited

elizabeth.amorosi:

this bypass of the operating model. Would like to know the community’s thoughts as to advantages of this - we can think of plenty of disadvantages - esp in our fe

It was so historically, when you programmatically upload relations/attributes to an asset but those relation types and attribute types are not configured in a Scope. As a result, end user doesn’t see it, but it exists. And once you will add setting it magically appears in Collibra User interface. Think this is a bug, rather than a feature, because API’s should behave in the same way as User Interface.

stefan_busch

·2 years ago · Edited

I actually like this feature and also use it.
One thing you can do with it is to store data that normal users can not see but that can be accessed via api.