Liquid error: Value cannot be null.
Parameter name: key
Microsoft Dynamics 365
Rightly said an advance system like D365 should be able to stop zero price invoicing.
While I'm not Akira, my user scenario would be very simple:
User A works primarily in Dynamics.
User A wants to create an appointment in Dynamics, which also contains details for a Skype Meeting.
There's no button to turn the appointment into a Skype Meeting, so he is unable to do that.
User B works primarily in Outlook
User B wants to create an appointment in Outlook, which also contains details for a Skype Meeting.
There's a button (via the Skype plugin for Outlook) that allows him to automatically have conference details (and a link to the Meeting) added to the appointment.
Add a similar button to Dynamics appointment form.
We have got several customers who also need this functionallity
I agree, currently we can add default values to certain types of fields but we need the ability to add a default value to all types of fields like text and currency
Easiest function to change Company will be great !
Perhaps button on main page.
The data Exchange in the automotive Industry is often based on VDA Standard. The VDA 4984 defines item no. with a length of 35 Signs, so there is the Need of 35 Signs at least. Without changing those field (Item Vendor Number and Item Reference No.) this branch cannot be supported with standard BC.
A field that displays a configurable mask such as *****9999 (displaying last four digits only) or ********* displaying no digits) but that would allow a user with appropriate credentials to enter or modify the SSN would be good. If the user is enabled for access under field-level security a fly-out prompt could be presented (similar to the composite address prompt on the Contact form) when the user clicks on the field. When user exits the prompt it would return to the masked display. We are using Sales for a financial services app, where this enhancement would be very useful.
As a customer point of view PO and SO are two separate entities, though a PO is created through SO in Direct Delivery process still it will be considered as a separate module at the time of processing so this needs to have a workflow applied as a standard feature.
This is something that we've implemented for more than 10 customers. In the Retail/Fashion/Sporting goods industry, all Booking orders have multiple payment terms (Payment schedules).
Much needed feature ! Not all companies handle physical items. For a ''Service'' with a lot of requisiton/purchase orders, this is a must needed feature to speed up accuracy, budget tracking and month ends.