Back

Defining User Setup and journals for the Warehouse

Configuration of Warehouse Mobile
Video 3/9
Play
Close
  • Helpful
  • Not helpful
  • Needs update
  • Technical error
A "configuration"-video is about how you configure your solution and get it ready for use. Typically, these videos are quite advanced. Configurations This video includes functionality from the app "Warehouse Mobile" which is available at Microsoft AppSource. Click to visit AppSource. Warehouse Mobile

Playlists  Manage

Log in to create a playlist or see your existing playlists.

Presenter: Sune Lohse, Chief Strategy Officer

When you work with warehouse mobile flows in Business Central, you control posting behaviour per resource, not per Windows user. This means you can decide for each individual worker whether actions like picks, movements, and reclassifications post automatically or stay in a journal for review.

You find these settings in the mobile flow user setup, where you navigate to the mobile flow resources and open the mobile flow resource setup card for each resource.

The setup comes with a default configuration that pulls journals from the standard setup in Business Central, so you don’t have to build everything from scratch.

A common use case is to enable automatic posting for experienced users while disabling it for new users, so someone can check their work before it posts.

How posting works in warehouse mobile flows

When you work with the warehouse mobile, there are many flows you can execute, and several of them include postings. The behaviour differs depending on the flow.

For counting, you normally wouldn’t post directly. You leave the result in the journal. For a warehouse receipt, on the other hand, you typically want to register it, which is also a posting.

All of this is configured on the resource, not on the Windows user. That distinction matters because it lets you tailor the experience to each individual worker on the floor.

Where to find the mobile flow resource setup

You start from the default setup created in the mobile flow user setup. From there, you navigate into the mobile flow resources.

If you remove the filter, you can see all the resources and all the users you have. For each resource, you can edit it and open the mobile flow resource setup card.

The card arrives with a default setup. Among other things, you set up permissions here, and you set up all the journals. These journals are created from, or pulled from, the standard setup in Business Central.

Configuring posting per resource for warehouse activities

In the warehouse section of the setup, you can control posting for the different warehouse activities. For example, you decide whether to post the warehouse journal lines when doing picks and movements that create journal lines. You also decide whether to post reclassifications and which journal should be used for each activity.

Because all of this setup is per user, you have flexibility. For some users you can enable all the automatic posting. For other users, such as new staff, you can remove the automatic posting so that someone can check the work before it goes through.

Q&A

Is warehouse mobile posting configured per Windows user or per resource?

It is configured per resource, not per Windows user. This lets you set different posting rules for each individual worker.

Where do I configure posting behaviour for warehouse mobile flows?

You start in the mobile flow user setup, navigate to the mobile flow resources, then open the mobile flow resource setup card for the relevant resource.

Does counting post automatically in the warehouse mobile?

Normally no. Counting is left in the journal rather than posted. A warehouse receipt, by contrast, is typically registered, which is a posting.

Where do the journals in the resource setup come from?

The default journals are pulled from the standard setup in Business Central, so you don’t have to create them all manually.

How do I prevent new users from posting automatically?

Open the resource setup card for that user and remove the automatic posting. This keeps their actions in the journal so someone can check them before posting.

672269009-QA9im02C0mI-ENG21111069