You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A clear and concise description of what the bug is.
@jingtang10@aditya-07
Fhir engine converts List resource to Binary resource while syncing. The change log in LocalChangeEntity is correct, But while uploading the resourceType is converted to binary and the data is something entirely different.
@mansikalraa Can you provide the data (maybe the LocalChangeEntity of List/569) for us to debug the issue that the Binary data is completely different ?
The PATCH's data is basically Base64 encoding of the LocalChangeEntity.payload and incase List/569 has more than one LocalChangeEntity (multiple changes made to the list resource on device before sync), then all of these LocalChangeEntity are merged (as per Json Patch Merge) to create a single LocalChangeEntity.payload and sent up in a PATCH to the server.
Describe the bug
A clear and concise description of what the bug is.
@jingtang10 @aditya-07
Fhir engine converts List resource to Binary resource while syncing. The change log in LocalChangeEntity is correct, But while uploading the resourceType is converted to binary and the data is something entirely different.
Due to this the syncing process fails entirely, which is causing us the loss of important data.
Component
Core library (Fhir engine)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
The resourceType of List resource should not be changed to Binary, and the syncing process should work correctly.
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
Would you like to work on the issue?
Please state if this issue should be assigned to you or who you think could help to solve this issue.
The text was updated successfully, but these errors were encountered: