Liquid error: Value cannot be null.
Parameter name: key
Microsoft Dynamics 365
Agreed - this is a common requirement and would be a welcome addition.
Don't have any update for the function?
REMARK: Not identifying a financial statement by shorter periods of time, user may potentially process multiple calculations, rather then visualizing a financial statement in other period segment of length preferences.
I feel like this one would be a very easy quick win - we built our own batch method to allow the forecasting team to use select criteria (records to include) on the job to select all the matching forecast records they wish to allocate with the same key. We are dealing with tens of thousands of records that need to be split into weekly buckets, users cannot be expected to do this manually one line at a time
This change request would help a lot !
We have more than 70 % Drop Shipments and have big struggles with the purchase invoice posting.
My suggestion would be:
Microsoft will make a new setting in the Purchases & Payables Setup. There could be the following field for drop shipments:
Allow purchase invoice posting before sales invoice posting (answer: true/false)
Then every mandant can choose his own way.
This is indeed very much needed, as more and more B2B customers are exploring the call center functionalities. I find this need in every project I am involved, so please consider to re-preoritize this quite simple feature.
It would be sufficient in my perspective to have a drop down which allows you to chose for which call center the sales order should be created when the user presses the "new sales order" button in the customer service form.
Use cases additional to the one mentioned in the initial idea:
- backoffice users for B2C stores which are handling complaints need to create sales orders and/or return orders via different call center channels within one legal entity, so that the financial dimensions and prices/discounts and modes of delivery apply properly
- backoffice users for B2B stores may operate on different legal entities, and therefore need to be assigned to at least one callcenter per legal entity (again to handle the prices, discounts and modes of delivery)
- provide different financial dimensions (which are tied to the call center) by simply choosing the right call center
Has there been any update on Treasury Management Module for D365 F&O ? or could you suggest any add-on's certified by Microsoft
Thank you !
wonder why it was not implemented before
What was released isn't what Frédéric had suggested. The feature that was released allows users to use date formula to define when to run the scheduled job - i.e. "CM+1D" in the 'Next Run Date Formula' field will schedule a report on the first day of the next month.
This feature is actually not useful if you're scheduling a report where you have to define a date filter - i.e. if you want schedule an Income Statement to run on the 8th day of each month for the previous month's results.
If you use the date formula in the date filter, assume today is 14/06/2021 (DD/MM/YYYY), "CM-2M+1D..CM-1M" this will give the result "01/05/2021..31/05/2021" - this formula on the date filter doesn't recalculate. The same report will run every time it's scheduled to run. The expectation is that when this runs in July, I get the Income Statement for June, when this runs in August, I get the Income Statement for July and so on. I don't want the Income Statement for May, every month which is what will happen because the date filter formula isn't recalculated.