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.

Helpful Links:

Comments

  1. I admire this article for the well-researched content and excellent wording. I got so involved in this material that I couldn’t stop reading. I am impressed with your work and skill. Thank you so much. Azure Data Migration Services

    ReplyDelete
  2. It’s great to come across a blog every once in a while that isn’t the same out of date rehashed material. Fantastic read. Best drupal migration service service provider.

    ReplyDelete
  3. Extremely useful information which you have shared here. This is a great way to enhance knowledge for us, and also helpful for us. Thankful to you for sharing an article like this. data migration consulting services online

    ReplyDelete
  4. For expatiating at the importance of conferences, I actually have to inform you of a mega assembly that happened currently and which I had the honour of attending.AA Meeting directory

    ReplyDelete
  5. I liked your work and, as a result, the manner you presented this content. It is a valuable paper for us. Thank you for sharing this storey with us. SAP integration services

    ReplyDelete

Post a Comment

Popular posts from this blog

Validating User Input In CRM Portals With JavaScript

When we are setting up CRM Portals to allow customers to update their information, open cases, fill out an applications, etc. We want to make sure that we are validating their input before it is committed to CRM.  This way we ensure that our data is clean and meaningful to us and the customer. CRM Portals already has a lot validation checks built into it. But, on occasion we need to add our own.  To do this we will use JavaScript to run the validation and also to output a message to the user to tell them there is an issue they need to fix. Before we can do any JavaScript, we need to check and see if we are using JavaScript on an Entity Form or Web Page.  This is because the JavaScript, while similar, will be different.  First, we will go over the JavaScript for Entity Forms.  Then, we will go over the JavaScript for Web Pages.  Finally, we will look at the notification JavaScript. Entity Form: if (window.jQuery) { (function ($) { if (typeof (entityFormClientVali

Dynamics Set IFrame URL - D365 v8 vs. D365 v9

While doing client work, I came across a problem with setting an IFrame URL dynamically.  The underlying issue was that the sandbox instance is on v8 of Dynamics 365 and production is on v9 of Dynamics 365.  The reason for this was because this client was setup around the time that Microsoft rolled out v9.  Anyways, JavaScript that I wrote to dynamically set the URL of the IFrame wasn't working in the v9 instance.  This was because of changes that Microsoft made to how IFrames are loaded on the form and also changes to JavaScript. Here is my v8 setup: JavaScript runs OnLoad of contact form.  This works because of how IFrames are loaded in v8.  You can also run it on either a tab change (hide / show) or OnReadyStateComplete event of the IFrame.  Depending on your setup you will need to choose which is best for you.  For me in this case it was the OnLoad event. Here is the JavaScript: function OnLoad() { //Get memberid var value = Xrm.Page.data.entity.attri

SCRIBE Software Acquired By TIBCO

On June 6th, 2018 Scribe Software was acquired by TIBCO.  Below is the announcement I and other partners received in an e-mail with links to the press release. "We are pleased to announce that on June 6, Scribe Software was acquired by TIBCO Software. This milestone reflects the increasing strategic importance that Scribe’s product line has with IT organizations and presents great opportunities for Scribe’s partner community. In the short term, there will be no immediate impact to how you conduct business with Scribe. Your sales and support contacts will all remain the same. Over time, we expect that the combination of Scribe’s best-in-class iPaaS with TIBCO’s enterprise product portfolio, which includes messaging, application integration, API management, and analytics offerings, will provide significant capabilities and opportunities for Scribe’s partner community. To learn more about the opportunities that lay ahead, read the  press release ..."