Microsoft Dynamics 365
The Fringe Benefits Tax Returns (FBT) does not follow Australian Financial Year either, it's dates are from 1st April to 31 March.
Currently this has to be achieved by running the Ledger Transaction List report twice for the two financial years otherwise you receive the error message "dates must in the same financial year" which is time consuming.
This is one of common scenario where place of Work order is changes after the booking is created. But, the travel time is not updated although the geo location is updated in the work order/booking/requirement.
At least hide it on on-prem installations.
hi i am also facing same issue and it's taking too much time
so please consider this request urgent baizes and solve it immediately
Also voted. Either something is synchronised or it isn't, there's no half-way house. If the status (or anything, in fact) changes in one system, it must also change in the other, else you have two sources of the truth.
Its great that we can integrate the dataverse with the F&O but there are so many holes that need to be tidied up. This is an issue and should be sorted already. Closed in the Dataverse then Finished in F&O otherwise provide manual way to perform this in F&O at least
Any news about this idea ? Some of our customers need this too
Or someone find an alternative?
Maybe the proposal of the idea is too general and needs more examples to gather more votes:
I found 12 matches of Scope('OnPrem') in the sales line table. I was wondering, why the procedure CopyFromSalesLine(FromSalesLine: Record "Sales Line") for example needs the scope OnPrem?
These examples make it extremely difficult for us to program an app that complies with the universal code initiative.
This is a must have