Liquid error: Value cannot be null.
Parameter name: key
Microsoft Dynamics 365
It should be good to map the function keys:
- general (e.g. F4 is always OK)
- specific per mobile device menu item (e.g. in Sales Pick F3 is Full)
Warehouse visibility added as some partners/ consultants/users implement same warehouse locations across the same warehouses and thus ruining the inventory for the same reason.
Very Good Idea!
I can add, that according to Polish accouting rules, all postings have to represents real transactions. And inventory movement which takes place during price credit notes has nothing to do with real items movements. The same is when we correct tax value (tax item group or tax group value).
It would be great having a way to set the "Dimension Format ID" in the Odata/Entity integration call. So, this way we could use a specific format.
As far as i know we were able to connect No.- series in NAV, so we were able to use different No- series for different usage cases.
How should a template work?
How am i automatical able to determine at document creation time which No- series i should use?
I do not know anything about the document, no responsibility center, not if operation sales or other.
The only possibility we have is to select it manualy before creating the doc, but this is available via the assist edit of the document number, if there are multiple No. -series.
Other pages may require special No.- series from special setups. They may set it in OnNewRecord of the page if required.
Please update the DRA to enable it to run properly as a service for all purposes.
Glad this was added in the April release, however, the reprint does not use the vendor's custom report layout if one is defined in the Vendor Document Layouts. Would be very nice if it did.
This is very required functionality - usually project manager will add the whole WBS task hierarchy and the tasks to the project. it still should not show to all employee in timesheet. Project manager should have option to tell in WBS task level, which tasks are open for using. Now the only possibility is to put all tasks closed and then open the ones which will be using this moment.
Closing will also close the plan of the hours etc. - so it is not a good work around.
To put only active wbs tasks to the project WBS tasks is not also good work around, when system should support Project manager work and this should manually change and update in some other place to follow up with whole WBS hierarchy.
Status Not started is default status in the activity line and of course to change several task to specific status would be good function in the form to select required one to the in progress and to show in timesheet or in other activities. Select the required one to be completed or to other status. This is almost very necessary after the status In process start to work with activity lookup filter and when Not started is default value in the task.
From the side of sales "Sales of services" could be solution for this problem. Customer Balance-to-Date and/or Customer Statement with a working filter on Sell-To-Customer or an option to group by bill-to customer, then by sell-to customer could solve the situation.
Scenario #1 - A company, that is classified as SME, provides services members of international group of companies. The payer is always the group head office, whereas the receiver of the service is a particular company, that needs to be indicated on the invoice. At the end of the period the head office of the customer would like to receive Customer Balance to Date and/or Statement with its total balance and a split of transactions by sell-to customer.
Scenario #2 - a plumbing company provides services to several houses, managed by house -master company. At the end of the month the house master would like to see a separate invoice per point of service, at the end of the quarter a summary per all points of service.
From the side of Buy-from/Pay-to Vendor- advance holders in localizations are created as vendor cards, therefore Vendor Balance-to-Date with a breakdown by Buy-from could provide analytics per each advance holder.
The approach should be not to create separate reports, but to make the existing reports more flexible. Because the our customers ask a logical question - if a system provides an option to specify sell-to/bill-to and buy-from/pay-to for transactions (that is a normal course of business), why it does not provide a possibility to see this information in a report with means of filters or options, but only by filtering posted document lists?