Liquid error: Value cannot be null.
Parameter name: key
Microsoft Dynamics 365
"...hates that change" - agree!
This is a modification that never should have been done - entering Description trigger a lookup into Item, Resource, ...
It was never broken.
Secondly this should be optional.
It is very common that Description on Sales Lines is changed by various reasons.
At the end it is the customer's system.
This is now possible, however only as a back office MS Support process.
MS Support, can move a Tenant-Environment from Tenant to Tenant, you have to then reset the new users and it is a pain to work through, but it works.
MS Support are able to 'move' an environment from one tenant into another tenant, this was completed recently for on of my Clients, from a US Tenant to a UK Tenant without issue.
What happens however is that the user@US-Tenant.com is disabled and recreated as user@UK-Tenant.co.uk and any user personalisation is lost against the user@US-Tenant.com and therefore the user@UK-Tenant.co.uk, which is the same physical person has to process all their pages changes again.
What is needed is a method to export/copy User Personalisation and import against another User Personalisation record. in the same way that Profiles and page customisation can be exported/imported.
Agree so much needed, I am about to create 10 Production Environments into 1 tenant with over 100 users across the tenant, I am done one additional already and had to go through 80+ users to disable access to the new Production Environment.
Need to be able to do a 'select AD User/s' rather than pull all please Microsoft.
I have the same question, so the answer is to select the existing available Norway East DC which I will look for and get MS Support to migrate our client.
At Dr. Martens we have leveraged Foreign Trade to support commodity code functionality in Americas and EMEA roll outs but now that we are deploying to AsiaPac (with HK first followed by CN, JP, KR) we are having to rewrite this because Foreign Trade is not available in these legal entities. Microsoft - Please include this in your GLOBAL solution! Thank You!
Disagree... material availability should not be considered as a driver to firm or not to firm planned production orders. That's a matter of production release. Very often we need to firm planned orders in advance, for many reasons (example firming a production plan MPS).
This functionality should be taken into consideration as soon as possible.
Finance and operation covers it by using the Dual-Write Solution and I know BC Team is working on this scenarios as the amount of Customer that are using Dynamics 365 is increasing daily.
Just ask for any help from our side.
To my opinion it is not acceptable not to have those features in the standard. We strongly need it.
Is there any progress on this item? For me it's a must have.