Comments
It would in fact be even better to show both the local currency code, the amount in local currency, the transaction currency and the amount in the transactions currency in all screens system-wide. E.g. also in sales invoices, purchase invoices, ...
My proposal is to use the suggestion of the original poster, but adopt it everywhere AND also show the local currency code (instead of leaving that blank).
We are working with foreign currencies for about 30% of our transactions and in any given selection or page view there could be a mix of different currencies. Very often the user would like to see the local currency amount equivalent on posted sales invoice lines and totals. Seeing both local and transaction currency for every document and transaction is useful and should not be a problem on screens with increased pixel real-estate.
If you switch between BC-companies with accounts in different currencies, the 'local currency' might not be immediately obvious for the user. It is better to always show that local currency instead of leaving the currency code field empty, as is now the case. (Or at least make it optional to show it when the user wants.)
To prevent users from changing other users' job queues, could we restrict users to see their own job queues only?
We can introduce a job queue permissions for users who are responsible for managing / monitoring recurring job queues.
Allowing admin / users with specific permissions to see all job queues so that no user will 'accidentally' pause / delete job queues set up by admin or other users.
Bookable Resource Booking sync to Outlook was disabled on a platform level due to platform issues. In the 2021 release wave 1, the following feature is introduced to Field Service:
https://docs.microsoft.com/en-us/dynamics365-release-plan/2021wave1/service/dynamics365-field-service/appointments-data-included-resource-scheduling
It is possible to programmatically create Bookable Resource Bookings to fill the Schedule Board from Outlook events with Power Automate, Logic Apps or Azure Functions. A two-way sync is hard to achieve as Project Operations produces a Bookable Resource Booking record per booked day, easily leading to a bloated Outlook calendar.
An option could be to sync Resource Assignments to Outlook from Project Operations. This can be done with Power Automate, Logic Apps or Azure Functions, depending on throttling considerations.
When creating Word Layouts with tables the alignment within the table is not maintained all the time.
E.g. A Purchase Order layout is generated which includes a repeating line for the PO lines. Some of the table is left aligned and some of the table is right aligned but when a change is needed to the layout and the existing layout is exported to Word the alignment in the table is not per what it was set previously nor what is working in BC.
This also occurs when the Word Layout is just opened from the local machine when a small change to the layout is required during initial testing.
Steps that happen.
1. Export a Word Layout from Business Central, all is working as expected with all cells left aligned.
2. Set a cell in the table, on a repeating line, to right aligned
3. Save the word layout and close
4. Import the layout into BC
5. Process Report to view the changes and note a small change that needs to be made to the Word Layout
6. Open Word file, with or without downloading the layout again
7. The field that was previously right aligned is now left aligned again
This is absolutely needed to create a seamless task creation step within Outlook and have the task tracked to Dynamics 365 to a Regarding record. In addition, providing the ability to create recurring tasks in the same manner.
1. Create Task in Outlook, using Dynamics Add-On
2. Set Task to recurring within Outlook
3. Create multiple tasks within Dynamics 365, per the recurring task settings.