Skip to main content
Solved

Expose Fields from IN Issues Screen (IN302000) to Scan and Issue Screen (IN302020) to both Web and Mobile End

  • December 2, 2024
  • 6 replies
  • 155 views

Forum|alt.badge.img+2

Hi I need to copy the values in issues screen (Project and Project Task) to the scan and issue issue screen because they are not exposed to this screen by default. 

These fields also need to be exposed via mobile app end as well, how can I modify the mobile app screen to include these additional fields?

Any help would be appreciated, thank you!

Best answer by noorula77

Hi ​@TharidhiP , ​@SamMemar ,

To implement this customization:

  1. Create a new customization project in Acumatica
  2. Add the DAC extension (IssueExt) to add the Project and Project Task fields
  3. Add the Graph extension (ScanIssueEntryExt) to handle copying the values
  4. Modify the mobile site map to expose the fields in the mobile app

For the mobile app customization:

  1. Go to Configuration → Mobile Application
  2. Open the Scan Issue screen configuration
  3. Add the custom fields (UsrProjectID and UsrProjectTaskID) to the form
  4. Publish the mobile site map changes
View original
Did this topic help you find an answer to your question?

6 replies

SamMemar
Freshman II
  • Freshman II
  • 8 replies
  • December 3, 2024

Hi, I need exactly the same with Scan and Issue as well as the Scan and Receipt screen. Thanks in advance for your help.


Forum|alt.badge.img+1
  • Jr Varsity I
  • 62 replies
  • Answer
  • December 3, 2024

Hi ​@TharidhiP , ​@SamMemar ,

To implement this customization:

  1. Create a new customization project in Acumatica
  2. Add the DAC extension (IssueExt) to add the Project and Project Task fields
  3. Add the Graph extension (ScanIssueEntryExt) to handle copying the values
  4. Modify the mobile site map to expose the fields in the mobile app

For the mobile app customization:

  1. Go to Configuration → Mobile Application
  2. Open the Scan Issue screen configuration
  3. Add the custom fields (UsrProjectID and UsrProjectTaskID) to the form
  4. Publish the mobile site map changes

Forum|alt.badge.img+2
  • Author
  • Pro I
  • 104 replies
  • December 3, 2024

Thank you ​@noorula77 for providing the steps to cater this requirement!


Forum|alt.badge.img+2
  • Author
  • Pro I
  • 104 replies
  • January 30, 2025

Hi all, I have managed to implement the exposure of fields as below and face one issue.

The reason code was already available as a field to expose on the web screen. The only issue is that the reason codes gets populated, but it adds the reason code automatically as a default code without showing the selector.

Moreover I have exposed this same field to the mobile screen and don’t see any selector values.

update screen IN302020 {
update container "Issue" {
    fieldsToShow = 6  
    add field "ProjectID" {
      listPriority = 50
      listDisplayFormat = CaptionValue
   selector {
        fieldsToShow = 2
        add field "ProjectID"
        add field "Description"
      }
      pickerType = Searchable
    }
    add field "TaskID" {
      listPriority = 40
      listDisplayFormat = CaptionValue
   selector {
        fieldsToShow = 2
        add field "TaskID"
        add field "Description"
      }
      pickerType = Searchable
    }
    update field "ReasonCode" {
      listPriority = 30
   listDisplayFormat = CaptionValue
      selector {
        fieldsToShow = 2
        add field "ReasonCodeID"
        add field "Description"
      }
      pickerType = Searchable
    }
  }
}

Please let me know what I might be missing, thank you!


Forum|alt.badge.img+1
  • Jr Varsity I
  • 62 replies
  • February 2, 2025

Hi ​@TharidhiP ,
 Try to update like mentioned below.

 

update field "ReasonCode" {
      listPriority = 30
   listDisplayFormat = CaptionValue
      selector {
        fieldsToShow = 2
        add field "ReasonCodeID"
        add field "Description"
      }
      pickerType = Searchable
 defaultValue = ""  // Add this to prevent auto-population
    required = false   // Make it optional to prevent auto-population
        }
    

Key changes made:

Added defaultValue = "" to prevent automatic population
Added required = false to ensure the field isn't forced to have a value
 


Forum|alt.badge.img+2
  • Author
  • Pro I
  • 104 replies
  • February 2, 2025

Hi ​@noorula77 thank you for the suggestion, so for the web screen in order to avoid default reason codes getting populated I need to set required to false as well?

Thanks!


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings