Facebook has a "View as" feature which lets users to view their profile as another person: http://www.wikihow.com/View-Your-Facebook-Timeline-As-Another-User
This feature in D365O would greatly improve testing the security role configurations. Security/System administrator would be able to click on a "View as" button on any AX form and select a system user from a dropdown to view the form as that particular user.
It would be great if you can add this to the road map.
In D365 if we need to create a new label and assign that to Label or Help text of an item, we have to create label in the label file and then paste in the object. There is no way by which via the object properties we can create a new label or edit existing one. There should be an ability to create a new label or edit the existing one when we go through object properties where Label or help text is provided.
Many AX / D365 customers have supply chain requirements that include scanning barcodes that are formatted to the GS1-128 standard. This includes barcodes that have multiple data elements where each element starts with an Application identifier and can either be fixed or variable length.
- For use with the D365 Warehouse App and WHSWorkExecute
- Parameters to signify special characters for "start of barcode", "end of barcode" and "end of variable length barcode segment"
- New table for GS1-128 Application identifiers e.g. 00 = SSCC (Licence plate), 10 = Batch etc.
- New table to map the Warehouse App fields to individual barcode segments e.g. 00 = Licence plate, 10 = Batch
- A single scan of a barcode that includes multiple data elements, each with its own GS1-128 Application identifier, will populate all associated fields, e.g. during Purchase receive, one scan will populate Batch + Batch date + Expiry date
- Scanning will include the removal of the Application identifier e.g. 00012345678012345678 will be processed as Licence plate = 012345678012345678
- Applies to all Warehouse App activities that involve the scan of a barcode
SysInfoAction support was not in the list of deprecated features, but it currently isn't available. API is still in place. Where Infolog invocation is supplied with corresponding action it has no effect in the user interface.
Without this feature, where certain document is created, that is serving as an input for following operation in a business process, user have to manually navigate to respective menu item and search for specific document by its identifier. Having direct link to a form pre-filtered on required document would significantly improve user experience and speed up execution of business processes, where this feature would be implemented.
In addition to the current lead time setup and calculation, a default lead time by vendor should be added to the vendor card. In several scenarios we had one vendor supplying 50K plus different products and maintaining the lead time per product is not really feasible. This is only the default vendor lead time, any other lead time calculations can stay as they are.
On print management settings to send commercial documents via email, system only gives an option to specify "Subject". System should allow users to specify generic body for the email. Ideally, this should be linked to email templates to specify dynamics variables in the body.
Suggested by Microsoft – Under Review – 9
Category: Reporting and AnalyticsWhen we export large data from Dynamics 365 Operations to an excel, the data is not copied completely and is restricted to 2000 rows only. We have to export the remaining rows once again to the excel to get the whole data. It will be good, if there is no such restriction and the data can be exported to an excel completely at a time.
Suggested by Microsoft – Planned – 9
Category: Warehouse management
The purchase receiving process has an issue. Mobile client brings the PO line to 'registered' - Nobody in warehouse or office is willing to go to each PO and individually click a "Product receipt" for the registered lines - Batch program in advanced warehousing exists to bring PO lines to "received" status using a LOAD number - So we can auto-create Loads for each PO via a parameter in Transportation - then the batch program , filtering on "inbound" and "open" load status could theoretically handle this.. all PO lines become "received" after being "registered" within a few minutes. But then we still have a Load in status 'received' which is not the final status. somebody will have to manually go to each Load (and we have one load per PO) and say "confirm inbound shipment".. and only then will the load be 'shipped' and disappear from the radar screen. No batch exists to "auto confirm inbound shipments". What can be done to streamline the PO receiving process in advanced warehousing? We would like to request a batch program that processes "registered" PO lines to "received" and also confirms the inbound shipment. There is no business added value to have that last step as a manual step
Please rebuild cross references on the DEV VM before making it available. They currently contain references to modules that aren't included at the box (unit tests) and don't contain xRefs that should be there. For example, I had to rebuild the application to get "Find event handlers" working.
Most vendors operate with a "delivery date" being the date where the items are shipped from their site or most often based on Delivery terms. So depending on the Delivery terms (Incoterms) the concept of delivery date changes. EXW often means a long lead time from shipment to delivery as opposed to DDP where shipment = delivery. There is a lot of misunderstanding with these concepts and that often leads to late deliveries...
This means we need a similar feature on shipment and delivery as on the purchase order. Most vendors assume the delivery date is their shipment dates. It is a tough sell to change this, so a feature supporting this is sorely required and something we always do for our customers.