Elise De Brie

When migrating to a new environment we face the issue that there is no data entity for query's. This means that when we migrate warehouse management and have a ton of location directives and other things we always need to manually configure the query's. This takes a lot of time and has to be done for each environment and for each location directive action. If you could make these query's into a data entity we could upload them from one environment to another without the manual work (besides the creation of the originals).

In today's fast-paced business environment, time and efficiency are crucial to success. With the increasing use of mobile devices, it's important that software tools are able to keep up with the pace. That's why i am excited to announce my new idea for D365FO that will make process documentation a breeze - the Task Recorder for Mobile Devices.

The Task Recorder, which is already available for the client, should be extended to the mobile app, allowing users to record their processes executed on the device and create automated manuals. This eliminates the need for manual documentation with print screens and text, saving time and effort and ensuring accuracy and consistency in recording processes.

Not only will this feature improve documentation, but it will also make the process of training and on-boarding new users smoother and more efficient. With the Task Recorder for Mobile Devices, users can create step-by-step tutorials for their colleagues, streamlining the training process and increasing productivity.

Kind regards,

Elise

Currently, the Inventory Status Change and Warehouse Status Change menus in D365FO allow users to change the status of inventory items, but there is no option to select a specific quantity to change the status from. This makes it difficult for users who do not have a mobile device to perform this action. To solve this problem, I propose adding a filter to these menus that would enable users to select the specific quantity they want to change the inventory status for.

The new filter would allow users to input the quantity they want to change the inventory status for, and the system would update the status only for that particular quantity. This would make it easier for users to manage their inventory and reduce the risk of errors when updating inventory statuses.

I believe that adding this feature would improve the usability and efficiency of the Inventory Status Change and Warehouse Status Change menus in D365FO, and I recommend that this enhancement be considered for implementation in a future update.

Microsoft workspaces currently lack the option to assign colors to tiles, limiting visual organization and quick identification of specific tiles or groups.

I propose the idea of adding color-coded tiles to Microsoft workspaces. Currently, the lack of this feature hampers visual organization and quick tile identification. By introducing color-coded tiles, users can enjoy benefits such as enhanced organization, faster tile search, personalized customization, streamlined collaboration, and improved accessibility for visually impaired users.

Currently, users can add custom columns to tables in D365FO. However, these columns lack the ability to be calculated or conditional fields. This limitation creates a need for extensive development when users want to perform simple comparisons between columns.

To address this issue and streamline functional programming, I propose extending the functionality of custom columns in D365FO. By enabling calculated fields or conditional fields, users would gain the ability to perform basic comparisons and derive values without relying on complex development processes.

Implementing this enhancement would significantly improve productivity, reduce development time, and empower users to manipulate data more efficiently. Let's enhance the D365FO experience by introducing this valuable addition to custom column functionality.

#D365FOEnhancement #ExtendedCustomColumns #SimplifiedProgramming

When creating workspaces for different departments, I frequently encounter a blocking error that prevents me from copying the workspace to a specific user. The error message states that a view with the specified name already exists. This restriction on reusing views hinders collaboration and customization.

In many businesses, multiple departments need access to the same information for different purposes. For example, logistics and purchasing teams may need to track the status of goods and ensure smooth invoicing. Creating separate workspaces helps each department focus on their tasks.

To address this issue, I suggest changing the blocking error to a warning. Instead of completely halting workspace creation, users would be notified of the existing view. This approach maintains flexibility while raising awareness of potential conflicts.

By implementing this change, we can enhance collaboration, streamline workspace creation, and accommodate the diverse needs of departments.

Thank you for considering this idea to improve the workspace creation process in Microsoft's platform.

Problem Statement:

Multinational companies face challenges when their Dynamics 365 for Finance and Operations (D365FO) mobile menu items are set up in a language different from that spoken by warehouse workers. This can cause inefficiencies and errors in operations due to language barriers.

Proposed Solution:

Introduce a feature that allows manual translation of mobile device menu items, similar to the existing functionality for item descriptions in D365FO. In addition, enable warehouse workers to set their own display language on the mobile device via user settings.

Key Features:

1. Manual Translation for Menu Items: Administrators can manually add translations for each menu item, similar to how item descriptions can currently be translated in D365FO.

2. User-Defined Language Settings: Warehouse workers can select their preferred language from the available options in the user settings on the mobile device, just like in the D365FO main platform.

Benefits:

1. Consistency Across Platform: Utilizing a translation mechanism similar to what is already in place for item descriptions ensures a uniform experience across D365FO.

2. User-Centric Approach: Allowing individual users to set their preferred language increases usability and reduces errors.

3. Operational Efficiency: Manual translation ensures that key terms and menu items are translated in a way that is most appropriate for the specific business context.

Technical Requirements:

• Modification to the administrative interface to support manual input of translated menu item text.

• Update the mobile interface to incorporate user-defined language settings that can be configured individually.

This enhancement aligns with the existing functionalities in D365FO, thus offering a seamless and more efficient experience for users across different roles and geographic locations.

Hello D365FO Community and ER Experts,

I hope everyone is doing well. I'd like to propose a feature enhancement for D365FO. While the platform currently allows for comparing a completed version of an ER configuration with a draft version, there's no in-built feature to compare two completed versions of any ER configuration. This functionality is vital for various reasons like accountability, historical tracking, and ensuring smooth transitions between team members.

I suggest the introduction of a feature that enables the direct comparison between two completed versions of any ER configuration. Adding this feature would fill a noticeable gap in the existing system and make it much more user-friendly for managing and understanding changes in configurations.

Best regards,

Elise

👋 Hello Dynamics 365 Team and Community,

I'd like to propose an enhancement to the way unit conversions and unit sequence groups are managed in Dynamics 365 Finance and Operations (D365FO). The current design is quite strict, allowing unit conversions only at the level of released products, without any vendor-specific flexibility. This creates challenges for companies sourcing the same item from different vendors, each of whom might package the item differently.

Current Challenge:

1. Unit Conversions: Suppose we have a single item, Item A, that we purchase from two different vendors:

• Vendor 1: Packages Item A in boxes of 50
• Vendor 2: Packages Item A in boxes of 100

1. As of now, the system only allows us to create a standard intra-class conversion like Box > Each. However, this does not address vendor-specific variations in packaging.
2. Unit Sequence Groups: Furthermore, the system only allows us to assign one unit sequence group to an item. This makes it nearly impossible to set up different unit conversions like "PL" > "Box" > "Each" and "PL Supplier Y" > "Box Supplier Y" > "Each Supplier Y" for the same item.

Proposed Solution:

I suggest the following enhancements to D365FO:

1. Vendor-Specific Table: Introduce a new table with table/group/all mechanism that allows users to define unit conversions specifically for each vendor.
2. Auto-Populate in PO: When a Purchase Order is created, the system would automatically populate the unit of measure based on the vendor chosen, leveraging the vendor-specific unit conversion.
3. Fallback Mechanism: In the absence of a vendor-specific unit conversion, the system would revert to a 'general' or 'default' unit conversion.
4. Multiple Unit Sequence Groups: Redesign the system to allow assigning multiple unit sequence groups to a single item. This would offer more flexibility in defining units for items purchased from different vendors.

By implementing these features, D365FO would significantly enhance its flexibility and usability, making it easier for companies to manage complex vendor relationships and sourcing strategies.

Thank you for considering this idea, and I look forward to hearing your thoughts!

Best regards,

Elise De Brie

The current acceptance tests for location directives allow testing against specific items and/or order numbers to verify expected results. However, this functionality lacks the capability to test scenarios where mixed items are received on a single pallet. This is a significant gap, as mixed-item receiving is a common practice in warehouses, especially when dealing with processes like ASN (Advanced Shipping Notice), Mixed License Plate Receiving, and Cluster Receiving.

Suggested Feature:

Extend the current acceptance tests for location directives to include test scenarios that allow multiple mixed items on a single pallet to be tested against their expected putaway locations.

Benefits:

• Enhances the accuracy of acceptance tests, covering a broader range of real-world scenarios.
• Allows warehouse operations to validate location directives for mixed items, ensuring efficient and logical inventory management.
• Provides additional layers of testing to ensure that the location directives work as intended for various types of work orders, thus reducing errors and improving workflow.

By implementing this feature, the system would significantly improve its ability to simulate and validate a wide variety of real-world receiving scenarios, thus contributing to a more robust and reliable warehouse management system.

Best regards,

Elise De Brie