Mobile App Builder Table Reference Cannot Retrieve Custom Table

[SIVASURYANP]

Hi Community,

I am experiencing an issue with Mobile App Builder. I created an applet with an Edit function, but I am unable to retrieve a custom table in the Table Reference field.

Based on my research, it appears that the Table Reference field limited to retrieving the first 10,000 records from the 'sys_db_object' table. I updated the (glide.cmdb.data_manager.db.max_view_records) system property mentioned in the ServiceNow documentation, but the issue persists, and the custom table still does not appear in the available results, Instead the search results display other relevant tables.

#mobileapp

#mobileappbuilder

[boteeuwen]

The cause is the default limit of 10,001 records for Glide queries based on a Database View. This is controlled by the glide.db.max_view_records system property.

If the property does not exist, ServiceNow uses the default value of 10,001. You can create the property as an integer and set it to a higher value, for example 75000, depending on what you need. Just keep in mind that setting it too high can have a performance impact. 🙂

[gourav786gs]

If working on small enhancement or development. You can also try configuring record in platform rather than mobile app builder[Open In Platform], there you would be able to set table without setting the "glide.db.max_view_records" property. 

[musislam]

Hi,

Before chasing the record limit - a stock PDI has ~6,700 rows in sys_db_object, so you'd need a very heavily customised instance to genuinely pass 10k. Worth counting yours first. Also, glide.db.max_view_records is documented for database views, and sys_db_object isn't one, which fits what you saw when the property did nothing.

I'd check the table's Application Access tab first (sys_db_object): Accessible from = All application scopes, Can read ticked, and Allow configuration (configuration_access) ticked. That last one defaults to false, and it's what hides a table from design-time pickers when your mobile config sits in a different scope from the table. Clear cache and retry after changing it.

If that sorts it, could you mark it as the recommended solution? Helps me support these better for the community.