0
Category:
STATUS DETAILS

Comments

Thi is a great idea, it will improve Business Central.

Category:

We really need it.

Category:

The would be a fantastic and much needed addition. This would allow for the most accurate reporting and up to date information to be added in the system. It would also alleviate extra work that must be completed to pull, review and file 1099 reports.

Category:

Yes, please. This should coincide with the "Report 1099" toggle switch so it is easy determined why a 1099 is or is not reported.

Category:

This has been a perennial grievance of mine, along with getting rid of the 'Initial public view' SB tab (turns out it was an easy fix). However, the JSON code appears to already exist.


Here are the steps that I have working in a PoC environment atm:

  1. Do a classic Advanced Find and search for 'Schedule Board Settings"
  2. Select your Schedule Board Settings row (To hide 'Initial Public View', just select and deactivate - problem solved)
  3. When opened, scroll all the way to the bottom of the Settings field in the 'Other' section
  4. Locate "ViewMode":"hourAndDay","WorkHours":{"end":18,"start":8} I set the default hours to 8A-6P here
  5. Insert the following code after the "hourAndDay","WorkDays":{"Friday":true,"Monday":true,"Saturday":false,"Sunday":false,"Thursday":true,"Tuesday":true,"Wednesday":true},"WorkHours":{"end":18,"start":8}
  6. Save it and refresh your SB
  7. Open the Schedule Board's Schedular Settings and you'll see the updated UI with the individual day selections

Category:

Many good points here. Voted! Especially I am looking forward for a feature which allows to link multiple purchase agreements to one purchase order. Also not having PurchAgreementID on the header or lines is inconvenient. The display field with direct link would be great

Category:

Great idea! I would suggest also to give possibility to create link on PO lines to different agreements.

Category:

I would suggest also to have a purchase agreement ID display on the related purchase order. Right now there is only hidden information on record info, or button which transfers to related agreement

Category:

BC Team - if you do consider implementing this method, please also consider an overload like the following. I believe this would cover another very common developer scenario.


Text.Join(Separator: Text; RecordVariant: Variant; FieldNo: Integer)

Category:

Agreed, many entities are facing this issue currently. Such a feature will be really helpful and useful.

Category:

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 500