Skip to content

[FIX] cash location_ids#69

Merged
chelsea-EYDS merged 2 commits intomainfrom
FIX-cash-location_ids
Mar 3, 2023
Merged

[FIX] cash location_ids#69
chelsea-EYDS merged 2 commits intomainfrom
FIX-cash-location_ids

Conversation

@chelsea-EYDS
Copy link
Contributor

FIX

Objective:

  • When the column for the pt_location_ids in the cash deposit table was last updated, the logic for the location lookup for cash reconciliation had an error if a location id was passed in with the reconciliation event. If a location_id is passed in to the recon event, this location_id should be used to lookup pt_location_ids, rather than expecting a pt_location_id to be passed in with the event.

@chelsea-EYDS chelsea-EYDS temporarily deployed to dev March 3, 2023 01:58 — with GitHub Actions Inactive
{
"fiscal_start_date": "2023-01-01",
"fiscal_close_date": "2023-02-27",
"fiscal_close_date": "2023-03-02",

Choose a reason for hiding this comment

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

This range is just for testing purposes, right? What's the best way to mark it so that it gets changed to the real fiscal year before this is being used in production?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think we could remove the dates from the event and just use an environment variable to set the date. If the plan is to run reconciliation daily starting from the start of the fiscal year, or quarter, etc, then we shouldn't need to pass these in.
We also probably don't need the option to pass in locations or programs either. It makes sense to look up by location for reporting, but if this is meant to run daily for all locations and programs then we can set these with env vars... I think we weren't clear on the criteria so it was left as flexible as possible for the time being.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

(I think this is something we should clarify with the team though and could be handled in another PR as this one will unblock testing).

@chelsea-EYDS chelsea-EYDS requested a review from jwarrenbc March 3, 2023 17:48
Copy link

@jwarrenbc jwarrenbc left a comment

Choose a reason for hiding this comment

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

TO DO: figure out how to handle fiscal dates

@chelsea-EYDS chelsea-EYDS merged commit a4cfb0d into main Mar 3, 2023
@chelsea-EYDS chelsea-EYDS deleted the FIX-cash-location_ids branch March 13, 2023 20:26
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