Share via

Requested Record doesn't exist in offline DB error in Mobile

Nagaraja Babu Shetty 0 Reputation points
2026-04-09T06:33:17.99+00:00

When open any bookings in the mobile, getting the error "Request Record doesn't exist in DB"image (8)

Microsoft 365 and Office | Other
0 comments No comments

2 answers

Sort by: Most helpful
  1. Jess-Q 9,585 Reputation points Microsoft External Staff Moderator
    2026-04-09T07:38:20.3066667+00:00

    Hi @Nagaraja Babu Shetty

    Based on the screenshot, this error appears to be related to Dynamics 365. For this reason, I recommend reposting your question in the Dynamics community forum, where others with more experience in that area might be able to help and you may get more accurate guidance. 

    User's image

    Once again, I apologize for redirecting you to a different community as the members of the posted category focus on users with Microsoft 365 concern and have limited knowledge about Dynamic, so to get a quick and better assistance, we redirect you in the correct way.     

    Thank you for your patience and understanding, if you have any other questions or need further assistance, feel free to ask.   


    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

    0 comments No comments

  2. Q&A Assist
    2026-04-09T06:33:42.9566667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The message "Requested record does not exist in offline DB" occurs when the record being opened is not present in the mobile app’s offline database. In Field Service / model‑driven mobile apps this is typically caused by the mobile offline profile filters removing the record from the device.

    To resolve:

    1. Verify the record is included in the offline profile
      • In the admin environment, review the mobile offline profile used by the Field Service mobile app.
      • Confirm that:
        • The Bookable Resource Booking table is included.
        • The filters on this table allow the specific booking (for example, date range, status, ownership) to be downloaded.
      • If the filters are too restrictive (for example, only future bookings, or only certain statuses), adjust them so that the bookings technicians must access are included.
    2. Re‑sync the mobile app
      • On the device, trigger a full offline sync.
      • After sync completes, open the booking again.
    3. Check for records removed after sync
      • After each sync, data that no longer matches the offline profile filters is removed from the device. For example:
        • Past or completed bookings may be removed if the profile only includes current/future or non‑completed bookings.
      • If technicians frequently see this error when revisiting older or completed bookings, relax the filters (for example, include a longer date range or include completed bookings) so those records remain available offline.
    4. Consider app reset if configuration changed
      • If the offline profile was recently updated, reset the mobile app or sign out and back in so the device downloads a fresh offline database with the new filter settings.

    If the error persists after confirming the offline profile and performing a full sync, review the offline sync status and logs in the app to see if there are sync warnings or errors that prevented the booking records from being downloaded.


    References:

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.