Comments
Another reason for changing the current state in BC is the situation with renaming a user specified in Job Queue Entry via Codeunit9800 User.RenameUser. Even though the original user ID (already renamed) remains the same in Job Queue Entry, after renaming, the task starts running under a different user—the one who performed the renaming. I have already added my voice to this, there are already many applicants, so please: Change your behavior in this area. Thank you.
I am reaching out to kindly request a reconsideration of the previously rejected feature proposal related to Microsoft Dynamics 365 Business Central.In our customer projects, we regularly face the need to procure external resources and allocate them accurately within the project cost and billing structure. This is a recurring requirement across multiple implementations. The absence of this capability in the standard solution forces us to rely on workarounds, customizations, or manual processes. These approaches introduce additional effort, increase the risk of inconsistencies, and reduce transparency for both partners and customers.Enabling this feature would significantly improve project accounting, enhance the usability of Business Central in service-oriented scenarios, and reduce the need for extensions that solve a common and recurring business need. From our perspective, this functionality is not a niche request but a core requirement in modern project-based businesses.We would highly appreciate it if you could re-evaluate this request and consider including the feature in an upcoming release of Business Central.Thank you very much for your time and for continuously improving the product. Please let me know if additional details or use cases would be helpful.