ADS and P360-Record counts doesnt match

[ThulasiP3]

Describe the bug ADS and P360 search result count does not match .This scenario is inconsistent.We have to manually clear the search Cache from ADS and P360 searches to resolve the issue

To Reproduce Steps to reproduce the behavior:

1. In P360 ,Through patient look up .Go to vitals and measures search . record count is 10
2. Run the same query on ADS .The record count is 245 which is expected(refer attachments) 3.Clear cache from both ADS and P360 search(vitals and measures) 4.Now ,P360 matches the record count of 245.

This behaviour is also reported by the client but the scenario is inconsistent. Attachments: error.docx

Expected behavior Row counts should match .User should not achieve it by clearing the cache

Additional context Build no : Region : Client :

[kilam005]

@ThulasiP3 Please include details of the product version.

[ThulasiP3]

ADS version - 2024.08.45507_RC6 P360 version - 2024.08.45510

[VikramSelvadurai]

RCA During search test, instead retrieving directly and entry is made into cache entity.. so while performing patient lookup with same test payload we are getting only 10 records. tempCache boolean that has to be sent to ADS is being sent as false instead of true Fix Detail update boolean to true while testing result

Local SS:

[VikramSelvadurai]

Server SS:

[kilam005]

@P3IND0167 Please test and once confirmed to work fine, add the verified and Awaiting release tags

[P3IND0167]

Ok @kilam005

Validated in test server , adding screenshots for reference

P360

Patient lookup screen

ADS Side Screenshot Reference

[kilam005]

@ThulasiP3

The issue is addressed in the latest build (P360 v2024.09.45555) Link to the build shared on email on Sep 30. If you have not received the email, kindly reach out to support team for build details.

Please udpate your environment with this build and verify.

[kilam005]

@ThulasiP3 Its been more than 10 days since we gave the release. Please validate the fix and provide a closure. if no repsonse / concerns is received by 18th October this issue will be auto closed taking testing team's verifiied confirmation

[ThulasiP3]

Hi,

Requested for deployment in Fairview .We will validate and post back ASAP.

Thanks, Thulasi.

From: Malik @.> Sent: 10 October 2024 22:16 To: P3-Core-Dev-Team/P3-Q-A @.> Cc: Thulasi Paramananthan @.>; Mention @.> Subject: Re: [P3-Core-Dev-Team/P3-Q-A] ADS and P360-Record counts doesnt match (Issue #132)

@ThulasiP3https://github.com/ThulasiP3 Its been more than 10 days since we gave the release. Please validate the fix and provide a closure. if no repsonse / concerns is received by 18th October this issue will be auto closed taking testing team's verifiied confirmation

— Reply to this email directly, view it on GitHubhttps://github.com/P3-Core-Dev-Team/P3-Q-A/issues/132#issuecomment-2405595650, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BLRJQVQEKEL6GHWXBW7RS3TZ22VLDAVCNFSM6AAAAABOZRVBXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBVGU4TKNRVGA. You are receiving this because you were mentioned.Message ID: @.**@.>>

[kilam005]

@ThulasiP3 For P360 we dont own the region and we never deploy. The details about the instalation and upgrade are provided with the package. Please update, check and confirm and provide the closure.

Like previous mentioned if no closure or concern is raised before 18th October, this will get auto closed

[kilam005]

@ThulasiP3 Reminder: Issue will be autoclosed if no action is taken on 21st Oct

[ThulasiP3]

Build verified.. Unable to see the issue being replicated now.

[kilam005]

Closing based on above commment