Project

General

Profile

Actions
Copy link

Bug #1685

closed

Feature #140: Technical Support, Bug Fixing and Services

Feature #1684: Version 1.8

Identify sync failed cases reported from client

Added by Thara S Pillai over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Aswathy M G
Category:
TechSupport
Start date:
11/23/2023
Due date:
11/23/2023
% Done:

100%

Estimated time:
Planned Due Date:

Description

eHealth reported sync failed errors from UAT1.
Debug issue to support or resolve.

Actions
Copy link
 #1

Updated by Aswathy M G over 2 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 90

Issues noted that
Data type mis match in UAT1 for ph_family_survey table colum last_chg_time(time) is different in UAT2 (last_chg_time(character varying)).informed to ehealth

Actions
Copy link
 #2

Updated by Thara S Pillai over 2 years ago

  • Tracker changed from Activity to Bug
  • Status changed from In Progress to Closed
  • % Done changed from 90 to 100

Communicated to eHealth

Regarding sync issue in family survey data

The log report from UAT1 application server showed a DataType mismatch error for ph_family_survey and a script comparison of UAT1 and UAT2 database showed that
the field last_chg_time of ph_family_survey has a data type of time without time zone in UAT1 and varchar in UAT2.
Please correct for this mismatch in UAT1 to proceed with upload synching of family survey data.

Regarding sync issue in device log data

The logs from device before user’s app login was inserting values 0 for User ID and Institution ID. The foreign key constraint set on ph_device_log prevented data insertion for these fields.
This is now handled using NULL values for User ID and Institution ID. The modified database function is committed in git. Please update the DB function in UAT1.

Actions
Copy link

Also available in: Atom PDF