View Revisions: Issue #5989

Back to Issue
Summary 0005989: Details in Load Screen can contain information for the incorrect load
Revision 2023-09-22 19:20 by cquamme
Description Currently, if there are 2 or more loads with the same load ID in the loads screen, when you go to select the details screen for a load, you may not get the correct details for that load. This is because the details screen is not getting the node information, only the load ID.
Revision 2023-09-25 16:26 by cquamme
Description Currently, if there are 2 or more loads with the same load ID in the loads screen, when you go to select the details screen for a load, you may not get the correct details for that load.

Issues:
1. The completed table count will be incorrect because we were getting the completed tables based on the node ID and load ID. We also need to take into account the source node ID so we don't count tables for a different node.
Revision 2023-09-25 17:06 by cquamme
Description Currently, if there are 2 or more loads with the same load ID in the loads screen, when you go to select the details screen for a load, you may not get the correct details for that load.

Issues:
1. The completed table count will be incorrect because we were getting the completed tables based on the node ID and load ID. We also need to take into account the source node ID for incoming loads and the target node ID for outgoing loads so we don't count tables for a different node.
Revision 2023-09-25 18:07 by cquamme
Description Currently, if there are 2 or more loads with the same load ID in the loads screen, when you go to select the details screen for a load, you may not get the correct details for that load.

Issues:
1. The completed table count will be incorrect because we were getting the completed tables based on the node ID and load ID. We also need to take into account the source node ID for incoming loads and the target node ID for outgoing loads so we don't count tables for a different node.
2. The current table reload request can sometimes be wrong, because the query we were using did not take into account the source node ID for the load you are selecting.