Same-Table Relationship

Question

I have a complex multi-table App used as a Project Management System that supports our End-to-End process from Intake, Governance, Prioritization, Resource Assignments, Status Updates, Multiple Releases, Risks/Issues, Actions, Decisions, Change Requests, etc.&nbsp; &nbsp;Our main Project Table has 17 traditional Parent/Child relationships.We now need to create a 'Same-Table Relationship' to associate numerous projects that are funded under a Big Brother (sibling) project.Use Case:

Some projects are funded uniquely and do not have associated sibling projects that are associated.&nbsp;&nbsp;
Some projects are Big Brother Projects that are managed as a big complex project and also provide funding for Little Sibling Projects (that are not uniquely funded).
All Projects that will be funded have a Yes/No condition whether or not the project is a Funded project which also means that it is eligible to be a Big Brother project from a funding perspective.
The creation of the funding relationship between the Little Sibling Projects and their associated Big Brother Project (which is both a project and a funding source for Little Sibling Projects) will be done be Portfolio Managers AFTER the Little Sibling Projects have been added through our normal intake process.&nbsp; &nbsp;

We would identify that the smaller project will NOT be uniquely funded in a SAFe Triage (governance) meeting.
We would then like to 'relate / associate'&nbsp; these Little Sibling projects to an appropriate Big Brother Projects via a drop down of 'Funded Projects'.&nbsp; &nbsp;(Drop Down would include the list of Projects for which the Funding Yes/No condition is Yes.)
Once the relationship is established, we would report on the rolled up work effort needed for Little Siblings as unique Project rows associated to the Big Brother project.&nbsp; &nbsp;
From an Accounting perspective, only "Funded Projects" are eligible for budgets/actual/projected $.&nbsp;

We do NOT see this relationship as Parent / Child Projects due to:

All projects (Big and Small) have the same need for relationship to all of the traditional children tables for unique details associated to resources, status reports, governance, decisions, risks, value proposition, attachments, etc.&nbsp; &nbsp;
The only differentiator from a Big Brother project to a Little Sibling project is that the Little Sibling is not uniquely funded, but derives is funding from the Big Brother project.

Where we are struggling:

We have the Same-Table Relationship created, created test rows of funded and non-funded test projects.&nbsp; &nbsp;We know the relationship from a funding perspective, but are struggling on how to 'relate' the Little Sibling projects to the Big Brother projects.&nbsp; &nbsp;

The Add function tries to create a new project.&nbsp; &nbsp;These projects will not be created New from this relationship.
We wish to simply 'relate' the existing Little Sibling projects to an existing Funded Big Brother project via a drop down of approved Big Brother projects.&nbsp; &nbsp;(If a Portfolio manager makes a mistake, we would want to alter the relationship when the mistake is discovered.)

Thanks in advance for any guidance you can provide.&nbsp; :)------------------------------Annetta Coleman------------------------------

marcelobenavide · Answer

Hello, Something like this occurs to me:Thank youMarcelo BEnavides Torres

annettacoleman · Answer

Marcelo -&nbsp; A bit more complex than your relationship.Project B may be a&nbsp; Big brother and have 30 Sibling projects associated to it&nbsp;Project D may be a Big brother with 5 sibling projects associated to it.Project H may be uniquely funded with 0 siblings associated to it (other than itself)Conceptually we have it mapped.&nbsp;&nbsp;Tactically we are not sure HOW to relate a sibling project to its Big Brother via a Same-Table relationship.&nbsp; &nbsp;We envision this as a dynamic drop down list of projects that are already approved to be approved as a funding source.&nbsp;&nbsp;

------------------------------Annetta Coleman------------------------------

marcelobenavide · Answer

It occurs to me to create a flag to know if a project can be big brother and a field to know who is the big brother of a sibling, create a report filtering the projects marked as big brother, put the result of that report in a ComboBox ( second field ) and so when you create a sibling you can associate it with one of the possible big brothers.

annettacoleman · Answer

Hi Marcelo -&nbsp;Yes, we already have the flag to determine if the Project is Funded (and thus eligible to be a big brother) and also a field to know who the Big Brother is (for projects that are not uniquely funded).&nbsp; &nbsp; &nbsp;We envision that the field that identifies the Big Brother project is a drop down.&nbsp; &nbsp;I do not see reference to ComboBox in QB help.&nbsp; &nbsp;Can you provide a link to an article?&nbsp; &nbsp;Is this a Report Link?------------------------------Annetta Coleman------------------------------

marcelobenavide · Answer

I apologize, I was in another project and I have digressed in different programming languages.... It does not allow filtering by the flag field that defines if it can be a big brother, to achieve this you have to have at least one table where only the possible big brother.

Forum Discussion

Same-Table Relationship