Nicolas Saleron Cap Vision

In the French localization, the Tax Audit export (Report 10885) currently allows to export the opening balance per G/L Account. In the last year, 30% of our customers who have been controlled by the Administration get the file rejected. The reason is that the controller requires accounts 512 (banks), 401 (vendors) and 411 (customers) to be detailed by tier account in the opening balance. It would be nice to implement this enhancement in standard to fit the real requirements of the French Administration.

In the codeunit 8612 - Config. Template Management, the procedures ApplyTemplateLinesWithoutValidation and GetNextLineNo contains the following line: ConfigTemplateLine.SETFILTER("Data Template Code",ConfigTemplateHeader.Code); It should be a SETRANGE and not a SETFILTER: if the template code contains a joker (*, ?, &, |, ...), the filtering behaves improperly. The following problem causes error in Data Migration when upgrading from Item Categories to templates.

Hello, The field Job Task No. does not exists in Sales Line Archive and Purch. Line Archive tables. When a Sales Quote/Order or Purchase Quote/Order is archived, the information is lost. It is not the case with the Job No. which exists in both tables. Could the field be added?

Hello, When you typed an Item No. in a Transfer Order, the application validated the Description. It means if you have another item that contains the description of the item you just typed, the application propose a substitution. I think the validation on the Description should be deleted when an Item No. is typed.

Hello, On a General Journal Batch, you can check the field Suggest Balancing Amount. When this feature is enabled, the Document No. is no more auto-incremented when the balance reaches zero. You can reproduce this behaviour by following theses steps: 1. Go to a General Journal 2. Open the General Journal Batch and check Suggest Balancing Amount 3. Type a first line with an Amount = 1,000 4. Type a second line, it will be filled with Amount = -1,000 automatically 5. Start a third line, the Document No. is still the same as before. I think the expected behaviour would be to increment the Document No.

Hello, When using the Bank Reconciliation process, you usually use the function Transfer to General Journal to post missing transaction. The General Journal Batch is usually setup with a balancing account sets to the bank account. It allows the user to just type the Account Type and Account No. in the General Journal and Post. Unfortunately, when changing the Account Type or Account No., the description that comes from the Bank Statement is cleared. It breaks the user experience by forcing the user to copy the description first, set the Account Type/Account No. and paste the Description again. In some circumstances, if the description is not kept, the automatic reconciliation fails to match the entries that was posted from the bank statements.

Hello, You have introduced the ability to search inside Business Central documentation with "Tell Me" (https://docs.microsoft.com/en-us/dynamics365/business-central/ui-search). It would be a nice improvement for ISVs to enable search in the contant of their own documentation.

Hello, This request especially targets sales and purchase documents where coexist factboxes related to the header and lines. When a user has the focus on the lines, the factboxes related to lines often requires to scroll down. When you are switching between headers and lines, it might requires to scroll every time to see the related informations. Some suggestions: * In Focus mode, factboxes related to the header could be moved below those related to the focused page * When focusing a subpage, the first factbox related to it could be bring at the same level as the subpage

Hello, Microsoft has created the new ALAppExtensions with a bunch of functions we constantly use. We often create, in our apps, codeunits with helper functions. When we use these functions, we have to declare somewhere a codeunit variable everywhere and I am proposing here to be able to declare "static" codeunits. It would be just a compiler trick but the idea would be that: - Like dotnet.al, we create a file "staticcodeunits.al" where MyHelperCodeunit is given an alias like MyHelper. - Anywhere in my app, instead of writing : var MyHelper: codeunit MyHelperCodeunit; begin MyHelper.DoSomething(); end; It could be written: begin MyHelper.DoSomething(); end; In our apps, we would be able to use functions like Math.Min, Math.Max, StreamHelper.ToBase64() exactly like Dialog.Message or Text.StrSubstNo.

Hello, This is an ergonomy request: Today, we can navigate from sales shipment lines to the invoices of one line. I would like to see the following changes: - if the shipment line is linked to only one invoice: open the invoice directly, not the list - from the shipment header, allow the user to navigate to the list of all invoice related to the shipment. If the shipment is linked to only one sales invoice (which is the case most of the time): open the invoice directly. This improvement in navigation could be added everywhere: between sales return and sales credit memo, purchase receipt and purchase invoice, ...