Skip to main content
Question

Adding custom fields to the mobile app in Acumatica 2025R2

  • May 15, 2026
  • 2 replies
  • 18 views

I’m trying to add a custom field in the mobile app to the Appointment Details screen, and I have not been having any success. I am able to add and remove existing fields, but the custom field will not appear. It is in the Web Service → Service description and its value is displaying in the field on the FS300200 web page.

This is how I have been attempting to add it. I’ve been using the remove command to verify the mobile app is reading my latest update, so I’ve tried it without that as well.


update screen FS300200 {
  update container "AppointmentRecords" {
      remove field "Other#Description"
      add field "ServiceOrderHeader#CustomerJobName" {
        displayName = "Job Name"
        placeAfter field "Description"
      }
  }
}

 

This is the field in the FSServiceOrder DAC extension: 
public sealed class FSServiceOrderExt : PXCacheExtension<PX.Objects.FS.FSServiceOrder>
{
        #region CustomerJobName
        [PXDBString(100, IsUnicode = true)]
        [PXUIField(DisplayName = "Customer Job Name", Visible = true)]
        public string UsrCustomerJobName { get; set; }
        public abstract class usrCustomerJobName : BqlString.Field<usrCustomerJobName> { }
        #endregion

}

 

If anyone has any other suggestions for me, I would appreciate it.

2 replies

arpine08
Jr Varsity I
Forum|alt.badge.img+1
  • Jr Varsity I
  • July 2, 2026

Hi ​@rweiler93 ,

I tested your mobile code in my local environment using 2025 R2 (25.201.0213) with the Sales Demo data, and it works correctly.

I tested both variations:

Without remove field "Other#Description"

 

 

With remove field "Other#Description"

 

In both cases, the custom Job Name field appears immediately after Description.


valentynbeznosiuk
Jr Varsity I
Forum|alt.badge.img+4

Hi @rweiler93,

Some time ago we noticed, and later got confirmation from Acumatica support, that there's a bug in 25R1 and 25R2 related to MSDL code (mobile mapping customization) when a Translation Dictionary is used. In simple terms, instead of using the field name, you need to use the translated (English) name of the field.

For example, instead of using ProjectTask, you'd need to use the field SomeName.

 

If that's not exactly what's causing your problem, since there's already a known bug, there may be other unexpected behavior related to it, and it might be worth contacting Acumatica support.