Auto Populate PO Line Attributes

Overview

The Purchase Order (PO) Attribute Propagation automation available in the ION marketplace streamlines the management of attributes between the PO level and the PO line level. This automation significantly enhances procurement efficiency by reducing repetitive data entry, maintaining attribute consistency, and allowing flexibility where needed.

Key Capabilities

  • Automated Propagation: Automatically copies values from PO header attributes to PO line attributes who's keys are an exact match.

  • Line-Level Customization: Allows users to override propagated values on individual PO lines.

  • Accommodate to New PO Line Items: Applies updates dynamically when new PO line items are created so they reflect the setup of header attributes.

How It Works

Triggers & Conditions

The automation activates under the following conditions:

  1. On PO Line Item Creation:

    • Copies Need Date and ETA from a specified PO header attribute to new PO line native fields "Need Date" and "Parts ETA Date ".

    • Copies custom attributes if matching keys exist between the PO header and PO line.

  2. On PO Attribute Updates (Need Date, ETA, or Custom Attributes):

    • Updates all PO line items with the new values.

    • If the updated PO attribute does not exist at the PO line level, the automation does not execute.

The attributes being referenced for this automation can be found on ION's Organization Settings page under the Purchase Orders tab. Scroll within this tab to view both Purchase Order and Purchase Order Line attributes.

Flow

Setup

In order to setup this automation refer to the Deploying Automations and Integrations documentation for generic instructions.

This automation allows you to map date-time attributes at the PO level to the native PO Line fields "Need Date" and "Parts ETA Date." During configuration, you can specify which PO attribute keys to map.

If you do not want to automate the population of "Need Date" and "Parts ETA Date" on the PO line, retain the default options during configuration and select "Finish."

Error Handling

  • If an attribute exists at the PO header but not at the PO line level, the automation does not attempt a copy-down. As such your attributes within IONs organizational settings must be an exact match for the copy to work.

Best Practices for Using This Feature

  • Be aware that any updates to attributes at the PO header level will be applied to all PO line items. Ensure team members understand the automated propagation mechanics to avoid unintended data changes.

Last updated

Was this helpful?