Skip to main content
Question

Object reference error in 25R1 when exposing custom GI to Acumatica Mobile App

  • October 16, 2025
  • 4 replies
  • 65 views

Hi everyone,

I’m experiencing an issue while exposing a custom Generic Inquiry (GI) to the Acumatica mobile app.

Here’s what I’ve done:

  • I created a new GI based on the AMOrderType DAC and added two fields, including the key field Order Type and same Navigation.

  • There is also a system GI (AM-OrderType) based on the same DAC, which includes all fields in its results grid.

  • Both GIs work perfectly in the web UI.

  • I tried both enabling and disabling the  “Expose to Mobile Application” for both GIs and added them as new screens in a custom mobile project, mapping two fields for each (using WSDL → Result Container → Field Names).

  • I also updated the Site Map with their respective screen IDs.

After publishing, both screens appear under the “Other” tab in the Acumatica mobile app.
However:

  • The system GI displays data correctly.

  • The custom GI shows the error:

    “Object reference not set to an instance of an object.”

Additional details:

  • Both custom and system GIs work fine when exposed in a 24R2 instance.

  • I’ve tested on both iOS and Android versions of the Acumatica mobile app, and the issue occurs on both in 25R1.

  • Tried with SQL view too but same error.   

I’m trying to understand why this is happening in 25R1.Any idea about this?

4 replies

Hi ​@lmadushanke , did you ever get this sorted? I am experiencing the same issue on my side.


  • Author
  • Freshman I
  • January 6, 2026

Hi ​@lmadushanke , did you ever get this sorted? I am experiencing the same issue on my side.

Hi ​@fredodendaal94, not really however the issue only occurs in the Sandbox environment; in Live it works as expected. 


dcomerford
Captain II
Forum|alt.badge.img+16
  • Captain II
  • January 6, 2026

@lmadushanke has your GI got a Parameter on it ?


@dcomerford mine has parameters in. It works on the main tenant on the mobile app but the moment you run the same report on a different tenant on the app then it gives the error message.