Forum Discussion
Funny to be competing against CHAT GPT now. It's a new world, huh?
If it wuz me I would have the single source of truth being the child log table and use a summary field to roll up the current status. Then I know for sure that there can never be a mismatch between the most recent child record and the status on the Parent as it's driven by summary fields and formula as opposed to an Automated Pipeline which can theoretically fail.
I would probably do a summary maximum of the [Record ID#] of the most recent Child DECISION STATUS CHANGE, and then a reverse relationship where One DECISION STATUS CHANGE has many REQUEST DECISIONS based on that Max Record ID# field. Then look up the value of the most recent decision, and who entered it and when up to the decision record.
If a reverse relationship seems too weird or too cluttered to you then you are free to use Combined Text Summary fields and summary maximum fields to summarize up certain fields from the the most recent record up to the Parent based on a filter that the child record [Record ID#] is equal to that Maximum Record ID# field which you summarized up to the parent and then would lookup back down to the child.
- kheatley15 days agoQrew Member
Mark
Thanks for quick reply. I actually have had some help from Don in setting this app up. He helped me set up what you mention above (Max RID#) and I have a button in my REQUEST DECISIONS report that allows an approver to make their decision via the button, which saves the record in DECISION STATUS CHANGES table that is pulled into REQUEST DECISIONS via Max RID.
Button formula: If([LEAVE REQUEST - LEAVE STATUS]="FINAL APPROVAL", "", URLRoot() & "db/" & [_DBID_DECISION_STATUS_CHANGES] & "?a=API_GenAddRecordForm&_fid_26=" & URLEncode ([Record ID#])& "&dfid=11" & "z=" & Rurl())So you're saying that you would go with the opposite recommendation from chatgpt?
- MarkShnier__You15 days agoQrew Legend
I guess what I'm saying is that independently Don and myself had the same recommended solution. Your source of truth is the Child table and you flow the most recent status update up to the parent record using formulas and summary fields which can never fail. So yes, imho, our two brains are smarter than Chat GPT.
Under the Chat GPT recommended solution you can have a theoretical mismatch between the children and the parent record status, then you might need to have a safety net report to detect those differences and manually correct them.