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
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
The text was updated successfully, but these errors were encountered:
org: any org
Issue:
Unable to do
individual.lowestAddressLevel.titleLineage
in rules. titleLineage is always nullAnalysis:
AC:
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
The text was updated successfully, but these errors were encountered: