on
RE:
Delegation of timesheets is a painful process when you have 100's or even 1000's of timesheet resources and you want certain trusted user(s) in a central department to be able to act as a delegate for any of those timesheet resources. It is a maintenance nightmare. Option A would be a role/permission or other option to be a delegate for anyone! Option B might be a "mass select" option (for this user I want to select every resource!) (with an option to auto-select new resources as well). Option C is some sort of "auto-assign" rules? The current solution is inefficient and a burden to manage.
RE:
ONE IDEA: (doesn't solve lost workflow history called by recall but it is a step in the right direction):We find the need to have to recall the timesheet to be clunky and an unnecessary step. Microsoft probably has a reason but it is not documented. If nothing else maybe the experience could be modified so that: (a) the Add Line option remains enabled, but (b) when the Add Line button in clicked in a Rejected status it would throw up a message that says: "This document is in a rejected status and must be recalled to add or remove any lines. Do you want to continue? Yes or No." If no, nothing happens. If yes, the recall occurs, AND a line is inserted. It would make the experience much better and avoid users calling the help desk to report that they "can't add or remove lines"!
RE:
Same exact (great!) idea requested for Expense reports: https://experience.dynamics.com/ideas/idea/?ideaid=71a46a55-c178-ee11-a81c-000d3a7ae3ff
RE:
We see the same exact experience also with a timesheet and find the need to have to recall the timesheet to be clunky and an unnecessary step. Microsoft probably has a reason but it is not documented. If nothing else maybe the experience could be modified so that (a) the Add Line option remains enabled, but (b) when the Add Line button in clicked in a Rejected status it would throw up a message that says: "This document is in a rejected status and must be recalled to add or remove any lines. Do you want to continue? Yes or No." If no, nothing happens. If yes, the recall occurs, AND a line is inserted. It would make the experience much better and avoid users calling the help desk to report that they "can't add or remove lines"!
RE:
It should solve the blocking error described in the link here reported.https://thedynamicsexplorer.com/2020/02/27/dynamics-365-business-central-error-message-select-dimension-value-code-for-dimension-code-when-applying-documents/It is a blocking error. And the work arount is not acceptable for Business Central product !!!
RE:
It would be helpful to see emails being sent to customers and vendors. We would also like to see emails from Customers and Contacts that have emails associated with them in BC linked in BC. Right now a sales person needs to be assigned to a Customer and only his or hers emails are being linked. We would the option to link all important emails to a customer, vendor or contact
RE:
It would be good if we can actually add on the top of the pre-built model similar the Readsoft Kofax. Also pls implement double click on the invoice mapping field to mark a field. In addition, some fields of the pre-build model cannot be edited/removed such as line level qty, unit price etc.Atm having 2 different model is unnecessary complicated.
RE:
There's an errore in the correct voucher.It must be like this: AMOUNT FIN TAGF000001 24404000001-CC1 1000 X4000001-CC1 110 X (THIS IS THE NON DEDUCTIBLE TAX LINE)2000001-CC1 110 X (THIS IS THE SALES TAX LINE)4000001-CC2 1000 Y4000001-CC2 110 Y (THIS IS THE NON DEDUCTIBLE TAX LINE)2000002-CC2 110 Y (THIS IS THE NON DEDUCTIBLE TAX LINE)The "TaxTransGeneralJournalEntry" table it is very helpfull to implement the correct solution because it joins taxtrans and generaljournalentry transactions.
RE:
It would be extremely helpful to be able to quickly confirm who a sales invoice was emailed to.
RE:
A strong solution would be to make the bank details table a date effective table, and enable the changes through Self service and Teams