Incorrect My Request Badge Count in Now Mobile

divya216
Tera Contributor

Hello,

The badge count displayed for My Requests in the Now Mobile is incorrect. When we open the My Requests, the actual number of records is displayed correctly, but the badge count shows a different value.

For example, the badge count displays 31 whereas the actual number of records is 10.

Please let me know if you have experienced the issue before and if so whether you have found any resolution steps.

Thank you in advance!

 My Request Count.jpeg

1 REPLY 1

kmohammed
Tera Guru

The key point is that the badge and the list are not necessarily the same query. A badge count in Now Mobile usually comes from the applet's count/badge configuration (a data item or function that counts a record set), while the list screen applies its own filter. When they disagree, one of them is usually counting a broader set - so compare them directly instead of treating either number as wrong on its own.

 

1. In Mobile App Builder / the applet configuration, find the My Requests applet and check what its badge/count is bound to: which table and what filter/condition it counts. Compare that condition, field by field, with the list screen's filter.

 

2. Common causes of a higher badge: the badge counts all requested items/tasks for the user (including closed, cancelled, or child tasks), while the list shows only open parent requests; or the badge counts approvals or tasks assigned to the user in addition to their own requests; or the badge condition omits a state filter that the list applies.

 

3. Run the badge's query as a list in the platform (same table, same conditions, same user) and see whether it returns 31. If it does, the badge is faithfully counting that broader set, and the fix is to align the badge condition with the list filter. If it returns 10, the badge value is stale or cached - then clear the app data / re-sync and re-test, and check whether the badge refreshes on a schedule rather than on open.

 

4. Test with one user and one known record set before changing the applet for everyone, and check whether the gap is consistent across users or specific to that user (which points to a user-scoped condition, such as requested_for versus assigned_to).

 

If the badge query and the list filter already match exactly and the count is still wrong after a re-sync, that is the point to raise it with Support with both queries documented, since it would then be a platform/mobile rendering issue rather than configuration.