1

Posted Journal Layout is so bad and rejected by 99% of customers.


While we asked most of the Customers to print before posting, which is not always a good option, when the customer try to print the posted journals it's coming in a very bad layout, and takes a very long time to generate, we checked the code behind it and it seems needs some optimization and another way of thinking.


I would suggest saving the journals like what happening in Dynamics 365 For Finance and Operations, and mark as posted or not posted.


I hope you consider this idea in the next minor release

STATUS DETAILS
Needs Votes
Ideas Administrator

Can you elaborate what you mean by "a very bad layout," and " it seems needs some optimization and another way of thinking."

Brian Nielsen, Program Manager
Business Central Team