An admin wants each record of a custom Project object to point to a parent project, and plans to use the hierarchical relationship type that builds management chains. In the new field wizard on Project, that type can't be used. Why?
Choose an answer to check it. Afterward, select any option to review its explanation.
Being a master is about controlling detail records, such as their deletion and who can view them. That isn't a precondition for another relationship type; the restriction here comes from which object the field is on.
This is a real rule, but for master-detail relationships: the field goes on the detail side. It says where a master-detail field lives, not why the hierarchical type is unavailable on Project.
Schema Builder can indeed create relationship fields, which makes this tempting. But it is another way to build the same field types, not the only place, and it doesn't unlock a type that the object can't have.
A hierarchical relationship is a special kind of lookup, but it is limited to the User object, where it models chains such as manager and employee. A custom object like Project can't use it, whatever the data looks like.
id q37abd2238a