-
Automatic Seats Count for Billing (CSP)
Using BC Online version, it is possible to update the number of named users using the solution monthly. But this update (create, deleting), does not update automatically the Seats Count to be considered for CSP billing purposes! It means that each partner has to have a resource to verify monthly each tenant and update the CSP Portal with the correct seats number to guarantee that the next month bill is correct. My suggestion is to automate this. -
Integration between D365BC and CDS should support more tables
The new functionality to integrate D365BC and CDS (under Preview) only allow to integrate four tables (Contacts, Currencies, Customers and Vendors). I suggest to add more tables to be possible to integrate between D365BC and CDS namely some transactions documents (like Sales Orders, Purchase Orders, ...). -
Date Compress Batch jobs
Following "Extend Data storage" for BC published in https://cloudblogs.microsoft.com/dynamics365/it/2020/04/28/extend-data-storage-for-dynamics-365-business-central/, i would suggest to bring again to Dynamics 365 BC the Data Compress batch jobs. In previous Dynamics NAV versions (old ones I must admit), there was some Batch jobs to compress tables like General Ledger Entries for closed periods (Report 98 Date Compress General Ledger and Codeunit 356 DateComprMgt). I would suggest to recreate similar batch jobs and besides the compress, it should allow to copy all the detailed transactions to Azure Data Lake storage. This way, Dynamics 365 BC will have less transactions and need less storage but for a BI perspective, all the data will be available to be analysed. Thanks, -
New VAT Scheme - OOS (One Stop Shop)
There is a new VAT scheme called OOS (One Stop Shop) available for companies with business in EU. Some detailed information here https://ec.europa.eu/taxation_customs/sites/default/files/oss_guidelines_en.pdf. This requirement will be common to a lot of companies and as far as we know there is no plan to have new functionality to match with this new requirement. Besides the configuration in BC to support OOS, there will be a new VAT Return form to upload the VAT information using a file. Some known details here https://ec.europa.eu/taxation_customs/sites/default/files/oss_guidelines_en.pdf. under Annex 3 - The One Stop Shop return details (Page 55 to 58). -
Workflow - New Response required for Purchase Document Approval "Post Preview the sales or purchase document."
Looking for the available Workflow Responses, we can see a list of 11 responses available. I propose to add a new one "Post Preview the sales or purchase document" similar to "Post the sales or purchase document." in order to submit the Preview Posting. If we have this new Response available, it will possible to setup a Post Preview action under a Purchase Invoice Workflow. This way, the User to request an approval is able to see the possible Post Errors before submitting for approval. Without having this option, the initial user can submit the Purchase Invoice for approval (without checking potential post errors) and when the Approval User approves it, the pop-up errors will appear and block the Post. -
Batch Post for Transfer Orders
Standard BC has the option to batch Post Sales Orders, Purchase Orders, Sales Invoices, Purchase Invoices and others. But this option to batch post does not exist for Transfer Orders. We are facing this requirement more frequently from our customers mainly from Retail industry. My proposal is to extend standard Business Central to have a new option Batch Posting under Transfer Order Page and a new report to Batch Post Transfer Orders. In fact, the proposal is to have the same for Transfer Orders as we have for Purchase and Sales documents. Some detail here: https://docs.microsoft.com/en-gb/dynamics365/business-central/ui-batch-posting -
Items List should not show blocked Items (by default)
When an user access to Items, Items List opens (Page 31) and it shows all Items.
Some of our customers proposed to have an automatic filter opening this List Page only showing the non blocked Items (by default).
Like a System Filter by default.
If the user wants to see all Items (including blocked ones), can access to Filter section and clear the filter Blocked = No.
This logic already exists when an user drill-down from Customer or Vendor Balances. By default, there is a system filter to only show the transactions Open = Yes.
This idea seems to be simple to implement, have a low impact in overall solution (including ISVs) and it will improve End User Usability.
-
Data Exchange Definition - Ability to insert Carriage Return as a Custom Column Separator
Data Exchange Definition - Ability to insert Carriage Return as a Custom Column Separator
Data Exchange Definition is a great tool to be used in order to generate files with the required formats to be imported as Bank Payments.
Recently, we received a requirement to have one line per field instead of one column per field.
The first 25 lines represents the first payment record, after line 26 until 50 represents the second payment and so on.
To achieve this without customisation, it's required to be possible to select 'CR/LF' in Custom Column Separator field and being interpreted as Carriage Return/Line Feed. At the minute, if we type 'CR/LF' in Custom Column Separator, the file is generated with 'CR/LF' between columns instead of transforming it as Carriage Return/Line Feed.
As a workaround, we cloned the xmlport 1230 "Export Generic CSV" and we added the line of code FieldSeparator = 'LessSymbolCR/LFPlusSymbol'.
It would be great to have this option in core standard product.
IMPORTANT NOTE: When you read 'CR/LF' you should read 'LessSymbolCR/LFPlusSymbol'
By LessSymbol and PlusSymbol we mean the math symbols.
By unknown reason, these symbols are not allowed in this form. We received the message: "We have encounter some malicious input. Please remove that and try again"
https://community.dynamics.com/business/f/dynamics-365-business-central-forum/487552/data-exchange-definition-to-export-a-bank-payment-file---one-line-per-field
-
Ability to export several Configuration Packages at the same time
Configuration Package - Export Package functionality only works for selected configuration package.
We have the ability to select more than one configuration packages but when we select Export Package functionality, it only exports one and not all selected.
This idea is completely aligned with general way of working of Business Central and it will represent a very nice improvement to onboard new customers and rollout solutions
-
New Vendor Bank Account API
After checking all available APIs available here https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/api-reference/v2.0/, it was identified the need for a new one to create Vendor Bank Account through an API.
It's possible to create/update/get a Vendor using https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/api-reference/v2.0/resources/dynamics_vendor with the basic fields but not possible to include Vendor Bank Account details.
A new API should be created to turn possible to create/update and get Vendor Bank Account Details (Table 288).
It will is also important to guarantee this new API is linked with Vendor API to allow the ability to use the expand function.
You’re offline. This is a read only version of the page.
