Field Name
|
Field Label
|
Field Type
|
Field Description
|
| request_id | Request ID | Number | The unique CyberGrants identification number for a particular grant request. Each request in CyberGrants will have a distinct Request ID |
| final_approval_date | Final Approval Date | Date | The date of final approval for the request |
| create_date | Create Date | Date | The date a request was created |
| np_submit_date | NP Submit Date | Date | The date the Non-Profit submitted the request |
| np_resubmit_date | NP Resubmit Date | Date | The date the Non-Profit resubmitted the request. |
| funding_principle | Funding Principle | String | A single-select classification item is used to identify the primary focus that the request is meant to address |
| disposition | Disposition | String | The current status of the particular request. When a grant is either canceled or rejected, the funds for any payments made against it are returned to the budget line for use in other requests |
| np_review_flag | Has the Organization Reviewed? | String | A flag that indicates if a request was reviewed by the organization |
| external_flag | Is Request Source External? | String | A flag that indicates whether or not the source of a request is external |
| paid | Paid Amount | Number | The portion of the grant amount that has been paid. Equals the sum of a grant's payments with a Paid payment status |
| request_submitter | Request Submitted By | String | The name of the person who submitted the request |
| total_request_amount | Total Request Amount | Sum | The sum of the request amount |
| total_grant_amount | Total Grant Amount | Sum | The amount that the grantmaker has elected to approve/reject the grant for. This does not have to equal the nonprofit's requested amount |
| request_owner | Request Owner | String | The owner of the request record |
| aggregated_approval_comments | Aggregated Approval Comments | String | An aggregated list of comments left across all steps of the approval workflow |
| aggregated_approval_order | Aggregated Approval Order | String | An aggregated order of the approval type (or step) within the approval workflow |
| approval_result | Approval Result | String | The resulting decision of the approval type (or step) |
| aggregated_approver_names | Aggregated Approver Names | String | An aggregation of all approver names across all applicable steps within the approval workflow |
| approval_date_date | Approval Date | Date | The date of the approval |
| approver_resubmit_date_date | Approval Resubmit Date | Date | The date of the approver resubmit date |
| aggregated_approval_types | Aggregated Approval Type | String | The aggregated titles of all applicable steps within the approval workflow |
| impact_report_id | Impact Report ID | Number | The unique CyberGrants identification number for a particular impact report. Each impact report in CyberGrants will have a distinct impact report ID |
| available_date | Available Date (Impact Report) | Date | The date the impact report is available for the organization to begin completing |
| due_date | Due Date (Impact Report) | Date | The date that the impact report is due to be completed by the organization |
| final_approval_date | Final Approval Date (Impact Report) | Date | The final approval date of the impact report |
| np_resubmit_date | Resubmit Date (Impact Report) | Date | The resubmit date from the organization |
| np_submit_date | Submit Date (Impact Report) | Date | The date the organization submitted the impact report |
| disposition | Disposition (Impact Report) | String | The current status of the impact report |
| comments | Comments (Impact Report) | String | The comments left on the impact report |
| submit_user_full_name | Submit User Full Name (Impact Report) | String | The full name of the user who submitted the impact report |
| proposal_type | Program | String | The application type for a particular request. Grant requests may have different questions depending on their proposal type |
| budget_id | Budget ID | Number | The ID that is assigned to each unique budget line within a client’s budget structure. Each payment within CyberGrants is tied to a budget line ID |
| budget_year | Budget Year | Number | The year a budget line is derived from |
| organization_id | Organization ID | Number | The unique CyberGrants identification number for a particular organization. Each organization in CyberGrants will have a distinct organization ID |
| payment_id | Payment ID | Number | The unique CyberGrants identification number for a particular payment. Each payment in CyberGrants will have a distinct payment ID |
