Microsoft Dynamics 365
A better new functionality about this information is the ability to have these on the documents (i.e. Shipment).
To copy the form control name or table name and field name you can follow these steps:
D365 Finance and Operations > Form > Right click a field control > Form information > Left click "Form name".
This will open the Form Information pane. If you expand the Administration tab you will be able to see and copy the following information:
Control name, Control type, DataSource (TableName), Data field, Form name, Menu item name, Menu item type, Query name, Query statement, Caller name, Caller type.
This information is similar to what is displayed in the AX 2012 Form Personalization window.
This information is helpful when writing designs/documentation.
We often need to copy the details for many fields.
The difficulty with the current Form Information pane is that the main form is disabled/greyed-out/unresponsive when the Form Information pane is open.
It would be very useful if the Form Information pane could remain open and update to show the details (Control name, Control type, DataSource, Data field) of the control that is selected as the user selects different fields on a form.
This will be a big time-saver by allowing us to copy the details for many fields much more efficiently.
This will mean the D365 Form Information pane would remain open and update like the AX 2012 Personalization does.
Our customer also generates SEPA DD files for customer collections using ER and subsequently receives a response file in the pain.002 format from the bank. This is the same approach as what we have for vendor payment status updates in D365FO currently.
It offers the user reassurance that the file has been received by the bank and that some basic checking of data has been performed. Any issues can then be addressed proactively rather than reacting to a failed collection.
Personally, it feels like this should be achievable with a small number of changes - allow the ER return format to be mapped to the Customer method of payment. Then either add the Customer payment journal line entity to the existing vendor payment status ER data model and map this OR create a separate one.
The Payment Transfers form already exists, as does the Return file import menu item.
Is there an update on this as we have had the same requirement?
Suggested read on this topic:
Huge missing functionality!
For companies with high volume of jobs, it has strong performance impacts + Completed Jobs are displayed in all lists page (from a PO, from the Jobs List) and it is clearly not user friendly at all.
Would be very useful:
- Going through requisition worksheets is necessary when inventory quantity is tracked as well
- For non-inventory items, it should be possible to create the PO directly from the Job Planning Lines. To meet other requirements Job Planning Lines would then need to be enhanced to enter the Vendor ID.
A work around for this might be to configure your own custom shortcut key in the Visual Studio options:
Visual Studio > Tools > Options > Environment > Keyboard.
Here you can choose your own shortcut key inside the "Press shortcut keys" field (for example "Ctrl+/" or "Ctrl+Alt+A") then click the Assign button.
If you assign a shortcut key to the "View.ApplicationExplorer" command then this will trigger the Application Explorer pane to have focus. When the Application Explorer pane has focus then the Tab key will activate the Application Explorer Search field/control.
If you assign a shortcut key to the "Dynamics365.Metadatasearch" command then this will open the "Metadata search" pane.
This would be super helpful. When you have a project on-going, and you need your non-production environments, the process for exporting PROD to LCS asset library is very tedious. If you have critical data in all non-prod environments that is required for testing, then the steps to get production data into LCS are as follows:
* Export non-prod data
* Refresh non-prod from prod
* Export non-prod
* Import to non-prod data that was previously saved
This does not cater for post SQL scripts required for specific customer requirements. Also, if you have a lot of encrypted data, then this needs to all be manually re-entered as well. It's really time consuming to get a simple backup of production data into the LCS project asset library. This would be super helpful and handy if this was implemented.