Liquid error: Value cannot be null.
Parameter name: key
Microsoft Dynamics 365
If the voucher number could be a hyperlink back to original voucher that would be ideal...that way all elements of the voucher (workflow history, attachment(s), would all be clickable from the payment journal.
This is extremely useful! Preview is used to test functionality and setup of Data! sometimes we forget the Deletion period of 30days so a 5 day pre-warning would be ideal!
I have now had numerous customers that have Customer or Item related records that are over 50k records. In one instance I have a record list of 166K+ customer records to bring in..
I have tried Items with 10k in and its taken over 5hrs to import using Configuration Packages! even splitting down the 166K to smaller files (2000 records for example, which take 10-15mins to process) will require 85 different files to be created. This is still going to equate to over 28hrs of Data Import!! then I need to import 160K+ contacts!
There needs to be a faster and more efficient method to bring in large numbers of records.!
The name is also wrong in the Path
Text shows "Rangfolge für Rabattausgleiche erstellen" while the item description already show "Skonto"
hope this cn be fixed as well
i strongly agree - must have!
Absolutely a fantastic feature. Having this feature OOB for system and custom entities will be critical for business that want for governance, enforcement of best practices, reporting and adapting best practices on evolving needs. Would love to see this ffeature become generally available. We can customize the Task creation to establish some calculated Due dates for any of these playbooks. With Track Progress feature, having a non-intrusive mechanism to assist with enforcement of best practices is quite useful.
Dear Business Central Team
Then how can we migrate and start customer on Business Central without importing ledger historic data?
This is not a feature but a real issue.
Without that you are blocking all project with data migration...
Which is a nightmare.
In organisations with strict IT security rules, some form of audit trail for IP address whitelisting is a must have. Also some way to enable bulk updates will be useful, e.g. via CSV file import.
I would settle for just being able to download a month's worth of monitoring data in a CSV file, if it will help to make this feature available quicker.
In our setup the limited selection of start dates in the deferral templates also prohibit the use of deferrals. So I would like support the OP's request for an expansion here.
In our case most deferrals would run over a calendar year. If an additional option 'Beginning of next Calendar Year' could be added (to the Start Date dropdown in the deferral template) we would be very happy.
I cannot imagine it could be too difficult for Microsoft to add a calendar year to the dropdown. However, doing deferrals by hand in an extension by putting the amounts on a G/L account and performing the deferral manual is infinitely more complex and in the end still a hack of the standard.
I can imagine other companies might benefit from a 'Beginning of next Account Year' option as well.
But I do admit that in some cases a custom start date and length in months for a deferral would even be better. I can imagine that is more complex to realise in the BC standard. In any case that change would only cover a very small percentage of our cases. So at least for us (but maybe not the orignal poster) a calendar year option would solve most of our problems with deferrals.