Check out the latest features available in Dynamics 365 for Customer Engagement, including LinkedIn Connect, Voice of the Customer and Universal Resource Scheduling.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants.Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements.
ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
I am currently learning on how to use SSIS for data imports between instances.
I have some basic contact records that are being moved, however, some of the system users are not present in the destination instance (no longer work there etc.). What is the best way to handle these users? I was thinking of using their owning business unit team to take ownership instead but am having trouble on how I would do that within SSIS?
Thanks in advance
When doing migration from systems, there is usually the case that users that were created in one environment do not exist in the target environment, especially since your users are integrated with Active Directory.
There is a concept in Dynamics CRM called Stub users, which is what is used to handle those users.
To Create a Stub user, simply create a new User in Dynamics and specify the UserName to be "email@example.com" (for example), instead of "DOMAIN\User". You can specify the real email address if you need to. This will not link the user to AD, but create the user as a Stub user. You can give the user the security role that it needs, and these users need at least Read Access Security role for users to be created for them.
You can see a previous article I wrote about this issue here:
Hope this helps.
Hmm sounds pretty interesting, I didn't know this was a feature of Dynamics. Does this work for CRM 2011 where I am currently testing these scripts?
I am currently thinking about how I could implement this into the SSIS scripts however I am having a difficult time on what components I should use to check when a systemuser doesn't exist etc. Can you provide a few pointers on how to do this dynamically please?
I have tried this and I get the following error. Can you advise? I have tried the 'domainname' as both the standard DOMAIN\user format and also the user@DOMAIN format. When i try the second format, the error comes back as domain logon is invald. When i try the first format, the error is below;
"CRM service call returned an error. LookupAccountNameW failed with error"
I am on Dynamics on-prem version 8.2.6 and am mapping the following fields using SSIS KingswaySoft adapter; domainname, businessunitid, firstname, lastname, internalemailaddress, islicensed, issyncwithdirectory
Business Applications communities