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

titleLineage not present in address level table after sync #1478

Open
mahalakshme opened this issue Aug 20, 2024 · 0 comments
Open

titleLineage not present in address level table after sync #1478

mahalakshme opened this issue Aug 20, 2024 · 0 comments

Comments

@mahalakshme
Copy link
Contributor

mahalakshme commented Aug 20, 2024

org: any org

Issue:

Unable to do individual.lowestAddressLevel.titleLineage in rules. titleLineage is always null

Analysis:

  • titleLineage column though present in address level table in realmdb, the column is empty. It is empty even in 3.40.4 version.
  • But the presence of the column and the presence of this query when fetching locations during sync looks like the code was working sometime back.

AC:

  • Fix the issue such that titleLineage is accessible.
  • Find the root cause of the issue
  • Will fixing this affect the performance? How to mitigate this.

Need:

Based on states(highest location type), some questions in forms need to be shown and others hidden. locationMappings column in addressLevel table cant be used as a workaround, since all catchments of users don't contain locations of highest(State) location types

@mahalakshme mahalakshme changed the title titleLineage not present in address level table titleLineage not present in address level table after sync Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Analysis
Development

No branches or pull requests

1 participant