Iaroslav Pankovskyi

Dear Microsoft Team, As you, probably, know Canadian EFT (ACH) formats vary from bank to bank. You have already set the default CA EFT to RBC. Excellent. Our existing and particularly prospective clients that use other banks need a bit more flexibility to choose Business Central. For example, those that use Scotiabank (CPA005 EFT standard) need that OOB EFT functionality in Business Central must allow the following: 1) Date format: YYYDDD (current is YYYYDDD and substring Transformation Rule does not work as it should); 2) File Creation Number (FCN) must be available on Detail and Footer (it is already available on Header) 3) Originator's cross-reference number (19 characters) on Detail - Users must be able to map this field in Data Exchange Definition to "Document No." Field on the Payment Journal Because this can be of use to a lot of exiting and prospective Business Central users, my colleagues and I hope that the above suggestions can be considered by Microsoft Team soon. Thank you, Iaroslav (Consultant at BDO [Partner])

1) Allow determining / filtering what Users are pulled in from Office 365 when the "Get Users from Office 365" function on the "Users" Page in D365BC is run.
2) Allow deleting those Users in D365BC that have been pulled in incidentally (they do not have any ledger entries yet).
3) When the "Get Users from Office 365" function on the "Users" Page in D365BC is run, ONLY those User who have D365BC Essentials, Team Member or Premium license assigned to them must be pulled in.
Thank you!

Hello Support Team, Currently, Requisition Worksheet can be run to generate the demand from Jobs. For example, I need 2 Rims for Job A and currently have 0 Rims. I run Requisition Worksheet and it shows a suggestion to purchase 2 Rims. I select the "Carry Out Action Message" choice and it creates a PO. Great. The only problem is that my PO does not show the Job-related details. For example, it does not show Job #, Task or Job Planning Line. Solution: Make Job-related information (Job #, Task and Job Planning Line) to be preserved on the Requisition Worksheet and then make this be carried over to the PO created from this Requisition Worksheet Line.

Currently, it is possible to post a Sales Invoice from Job Planning Lines that are of Type "Budget and Billable" prior to consuming what is on that Line (e.g. an Item). The result of posting such a Sale Invoice is that none of the inventory controls are enforced (e.g. Negative Inventory, Serial Number, quantities in the given Location, etc.). This may result in a sale of the same Item more than once and, consequently, puts companies using Jobs in an awkward situation with their clients when they are unable to deliver an Item because it is not available, which, they thought, was available. SOLUTION: To address this, in the “Job Setup” add an option to prevent from creating and/or posting a Sales Invoice for Planning Lines of Type “Budget and Billable” IF the related consumption has not been posted yet.

Dear Microsoft team and D365BC community: Due to the technical constraints of the underlying Table, the "Notification Setup" Page currently requires to either press the "Tab" key (on the keyboard) or click on the "New" button in the Ribbon of the Page to create a new Line. Here is what should be done to improve user experience: 1) eliminate the access to the “Notification Setup” Page (Table) from the “Approval User Setup” (this is to simplify the underlying Table setup - possibly, by keeping only one Primary Key) - instead, preserve the access to the Page via the system Search Box + allow Users to set Filters on that Page, including by User ID (this is to preserve the full functionality); 2) rename all the Page from "Notification Setup" to “Alerts” (or similar) to avoid confusion with “My Notifications” (AKA “Notifications” when accessed from the “My Settings” [the gear button]). Thank you, Iaroslav

Dear Microsoft team, community, Non-profit and other companies selling memberships and similar items require a possibility of starting a deferral not immediately, but, for example, from a new renewal period which can be other than the Posting Date and other options in the "Start Date" Field of the "Deferral Template" Page. To address this requirement, it is necessary to add an additional Field on the "Deferral Template" Page, such Field as "Modifier", for instance. This Field should allow Users entering formulas like "1M" or "-1M" and will work based on the "Start Date" Field (depending on the option selected there). For example, if the "Start Date" = "Posting Date" and the "Modifier" = 1M, the system will take the date (e.g. on a Sales Invoice), let's say April 1, and will start deferring one month after that (April 1 + 1M = May 1). Thank you, Iaroslav