Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Unticketed] Modify agency transform to ignore a new field #3672

Merged
merged 1 commit into from
Jan 29, 2025

Conversation

chouinar
Copy link
Collaborator

Summary

Time to review: 2 mins

Changes proposed

Adds a filter to the transform agency task to skip a new field

Context for reviewers

grants.gov added a new type of field to the TGroups table (the key-value table that stores agency info) which is causing the following error: Unknown tgroups agency field AllowSubmitWithExpSAM.

While I'm not sure what this field does exactly (something to do with allowing users to submit even if their SAM validation isn't done), I know we don't need to worry about it for a while as we don't yet handle anything with apply. So for now, ignoring the field so we stop erroring on these fields. We can always pick it back up later.

Copy link
Collaborator

@mdragon mdragon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved

@chouinar chouinar merged commit 10c415b into main Jan 29, 2025
2 checks passed
@chouinar chouinar deleted the chouinar/fix-agency-load branch January 29, 2025 14:29
DavidDudas-Intuitial pushed a commit that referenced this pull request Feb 7, 2025
## Summary

### Time to review: __2 mins__

## Changes proposed
Adds a filter to the transform agency task to skip a new field

## Context for reviewers
grants.gov added a new type of field to the TGroups table (the key-value
table that stores agency info) which is causing the following error:
`Unknown tgroups agency field AllowSubmitWithExpSAM`.

While I'm not sure what this field does exactly (something to do with
allowing users to submit even if their SAM validation isn't done), I
know we don't need to worry about it for a while as we don't yet handle
anything with apply. So for now, ignoring the field so we stop erroring
on these fields. We can always pick it back up later.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants