Open ChristinaTremel opened 1 month ago
@ChristinaTremel I took a look at the code for this and we made some assumptions about the task orders data that I don't think hold true anymore. This docstring explains better whats going on.
We're using that TASK_ORDER_ID
field as the primary key and if there are duplicate TASK_ORDER_ID's we "coalesce" by just commas separating all of the BYR_FDU's into one text field. It looks 24ART01073 has different data all across all of the fields, not just BYR_FDU so we will need to rework this if we want it to behave differently. I hope this helps
ohhh so is the issue that there are multiple rows of the same Task_Order_ID
that have differing BYR_FDUs
?
I think we use the same assumptions as long as we could add an additional factor of using that TASK_ORDER_ID field as the primary key and only coalescing the TKs where DEPT code is the same. Would that be a somewhat easy adjustment to make?
Ah I see now they're from different departments. Uhh I think it would be fairly easy to do that but I'm a little concerned that it'll break something else. It makes me wonder how many TASK_ORDER_IDS are in multiple departments?
It should only be between 2400 and 6200! When the departments merged in October, finance deactivated all of the TKs in DEPT 2400 and created these TKs again in 6200 (our new DEPT code). I confirmed this with Sharon and she said:
A TK can have 2 FDU's with different funds so yes. Not sure about those FDU's having diff depts tho -meaning 1 with a 2507 FDU and one with a 6207 FDU? I can't say it will never happen since we are now merged but we don't have any right now!
Diana and I were chatting about this and were thinking for the two Knack apps that we know of that use this view (Data Tracker and the Finance and Purchasing app), we couldn't think of anything that it could potentially break. But before we make the change we could definitely export some of the objects using task orders to have back ups just in case.
So we still want to be able to view both? I see they have different balances and stuff.
We would want to view both! I showed Finance this information and they said it's normal for them to have different balances - When they transitioned the money to the Task Order under the new department code they only moved the remaining TK balance and then divisions continue to add funding to active task orders!
@ChristinaTremel cc @stephaniemoorer Do we know the status of this? Sharon emailed this passed weekend asking if it's in the system yet.
Active TKs in DEPT 6200 (that were moved from 2400) are not pulling into Knack applications.
AMD Data Tracker Search Results
DEPT_2400_TK_VW Search Results
The SQL view shows the active TK, but that TK is not available in Knack. Need to troubleshoot why that might be happening