web
You’re offline. This is a read only version of the page.
close
  • Ability to change the calendar start date

    In Business Central, when you're in any date field, a calendar pops up. By default the calendar starts on a Monday. It would be nice if a user can change the start date to a Sunday.
  • Predetermined Quote Valid Until Date in a Sales Quote

    In the Sales Quote, it would be nice if the "Quote Valid Until Date" can be auto populated based on a setting either on a customer or on the Sales & Receivables Setting. For example, if I can set the Quote Valid Until Date to always be 30 days from the Document Date that would pretty handy rather than always requiring a user to always populate the field.
  • Merge customers and vendors

    Sometimes customers and vendors are created in error and are a duplicate of another record. It would be nice if there is a merge function in Business Central to get rid of the duplicate. In GP, there is a utility that allows a user to merge records and it will also merge all the posted transactions - if Business Central can have something similar, it would be extremely helpful.
  • Sales prepayment status doesn't change

    When I create a sales order that requires a prepayment, I would post the prepayment invoice and the sales order status changes to "Pending Prepayment". However, the the prepayment invoice is paid, the sales order status is still "Pending Prepayment". It would be great if the status can be changed to "Prepayment received" so a user knows to release the sales order.
  • Allow GL Currency Revaluation

    Currently when you go to "Currencies" and go to "Adjust Exchange Rates", you can only run the revaluation for the Currency alone. Meaning revaluation is done for all GLs at the same currency exchange rate. What should happen is allow users to run revaluation by GL because GLs can be revalued at different rates. The same exchange rate should not be applied to all GLs.
  • Allow voiding a payment that's posted in a currency that's different than the Local Currency

    Currently when you try to void a payment that's booked in a currency that's different then the company's Local Currency, a user will get the error message that they cannot void the payment because it's associated with a Realized Gain/Loss Entry. To get around it, users need to book a Refund payment. I am suggesting that this be fixed where a user can just Reverse the transaction without having to book a refund and then apply the payment to the refund. Not only do they need to book a refund payment and apply it, in the Bank Rec, they'll need to remember to check off the payment AND the refund (i.e. 2 lines on the bank rec). This seems like too much work just to void a payment.
  • Ability to Default Dimensions

    In the Dimensions page and you go to Navigate > Account Type Default Dim. when you set a value in the "Dimension Value Code", it doesn't actually default the Dimensions Value to the Table you've set. According to Microsoft, this is by design and "this functionality is to prevent posting from occurring without the Dimension Value defined. It doesn’t default the actual Dimension setup on the Item." It would be nice if the Dimension Value actually defaults to the master record (e.g. Customer, Vendor, and/or Item) you're trying to create.
  • Job Journals posting using the Resource posting group

    When posting a Job Journal for different Resources (People and Machine) the Job Journal posts based on the Job Posting Group. However, when there are Resources that are people and machines, they often go to different GLs (i.e. different Gen. Product Posting Groups) that is assigned to the Resource. Currently, posting to the GL assigned to the Resource is not possible in a Job Journal. The Job Journal will post all Resources to the one (1) GL assigned in the Job Posting Group setup. Therefore, we would like the the option to choose between posting based on the Resource posting or the Job Posting Group.
  • Field level security to restrict visibility on fields

    In Business Central, it would be helpful if there was the ability to have field level security where a user can restrict certain users' visibility on fields in certain pages, windows, and/or reports. It doesn't make sense to rely on custom development work (i.e. an Extension) to be built to restrict the fields from users.
  • Restrict a Dimension Value range for specific master records

    Right now we can default one Dimension Value on a GL. However, it would be nice to restrict a range of Dimension Values to a GL, Customer, Vendor, Job, etc (i.e. all master data records). For example, if I have a Dimension called "DEPARTMENT" and the Dimension Values are 100, 200, 300 and I have a GL 40010; I want to define on the GL to only allow Department Values 200 and 300 to be used on GL 40010. Currently I can make "DEPARTMENT" Code Mandatory on the GL but this will accept all Dimension Values being posted to GL 40010.