Skip to main content

License Plate Creation Import

The License Plate Creation import flow lets you build license plates in Business Central from prepared data, rather than creating them one at a time on a mobile device.

Why use it​

Introducing license plates to a warehouse that already holds stock normally means removing the inventory and receiving it back in so it can be placed on a license plate. That is disruptive and time-consuming for a live warehouse.

This import flow removes that step. You can license plate existing inventory in bulk — creating the license plates, their content, and any parent hierarchy directly from imported data — so an existing warehouse can be set up for license plate handling without first removing and re-receiving stock. It is well suited to initial roll-outs, onboarding a new site, and bulk corrections such as seeding license plates from a legacy system or an external stock count.

How it works​

Adjustment rows are loaded into the License Plate Creation page, one row per license plate content line. Each row carries the item, location, bin, unit of measure, quantity, license plate number, and optional parent license plate and license plate type values.

Running the Post Entries action processes every row in the page. For each row the app:

  1. Validates the row — required fields, parent license plate rules, and that a parent license plate is not the same as its child.
  2. Skips already-posted rows. If a License Plate Entry already exists for the row's document and line number, the row is ignored. This makes posting safe to re-run and prevents duplicate entries.
  3. Creates or updates the license plate. If the license plate does not exist it is created; if it exists, its location and bin are updated to match the row.
  4. Builds the parent license plate hierarchy. When a parent license plate is supplied, the parent license plate and the content line linking child to parent are created or updated. Up to two hierarchy levels are supported.
  5. Applies the license plate type (when supplied) to the top-most license plate in the row.
  6. Upserts the license plate content. A new item content line is created, or the quantity of a matching existing line is increased or decreased.
  7. Writes a License Plate Entry recording the movement as a positive or negative adjustment, providing an audit trail of the imported quantity.

After all rows are processed successfully, the imported rows are removed from the License Plate Creation page.

Parent license plate hierarchy​

Two parent levels are supported through the Parent LP No. Level 1 and Parent LP No. Level 2 fields:

  • A row may have no parent, a single parent (Level 1), or two parent levels.
  • Parent LP No. Level 2 requires Parent LP No. Level 1 to also be set.
  • A parent license plate cannot be the same as the child license plate, and the two parent levels cannot be the same as each other.

When a hierarchy is supplied, the parent license plates are created if needed and content lines are written so the child license plate is nested under its parent.

Validation and quantity rules​

  • Document No., Item No., Location Code, Bin Code, Unit of Measure, License Plate No., and Quantity are required.
  • A negative quantity is allowed and is posted as a negative adjustment, but posting fails if it would drive the license plate content quantity below zero.
  • Posting can be re-run safely; rows whose document and line number already have a License Plate Entry are skipped.

Dual unit of measure​

When Connect Dual Unit of Measure - Tasklet is installed, the import flow is extended so the unit and unit-of-measure values from each imported row are carried through to the created license plate content and License Plate Entry records. This keeps dual UOM information consistent for license plates created from adjustment data, matching how dual UOM is handled elsewhere in the app.

See also​