Liquid error: Value cannot be null.
Parameter name: key
Microsoft Dynamics 365
We need for D365 Commerce (website) as well, especially where we have one Online Store (website) operating in the EU. The current requirement includes; English, Italian, German, French; where we are configuring the system in English and would prefer adding translation for the other 3 locales.
This feature will come in a great use! Hopefully we will see this happen very soon
The feature was documented on the German-language version until end-of-2019, is was just missing in the application - so our customer was & remains especially disappointed that this issue is still unresolved - although it was working in AX, although this idea is here since 2017.
This was an important part of the sales and marketing module. Please re-implement it as soon as possible!
The ideas is to go for the same principle for Delegated Admin as being implemented in Azure Lighthouse. This means that you can create Delegated Admin User Group into the Client/Customer Tenant direclty from Azure Lighthouse and put Partner Employees into these groups allowing them access to customer resources. This is also more compliant with security measures and rolebased access control. We are aware of the fasct tha O365 is currently not supported by Azure Lighthouse.
In principle its more or less the same as you are doing with the Device User. If in the Device User Permission Group the Guest user is added or the partner Delegated Admin user its all working. And the customer is more in control of its data within the tenant.
So you can then create Role Based Partner Permison Groups allowing specific users only access to for instance a specific D365 BC tenant. And we do not require full Azure tenant access for all employees. We can reduce this for only a few Azure Admin employees.
For the UK too please this is a very common requirement
Thank you for posting this very much required idea, Frans!
Maybe, just in order for everyone´s better understanding, one typical scenario that we experienced with pain point no. 2. "there is no setup for a date range for the shipping date":
- We have orders for the same customer and delivery address etc. with different delivery dates for the next 5 days for example!
- Shipments should be split by requested/confirmed delivery date of the sales orders lines.
- This means that we want to do only one automatic release to warehouse batch job per day covering the order lines due for the next 5 days.
- Currently it´s only possible to get all order lines consolidated to one shipment!
- The workaround with multiple release batch jobs, filtered by (day(X)) is suboptimal!
This is a problem on every workflow, not just purchase orders!
This will also open up the doors for more international companies especially the mining industry. We have 4 legal entities with 4 different language requirements but all companies share master records, to manage the language is a pain and not very efficient for cross-functionality of users moving around operations.
Yes, without this 'hopefully coming soon new feature', the RSAT test case about workflow is very hard to run without failures.