Orphaned Records Matrix
This page covers:
Orphan Record Issue has been resolved: This resource is not actively updated
With the Amp Impact Fornax (1.27) release, the users are not able to delete the Parent records if there is a related child record in the org and will get an error message asking them to delete the child records first.
Glossary
Action Taken: What object record is being deleted?
How is Action Taken: What steps is the user taking to complete the action in Amp Impact?
Orphaned Records?
Yes - the field on the child record is cleared and the child record is orphaned.
No - the child record retains information from the parent record OR the child record is deleted along with the parent record.
Historic Result Data Preserved?
Yes - the child records are not deleted when the parent record is deleted.
No - the child records are deleted when the parent record is deleted.
Status:
No change - Amp Impact works as intended.
Backlog: dev change request - Amp Impact currently works this way but we have backlogged a user story to change this.
Backlog: config change request - Amp Impact currently works this way but we have backlogged a config change to change this.
Orphaned Result Records Matrix
Action Taken | How is Action Taken (through Amp Impact)? | Orphaned Result Records? | Historic Result Data Preserved? | Notes | Status |
---|---|---|---|---|---|
Delete a Project Geographic Area (PGA) |
| Yes | Yes |
| Backlog: config change request |
Delete a Reporting Period (RP) |
| Yes | Yes |
| Backlog: config change request |
Delete a Project Indicator (PI) |
| No | No | Child result records are deleted when PI is deleted | No change |
Delete a Catalog Indicator |
|
|
| Can’t delete a catalog indicator if PI is related to it | No change |
Delete a Project Indicator Geographic Area (PIGA) |
| Yes | Yes |
| Backlog: config change request |
Delete a Project Indicator Reporting Period (PIRP) |
| Yes | Yes |
| Backlog: config change request |
Delete a Disaggregated Indicator (DI) |
| No | Yes | Deleting a DI (related to parent indicator of PI) has no effect on PI or its child Results | No change |
Delete a Disaggregated Project Indicator (DPI) |
| Yes | Yes |
| Backlog: config change request |
Delete a Disaggregation Group |
| Yes | Yes | Child results related to child Disaggregation Values of deleted Disaggregation Group are not displayed on STAR if DG related to parent PI is deleted | Backlog: config change request |
Delete a Disaggregation Value |
| Yes | Yes | Child results related to deleted Disaggregation Value are not displayed on STAR if DV of DG related to parent PI is deleted | Backlog: config change request |
Orphaned Records Matrix
Action Taken | How is Action Taken (through Amp Impact)? | Orphaned Records? | Historic Data Preserved? | Notes | Status |
---|---|---|---|---|---|
Delete a Thematic Area (TA) |
|
|
| Thematic Area field on Indicator and Project indicator record retains the Thematic Area value | Backlog: dev change request |
Delete an Indicator Thematic Area (ITA) |
| NA | No | Thematic Area field on Indicator record doesn’t retain the Thematic Area value | No change |
Delete a Project Indicator Thematic Area (PITA) |
| NA | No | Thematic Area field on Project Indicator record doesn’t retain the Thematic Area value | No change |
Delete a Budget |
|
| No |
| No change? |
Delete an Objective |
|
|
| When a catalog objective is deleted, the related Project Objective record retains the objective name and definition but related Project Indicator Objective doesn’t. Objective(s) field on Project Indicator retails the Objective Name | Backlog: config + dev change request |
Delete a Project Objective (PO) |
|
| No | Objective(s) field on Project Indicator record doesn’t retain the Objective value | No change |
Delete a Project Indicator Objective (PIO) |
| NA | No | Objective(s) field on Project Indicator record doesn’t retain the Objective value | No change |
Delete an Implementation Plan |
|
| Yes |
| No change |