Setting Account Name in Project Drop-ship purchase order to default to branch name

I'm not sure what customization you're referencing, but yes, this is not difficult for a developer. Ask your VAR or find a freelancer.

AI was used to create this answer

darylbowman !

Yes, customizing the Account Name on a Purchase Order (PO) in Acumatica ERP is absolutely possible. Similar to how a shipping address might be customized, modifying or adding a field like Account Name requires working within the customization framework Acumatica provides. Here's a high-level overview of how this could be achieved:

1. Customization Project

• Start a Customization Project:
  • Navigate to System Management > Customization > Customization Projects.
  • Create a new project or edit an existing one.

2. Modify the Purchase Order Screen

• Access the Purchase Order Screen:
  • Identify the screen you want to modify, e.g., PO.30.10.00.
• Add/Modify the Account Name Field:
  • If Account Name is not already a field, you can add it by extending the DAC (Data Access Class) for the Purchase Order (e.g., POOrder).
  • Use the Customization Editor to add a new unbound field or bind it to an existing data source in the database.

3. Customize the DAC

• Extend the POOrder DAC to include the new field for Account Name:

  csharp Copy code

  [PXDBString(100)] [PXUIField(DisplayName = "Account Name")] public virtual string AccountName { get; set; } public abstract class accountName : PX.Data.BQL.BqlString.Field<accountName> { }

4. Update Business Logic (if required)

• If the Account Name should pull data dynamically (e.g., from a related table like Customer or Vendor), customize the graph to populate it during the PO creation or editing process.

5. Update the UI

• Add the Field to the Screen:
  • Use the screen editor in the customization project to add the AccountName field to the desired location on the Purchase Order form.
  • Map the field to the AccountName property added in the DAC.

6. Publish and Test

• Save the customization and publish it to your Acumatica instance.
• Test the changes to ensure that the field behaves as expected, populates data correctly, and integrates with the system.

Notes:

• If the Account Name already exists as part of the vendor or customer data, consider linking the field directly rather than duplicating the data.
• Ensure any customizations meet your organization's specific requirements for workflows and reporting.
• In case of future upgrades, always test your customizations in a staging environment to ensure compatibility.

This process is straightforward for a developer familiar with Acumatica's framework.