Feature/add applicant org county data #402
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issues:
Main Changes:
Update BAP query for 2023 PRF data to fetch the applicant organization county and inject that into a brand new 2023 PRF submission
Steps To Test:
NOTE: because we're creating multiple submissions with the same SAM.gov entity when testing, the BAP query returns the latest county value stored in the applicant organization Salesforce record, which looks like it's being updated every time the ETL runs with whatever the last county value was used for that SAM.gov entity in a FRF submission.