Incorrect TB Screening Count & Sync Status Not Updating Automatically

XMLWordPrintable

    • Type: Bug
    • Resolution: Done
    • Priority: High
    • 2.0
    • Affects Version/s: None
    • None
    • STOP TB Sprint 5

      When TB Screening is completed for one beneficiary, the count is incorrectly displayed as 2 instead of 1. Similarly, when screening is done for a second beneficiary, the count increases to 4 instead of 2, indicating duplication or incorrect calculation logic.

      Additionally, even when the Camp Hub is connected, the completed TB Screening records are shown under the Un-synced column instead of being automatically synced. The data only moves to the Synced column after manually clicking the Refresh button.

      Steps to Reproduce:

      1. Go to Beneficiary list
      2. Fill TB Screening form for one beneficiary
      3. Navigate to Dashboard / Sync Summary
      4. Observe TB Screening count
      5. Fill TB Screening for another beneficiary
      6. Check the updated count
      7. Observe Sync status without clicking refresh

      Actual Result:

      • TB Screening count is incorrect (1 → 2, 2 → 4)
      • Records appear in Un-synced even when connected
      • Sync happens only after manual refresh

      Expected Result:

      • TB Screening count should be accurate (1 → 2 → 3…)
      • Data should auto-sync when Camp Hub is connected
      • Records should directly appear under Synced

           

        1. image-2026-08-07-15-29-16-657.png
          52 kB
          Nidhi Saini
        2. image-2026-08-07-15-29-36-775.png
          50 kB
          Nidhi Saini
        3. image-2026-08-11-16-11-51-029.png
          97 kB
          Nidhi Saini
        4. image-2026-08-11-16-12-52-017.png
          113 kB
          Nidhi Saini
        5. image-2026-08-12-12-54-52-158.png
          88 kB
          Nidhi Saini

              Assignee:
              Nidhi Saini
              Reporter:
              Nidhi Saini
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: