Khaled El-Zorkany

It would be a wonderful option, in Price Model Criteria in Product Configuration Model to allow the user to generate a Unit Price, upon generating the P.O into a S.O in an Intercompany Scenario.

Additionally, this would make it possible to use the attribute-based price model on a supplier order and automatically calculate the purchase price according to the configuration.

The current session logoff functionality introduced via the Work User Access Policy in D365 SCM does not fully support the "User and password" authentication method on mobile devices. This creates a security loophole and usability challenge, especially for industries like Pharma where strict access control is mandated by regulations such as 21 CFR Part 11.

There are two authentication methods for mobile devices:

1. Device Code Authentication – One-time login with a device account, followed by warehouse worker login.
2. User and Password Authentication – Requires login with a Dynamics user account, followed by a second login with a warehouse worker account (often automated via Default User).

The session logoff currently only affects the second login (warehouse worker), not the primary user login. This leads to:

• Security Risk: After session timeout, users can cancel the warehouse login and reconnect, automatically regaining access via the still-active primary login.
• Compliance Gap: This violates regulatory requirements for access control and auditability for companies like Pharma Companies
• Usability Issue: Users are forced to re-enter warehouse credentials they may not know, while the actual user session remains active.

Proposal:

• Extend session logoff to also terminate the main user session when using User & Password authentication.
• Ensure that after timeout, users must re-authenticate with their Dynamics credentials.
• Prevent automatic re-login if the session has expired.

This change would close a security loophole, support compliance, and make the preferred authentication method more practical for real-world use.

Please parameterize an option to have these fields editable on the FnO (Application-Side) instead of pushing changes via SQL Scripts

Fields: SplitSitePickingList & SplitSitePackingSlip

Table: SalesParameters

SAP: Accounts receivable > Setup> Accounts Receivable Parameters > Summary Update > Split based on

User Story:

As a warehouse worker, when I perform Inventory status change from Item inquiry, I must choose a valid “To inventory status” before submitting so that I never see a first‑attempt error and I always confirm the correct status.

Problem / Business Need:

Warehouse workers use Item inquiry → Inventory status change in the Warehouse Management mobile app (WMA). To force workers to consciously choose the correct target status every time, customers configure the menu item’s default “To inventory status” to an empty value (“”).

• With this setup, the first attempt to change status errors (“status \"\" does not exist”), the second attempt succeeds, the third fails again, and so on—alternating behavior that wastes time and confuses users.
• Not defining any default “To inventory status” is not acceptable, because the app then auto-fills a real status and the worker might proceed without verifying it—making the process error‑prone.

Proposed Solution:

Add a “Require explicit selection” mode for the target inventory status in the Inventory status change flow. When enabled:

1. The To inventory status field renders with a placeholder (no default value submitted).
2. Submit is disabled until the user picks a valid status (via list or scan).
3. The app does not reuse the previous (invalid) cached value when the user returns to the step (fixing the alternating success/failure pattern often seen in detour navigation).

.

Technical Description

System grouping does not group works properly if the user logs out of the mobile device after performing the Pick operations.

Root Cause

The context for system grouping only works when the end-to-end scenario (Pick and Put) is executed in one go. If the user logs out after completing the Pick step, the system loses the grouping context. As a result, it processes each work individually instead of as a group.

Resolution

Ensure that the full workflow (Pick and Put) is completed without logging out. Logging out breaks the grouping logic because the system cannot identify which works were previously grouped.

Reference

https://fix.lcs.dynamics.com/Issue/Details?bugId=1072268&dbType=3&qc=6d655d5353feccb1a85c8c4539430ca01d8f2c822d6d2ced329c6120f6c8015a