Skip to main content

Using SCRIBE Online to Migrate Opportunities Into Microsoft Dynamics 365

  Recently while creating map's for a data migration from a legacy system to Microsoft Dynamics 365 using SCRIBE Online, I found that I needed to bring in Opportunities.  Anyone that has worked with CRM for a time, know's that migrating closed opportunities into CRM can be a bit of a pain.  I was having one issue in particular when bring this data in, the actual close date was being set to the day the record was migrated into CRM.  This is because of how CRM handles opportunities when they are closed.

Here is what I was doing:
  1. I performed all my look ups first to get the associated account and contact from CRM.
  2. I created the opportunity with the closed status of won or lost (see links below for website to get the standard values for reference).
  3. This makes the opportunity as read only (which I expected to have happen.  But, the actual close date was set for the day the record was created.  Even though I provided a date in the actual close date field.
Why is this happening?
     This happens because when you close an opportunity in CRM, it creates an opportunity close activity.  Doing an advance find I was able to locate this record and the actual value and actual close dates where blank.  Keep in mind, my mapping didn't create this record.  CRM created it when the status of the opportunity was set to one of the closed status (won or lost).

How do we over come this?
    The way to over come this is really simple.  It was a post in the SCRIBE forums on how to do this with SCRIBE Insight that helped me come up with the way to do it with SCRIBE Online.  Here is the solution:
  1. Create the opportunity with the close status you want (won or lost).  This will make it read only.  Don't worry about that.
  2. I recommend doing an if else block after the create opportunity step.  This way if you are bring in open opportunities you the if else will be skipped.  We want to enter the if statement only if we have have a closed opportunity.
  3. Inside our if else, we want to do a lookup to get the opportunity we just created.
  4. After our lookup do a delete block against the opportunity close table.  Use the opportunity id in the matching criteria.
  5. After the delete we want to do a create opportunity close and populate it with the actual close date and actual revenue.
  6. Finally, do an update block to the original opportunity and populate the actual close date and actual revenue.  Even though the record is read only, it will update these fields.
Screenshot:

Helpful Links:

Comments

Popular posts from this blog

Dynamics 365 v9 Unit Testing and .NET Confusion

Recently while creating a plugin for Dynamics 365 v9, I ran into an issue trying to connect to CRM via the tooling connector in my unit test project.  The underlying problem was that the .NET version I was using in my unit test was 4.5.2.  This was preventing me from being able to connect to CRM to create my organization service.  I updated the .NET version on my unit test project to 4.6.1 and was then finally able to connect.  I will also add that I am using the latest nuget package version for Dynamics 365 v9.

For consistence, I updated the plugin project I was working on to .NET 4.6.1.  Locally, everything was working great.  I was able to connect to CRM and make sure that all the methods I had written did what they where suppose to do using test driven development practices.

Then when publishing my plugin via the latest version of the plugin registration tool, I received an error and could not publish my plugin.  The error was due to the .NET version of my plugin project not bein…

SCRIBE Connector Development - Handling Array List

Are you working on creating a connector with SCRIBE's CDK?  In your connector do you have an array of strings or list of  strings that you need to pass?  SCRIBE makes this easy to do within the CDK and SCRIBE Online.

I came across this scenario on a connector I was creating that passes a JSON message to an API.  In the JSON message it had a list of strings for entity ID's. Here is an easy way to accomplish this:

1) Create you Property Definition as past or your Object Definition.
1: new PropertyDefinition 2: { 3: Description = "Use TOLIST() to pass in a list of entity id's.", 4: FullName = "Entity IDs", 5: IsPrimaryKey = false, 6: MaxOccurs = 1, 7: MinOccurs = 0, 8: Name = "PublishTo", 9: Nullable = true, 10: NumericPrecision = 0, 11: NumericScale = 0, 12: PresentationType = "string", 13: PropertyType = typeof(string).Name, 14: Use…

Getting Started Connector Development

One of the benefits of working with Scribe Online is how easy they make it to create connectors if one does not exist.  In this blog post we are going to look at how to get setup, if this is the first time you have made a connector for Scribe Online.  But, before we get into that, we should first make sure that a connector doesn't already exist that can handle what we need.

We can do this by looking in the Scribe Online Marketplace.  Still not seeing what you need?  Reach out to Scribe directly or ask in the Scribe forums if a connector exists for an application.  There are instances where a connector exists but is not listed in the marketplace.  An example of this is for a client that I built a connector for.  They didn't want to setup a system to run the on-premise agent, so they asked me to set up the connector to run on Scribe's cloud agent.  This meant that I had to submit the connector to Scribe for validation.  Once published the connector is in the Scribe marketpla…