Rollups

[sharicarlson13]

Summary of need: There are several lookup relationships in the OFM package - would be beneficial to add rollup to display values on parent objects through system. Need to first gather requirements and determine real need, then design a near-term, no-code solution.

[sharicarlson13]

Requirements

What are the relationships that will need rollups? Funding Request to Funding Program (parent) Total Number of Requests Total Amount Requested Total Number of Awards Total Amount Awarded Total Amount Disbursed

Total Program Amount

• could be populated from GAUs or where the funds are coming from
• GAU vs Funding Program - some don't use one or the other
• multiple GAU funding to a single Funding Program, multiple funding programs can be funded from a single GAU
• roll up from GAU - need a relationship between GAU and Funding Program
• see last sprint conversation about connect GAUs to Programs

Potential Use Case: Given a GAU amount entered in to GAU when those amount are approved, then that amount should be populated in program amount field. When that amount is amount Best option: Module/screen move the amount to Funding Programs as needed.

Possible solution instead of a roll up: Use the GAU Disbursement on the Funding Request go down the relationship tree - to pull in the funding programs tracking - vs budgeting - could put chart to showing programs for tracking purposes

Funding Request and Contact Total Number of Applications Total Amount Awarded First and Most Recent Funding Program Applied Most Recent Funding Program Awarded First Application Date Active Applications

One example: for a client had to build/update on Status - whether a funding request is closed won or open (awarded but not fully disbursed)

Repeat the above for Accounts as well

Requirement to Funding Request Next Requirement Date Next Requirement Due Type

Approach Potential tasks for tomorrow Build fields Chose your own adventure - builds/instructions

Dream would be - Customizable rollups

A stretch - create flow template to include in post deployment steps via meta deploy

CCI - post deployment step - templated flows

[JurgenPeters]

Standard en custom objects

Op wo 10 feb. 2021 om 22:05 schreef sharireily notifications@github.com:

Requirements

What are the relationships that will need rollups?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/SFDO-Community-Sprints/OutboundFunds/issues/12#issuecomment-777034900, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADDFVOLIHWFATZELIBACARLS6LYILANCNFSM4XNVGVIA .

[Nickers3]

[Nickers3]

• David developed flow
  • Will share code
  • Scheduled flow, runs nightly on all accounts
  • Options for providing to users
    • Include in post-install instructions
    • Include as a flow template

[Nickers3]

Discussed ideas of using reports on Lightning pages to capture rollups as graphs as an additional option to fields.

[Nickers3]

Tested custom report type on GAU Expenditures using field lookups to parent and grandparent records to use as graphs for pages

[DavidChater]

Scibed notes from Day 2

Outbound Funds – Reporting and Roll ups

Core Issue There are some common use cases/gaps in analysing data within OF For security and sharing reasons (as well as flexibility of the data model) Master-Detail relationships are kept to a minimum. We want Low/No code solutions Discussion Roll-ups are best used where they help drive business logic (preventing multiple applications per round, flagging next outstanding requirement etc) Other needs could be better handled through report charts on key records (Funding Programme, GAU etc) Core example roll ups would be Count of Requests, Sum of Requested Amount, Count of Awarded Requests, Sum of Awarded funds Currently no Dashboards out of the box for Outbound Funds. This feels like a gap Potential to use Snowfakery, including an OF Snowfakery recipe. This would be particularly useful to populate Dashboards and Reports

Sharing the Outputs For this work the Principle of a lean offer that let’s people adapt, amend and make edits to the core components If building a Flow for the Roll Ups, it needs to be separate to the core Managed Package to prevent the issue of incrementing Flow Versions with each release (and eventually breaking) It could be possible to deploy it as an inactive flow that users can adapt and edit Or it could be part of the post-install process

[Nickers3]

Document Pros/Cons with different solutions (Flows, DLRS, etc).