Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Null Value in individual.encounters #731

Open
2 tasks
Tracked by #1614
BEULAHEVANJALIN opened this issue May 29, 2024 · 1 comment
Open
2 tasks
Tracked by #1614

Null Value in individual.encounters #731

BEULAHEVANJALIN opened this issue May 29, 2024 · 1 comment

Comments

@BEULAHEVANJALIN
Copy link

BEULAHEVANJALIN commented May 29, 2024

Describe the bug
There is a variation between the web app and the mobile app on the retrieval of individual.encounters and individual.enrolments in form element rule. Mobile shows these objects correctly when they exist, but the web app doesn't even though the objects exist.


To Reproduce
Steps to reproduce the behavior:

  1. Try logging the individual object.
  2. Check theindividual.encounters and individual.enrolments fields in the logged result.

Screenshots
image

image

Additional context
There is a requirement from Ashwini to autopopulate the value from one encounter to another. For that, I need a list of encounters. Even the prototype is resulting in an empty array, so there is no way to retrieve the data currently.


Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Developer Checklist
Developer fixing the bug should fill this checklist.

  • Does the fix require extensive regression testing?
  • Are you mentioning the required scenarios that could be affected?

@mahalakshme
Copy link
Contributor

@BEULAHEVANJALIN the above was in form element rule right? Can you add that as well in the description, because different rules are executed in different context - will help in fixing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: New Issues
Development

No branches or pull requests

2 participants