Liquid error: Value cannot be null.
Parameter name: key
Microsoft Dynamics 365
I believe the solution can go either way. Either you cannot select an item from a drop down (if an item was already selected), or everything should be updated as if you'd just selected an item.
Support the idea
Also needs to be for all entities including custom, and also not just for Sales. E.g. having a set of playbook activates that can be tracked etc would be extremely useful on the Case entity.
Getting tired of functionality that is general in nature only getting released for specific entities and only in specific SKU's (functionality that is general in nature should be made available to all modules not just Sales all the time this includes PDF - this should be available everywhere Word Templates are available).
This would really help to get the integrations working with the simplicity that is expected from interconnecting PowerApps/Flow and such with D365FO without building custom connectors...
In the presented case, we need to add a service account for each new entity and change the logic of the connector with an additional authentication. This just doesn't work.
This is such a pain point. Please allow sorting by column headers or at least some additional sorting options.
An often requested piece of functionality and would be a good addition to D365. The work around is to have many production orders with smaller quantities but that is very cumbersome and creates more confusion on the shop floor for some customers.
Still pretty complicated to implement. This is a Marketing app and the end users are not technical. This should be more point and click without the need to create blob containers, access the azure portal, using storage explorer, etc.
In addition to the above:
- Ability to add and format a table....without resorting to hand coding HTML.
- A true full screen editor, the instead of the shadow modal form.
- Better and more templates. Many are old and don't even render properly in the editor.
- Fix the bugs the editor has, often times have to refresh the screen to be able to drag and drop the Sections
- Support for attachments
- The Assist Editor is confusing and difficult to use
- Drag and drop social buttons/links
Full/Partial qty inbound/outbound feature should be available in every document
In general scenario round off should behave on normal rule base. Because many integration processes configure based on normal round off. Otherwise there will be a mismatch in balance between Legacy(Third party software) and D365.