Options
  • State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 14 subscribers
  • Views 330 views
  • Users 0 members are here
Related

parent vs owner properties

amaury.bianchi

Hello,

I thougth all the properties named Owner ("property")  where the ones used when you select any object, then create a new one with the (+) button. Then the owner property is added to the metadata card, linked to the selected object.
On other side Parent ("property") was related to the hierarchical definition of object types, in M-Files admin.

But after some testing, I am trying to doubt! I have those objects types:

  • Direction (which shows Division as a subtype
    • Division (which shows Business unit as a subtype)
      • Business Unit (which shows nothing in the subtypes)

(by "which shows xxx in the subtypes" I mean in MF Admin, in the advanced tab of the properties of the object type.)

But when I look at the property definitions, there is no "Parent (Division):

I when I create objects in MF Desktop, the properties used by the system make no sense to me: 

   

Can somebody explain this to me? I didn't see any clear documentation on this.

End goal is to use M-Files importer to create this hierarchy, so I need to know when I have to use the Parent() or Owner() property

Thanks

Parents
  • 0

    The Owner properties are used when an object type is marked as a subtype of another object type. For instance, we have a Customer object type which has a subtype Contact Person.

    Having this hierarchical relationship defined means that Contact Person objects cannot exist in the vault independently, they need to always belong to a certain Customer. Also, if you delete the parent Customer object, all the related Contact Persons will also be deleted.

    User guide: Defining an Object Type Hierarchy

    By default M-Files vaults don't have any Parent properties, the relationship is only defined on the child object's side via the Owner property and that's what you need to set with M-Files Importer as well. Have you or someone else created these Parent properties in the vault?

Reply
  • 0

    The Owner properties are used when an object type is marked as a subtype of another object type. For instance, we have a Customer object type which has a subtype Contact Person.

    Having this hierarchical relationship defined means that Contact Person objects cannot exist in the vault independently, they need to always belong to a certain Customer. Also, if you delete the parent Customer object, all the related Contact Persons will also be deleted.

    User guide: Defining an Object Type Hierarchy

    By default M-Files vaults don't have any Parent properties, the relationship is only defined on the child object's side via the Owner property and that's what you need to set with M-Files Importer as well. Have you or someone else created these Parent properties in the vault?

Children
M-Files
M-Files Support


© 2024 M-Files, All Rights Reserved.