LeBarre Kyle Technical architect

Add a URL scheme (eg. "mswarehousemanagement://") to the iOS Warehouse Management app to be able to launch it from another app.

Due to iOS restrictions, we're unable to launch the mobile app through code without a URL scheme configured for the application.

There may be a requirement to launch the app via another custom application. For our case, we need to apply a custom barcode scanner configuration when the WMA app is launched. To facilitate this, we are designing a custom "launcher" app, which will set the scanner configuration and also launch WMA. Currently we don't have a great way to launch WMA from our custom launcher app without a URL scheme.

Currently there is a mobile device menu item to enable a worker to override the printer they are printing labels to from the WMA.

This functionality currently does not work if "Document routing" is used to configure the print locations.

If a printer name is defined in "Document routing", that is always the first place the cost looks at when deciding where to print a license plate label to.

The printer override will only work if the system is configured to use "Dynamic printer selection":https://learn.microsoft.com/en-us/dynamics365/supply-chain/warehousing/dynamic-printing-selection

However, license plate labels by location are not currently supported, so currently we can either have printing by location using document routing OR printer overrides using dynamic print selection.

We should be able to map multiple AI codes to the same internal field and assign a priority to determine which AI code's value is used, in the case they both exist in the GS1 barcode.

Currently, in the "Barcode data policy" setup form, only a single GS1 AI code can be mapped to an internal field.

Vendors may use different AI fields to transmit their data. In the example of bulk receiving, vendors will typically only transmit the weight. There are many AI codes that could be transmitted that need to be mapped to the same internal "Quantity" field.

eg. (30), (310n), (315n), (320n), (357n), (360n), (361n)

There is no way to accommodate for this in the current GS1 mapping setup, other than creating a barcode data policy and a separate menu item for each unique combination. The user would need to determine which menu item to use depending on which AI codes were sent in the barcode and open the specific menu item that will allow the GS1 to be successfully scanned and mapped, which is far from an ideal workaround.

When modifying an existing line on a mixed license plate, using the "Mixed license plate receiving" work creation process, the unit of measure should be selectable in the "Select new quantity" step.

When entering a new mixed LP line, workers do not typically use the inventory UOM. When the try to modify the line's quantity, it is always in the invent UOM and does not represent what they initially entered. Allowing the unit to be selectable, and preferably, stored on the WHSMixedLicensePlateReceiptLine record defaulted to the UOM it was initially input as, would be ideal to eliminate confusion and manual conversions.

We're unable to convert from OZ to LB when converting through two base units when the standard conversion is set up as LB to OZ.

The converter should be able to use the LB to OZ setup to infer the OZ to LB conversion.

This is due to a bug @ UnitOfMeasureConverter_Product.findConversionThroughTwoBaseUnits() Line 319 (10.0.42)

https://www.yammer.com/dynamicsaxfeedbackprograms/#/Threads/show?threadId=3194517380096000