Unsupported Customization Errors when importing a CRM 2011 Solution into CRM 2015+

Posted by dynamicsnick on June 07, 2017
Dynamics 365 / Comments Off on Unsupported Customization Errors when importing a CRM 2011 Solution into CRM 2015+

I had an issue with a vendor recently that I was working with and they no longer supported CRM because they were no longer available. So, in my case the vendor did not happen to have a solution of the product for Dynamics 365. This made it difficult to export and import system customizations into my Dynamics 365 development server for upgrade staging.

I decided to try the version that I did have available (i had luckily archived) for version CRM 2011. However, after attempting to import the solution I was presented with this lovely screen.

Dynamics 365 Error

And there it was… “you can only import solutions with a package version of 8.2 or earlier into this organization“. So another issue that I had was that this was a managed solution.

My first option involved downloading and creating all the missing resource files that came from the solution. I then updated my CRM publisher when adding the resources into a new solution so the files could be named exactly as they appeared in the old solution file. This all was going well until I realized that there were special ribbon options that were required, other relationships for the entities, and more I would need to fabricate in order to solve this issue. At this point, I knew that there had to be an easier way.

Solution

So when solution files are created in Microsoft Dynamics CRM it stamps the version number that is used to determine when the imports are compatible or not. Microsoft provides the following version compatibility chart as well that further tells me what I am doing is most likely unsupported.

You will be able to import most solutions I found by augmenting the solution file and the Import/Export version node of the solution file, and this appears to work for managed and unmanaged solutions as well.

This is how it is done.

1.) Export your solution from CRM 2011 environment (or if you already have a managed package create a copy of it)

2.) Use WinRar – (or another archiving tool) to open the solution package.

3.) Copy the solution.xml file out of solution file. Chances are it will read something like the following below if it is CRM 2011

<ImportExportXml version=”5.0.9690.4150″ minimumversion=”5.0″ languagecode=”1033″ generatedBy=”OnPremise” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”>

4.) Replace the top line of the solution.xml with an updated version like the following below.

<ImportExportXml version=”7.0.0000.4013″ SolutionPackageVersion=”7.0″ languagecode=”1033″ generatedBy=”OnPremise” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”>

5.) Copy the solution.xml file back into the copy of the solution you made.

Since this is not a supported procedure you will want to test this by then uploading the solution into our CRM development or test environment first before moving it into a production solution.

That is all there is to it.

This solution worked for my situation and I was able to import the solution and continue on.

Tags:

Business Process Management in Dynamics CRM 2016

Posted by dynamicsnick on November 24, 2016
CRM 2016, Microsoft Dynamics CRM / Comments Off on Business Process Management in Dynamics CRM 2016

Wouldn’t it be great to have a way to send your users on a journey that guides them through the intricacies of business processes, stages and steps that are required to successfully complete processes efficiently in your organization?

This is particularly important when you need to handle a task exactly the same way such as in a customer service case or for handling sales opportunities in the organization.

This is all possible through CRM using the latest revision of guided processes.

Business Process in CRM

 

Microsoft CRM implements a useful feature called the process bar to visually assist walking users through and outlining the steps that are needed to support each stage of your a process.

Essentially, it is a progress bar that guides your users advancing them through each stage of your defined business process.

It also supports branching which means that if you discover mid-stream a different process needs to be followed you can choose to transition to that process at and pickup where you left off.

If you have CRM 2016 or the CRM Online you should check out this great feature. In CRM 2016 this feature now even spans across not only built-in system entities, but additionally custom created entities as well.

Tags: , ,

Configuring Office Web Apps in SharePoint 2013

Posted by dynamicsnick on October 27, 2016
Office Web Apps, Sharepoint / Comments Off on Configuring Office Web Apps in SharePoint 2013

As you know or will soon learn, Office Web Apps in SharePoint 2013 is no longer a service application that is part of your SharePoint farm.  Instead it is installed as a separate farm, which provides a number of advantages, such as reuse between multiple SharePoint and Exchange farms, a separate patching schedule, etc.  It can be a little confusing at first though, to figure out how to connect an Office Web Apps farm to a SharePoint farm.  What follows here are the installation pre-requisites for Office Web Apps and information about how to connect these farms together.

Prerequisites

 

Office Web Apps does not have a prerequisites installer like SharePoint 2013 does so you may need to install these components separately before you starting installing.

 

  1. Install PowerShell 3.0 (RC1 is the latest version at this time: http://www.microsoft.com/en-us/download/details.aspx?Id=29939)
  2. Install .NET 4.5 (RC is the latest version at this time: http://www.microsoft.com/visualstudio/11/en-us/downloads#net-45). IMPORTANT: If the installer shuts down any of the .NET listeners during installation, you MUST reboot the server prior to installing WAC. Otherwise you will find numerous errors about endpoint not found, not listening, or connection refused in the Office Web Apps application node in the Event Viewer and you will not be able to render any documents.
  3. Install this hotfix: http://www.microsoft.com/download/en/details.aspx?id=27928

 

UPDATE:  I wanted to update with some additional information on this for RTM and Windows Server 2012.  Part of the difficulty in providing this guidance before we ship is that things change.  Here’s the latest experiences when using RTM builds on Windows Server 2012:

  1. You don’t need to do any of the three steps above.
  2. You need to start PowerShell as an administrator.
  3. You need to add the WAC admin module as follows:  import-module “C:\Program Files\Microsoft Office Web Apps\AdminModule\OfficeWebApps\OfficeWebApps.psd1

 

You will need to jump through a couple of hoops on Server 2012 to get all the pre-reqs in place.  You need to:

  1. Install the IIS, .NET 4.x, and the Ink and Handwriting Services (no idea why on that last one)
  2. After all that’s finished you have to go back add additional features to that service:
    1. ASP.NET 4.5”
    2. “.NET Extensibility 4.5”
    3. “ISAPI Extensions”
    4. “ISAPI Filters”
    5. “Server Side Includes”

You can now install Office Web Apps.  Once it’s installed, you need to either create a new Office Web Apps farm, or join your server to an existing farm.  In this case I’m just going to describe how to create a new farm; to get the PowerShell to add a server to a farm just do a get-command *office* in PowerShell.  To create the farm do the following:

 

  1. Open PowerShell by going to Start…Run and typing powershell.
  2. To use HTTPS with WAC (recommended):
    1. Create an SSL certificate that will be used with the fully qualified domain name of the server; make note of the friendly name you use when you create the certificate. You should use IIS to request the certificate to ensure that it gets created in the correct certificate store.
    2. Provision the WAC farm with this PowerShell command: New-OfficeWebAppsFarm -Verbose -InternalUrl https://<machinename> -ExternalUrl https://<fully.qualified.machine.name> -CertificateName <FriendlyNameOfCertificateFromPreviousStep> -ClipartEnabled -TranslationEnable
  3. To use HTTP with WAC (not recommended):
    1. Provision the WAC farm on the WAC server with this PowerShell command: New-OfficeWebAppsFarm -Verbose -InternalURL http://<machinename> -ExternalUrl http://<fully.qualified.machine.name> -AllowHttp -ClipartEnabled –TranslationEnabled

 

Now that your Office Web Apps farm is up and running, you can connect your SharePoint farm.  To do that, login to any server in your SharePoint farm and open the SharePoint PowerShell command window.  Use the following command to connect to the Office Web Apps farm:

 

  1. To use HTTPS with WAC (recommended):
    1. Create the connection to WAC with this PowerShell command: New-SPWOPIBinding -ServerName <fully.qualified.machine.name of WAC server>
  2. To use HTTP with WAC (not recommended; Note – will not work if you did not configure Office Web Apps to support HTTP):
    1. Create the connection from the SharePoint farm to the WAC farm with this PowerShell command: New-SPWOPIBinding -ServerName <NameOfWacServer> -AllowHTTP
    2. Run the following command on the SharePoint server (note there’s no “s” at the end): Set-SPWopiZone internal-http

 

Generally speaking, you should configure Office Web Apps to use HTTPS. The reason for that is that you can only have one WopiZone binding per SharePoint farm, HTTP or HTTPS. If you ever have both HTTP and HTTPS web apps zones, you will need Office Web Apps to be HTTPS. If it’s HTTP only, you will get mixed content warnings when you are in an HTTPS site and you try and render HTTP Office Web Apps. However if you try to render HTTPS Office Web Apps in an HTTP web app zone you will not get any warnings. In addition, since the access token is passed between SharePoint and the Office Web Apps servers it is safer to have the traffic encrypted with SSL so that it cannot be sniffed out and replayed.

UPDATE:  One final note worth making here.  When you create the New-SPWopiBinding to the web apps farm, it will use the server name you provide and expect it to be HTTPS.  That means if you say your ServerName is wac.foo.com, then it will try and contact it at https://wac.foo.com.  If you do not have an SSL certificate with a common name of wac.foo.com bound to the IIS server that the web apps is using, then the New-SPWopiBinding will fail and tell you that it can’t find the server.  There other thing to note is that THIS IS NOT NECESSARILY THE SERVER NAME SHAREPOINT WILL USE TO REQUEST WAC CONTENT!!  The server name it will use is actually contained in a discovery document on the web apps server.  If you navigate to https://wac.foo.com/hosting/discovery then you should get the XML document it uses, and it will show the names it is using for both the internal and external zone (web apps only have two zones, it is not like SharePoint).

 

The reason I bring this up is because what I found is that after I run the New-SPWopiBinding cmdlet on SharePoint, by default it is setting the current WOPI zone as internal-https.  However, I use a fully qualified domain name for my WAC endpoint.  So instead of SharePoint requesting web apps at https://wac.foo.com, it makes the request to https://wac.  The problem then is that your SSL certificate on the web apps servers does not match the request coming from SharePoint, so you will get a random and varying assortment of errors.  The solution to this is to change your WOPI zone in SharePoint with the Set-SPWopiZone cmdlet, i.e. Set-SPWopiZone external-https.  That will make SharePoint use the external name in the discovery document, which should be https://wac.foo.com.  Many thanks to Yanlin for helping me track this down!

Custom Mapping from Quote Product to Order Product

Posted by dynamicsnick on October 17, 2016
CRM 2016 / Comments Off on Custom Mapping from Quote Product to Order Product

So CRM 2016 even the latest release still has some issues with this system mapping and it is easy to move custom attribute fields from one to the other once you know where to look. Usually these mappings are controlled on the relationship, but you will not see this one to get it takes a little trickery to CRM’s Relationships Mappings master.

First you have to find the ID of this relationship which is to find using a simple OData Query.

https://{yourCRM}/{YourORG}/XRMServices/2011/OrganizationData.svc/EntityMapSet?$select=EntityMapId&$filter=SourceEntityName%20eq%20%27quotedetail%27%20and%20TargetEntityName%20eq%20%27salesorderdetail%27

In the first part you are just asking the Odata service to return to you the ID for the system mapping you need. Once you have filled out your crm information and ran it in a browser (use chrome it’s easier) it will return a result of EntityMapId.

entityid

 

You can now append this id returned to the end of the following system mapping link.

https://{YourCRM}/{YourOrg}/Tools/SystemCustomization/Relationships/Mappings/mappingList.aspx?mappingId=

Once you have the link together and paste it in the browser you will get the relationship mapping editor for the options selected.

otherpage

Now you can create the mappings to support your custom entities in CRM.

Tags: ,

CRM Client – Failed Uninstall – what to do next?

Posted by dynamicsnick on September 16, 2016
CRM Outlook Client, Microsoft Dynamics CRM / Comments Off on CRM Client – Failed Uninstall – what to do next?

There are times when uninstalls that are .msi based do not complete fully and when that happens it can be a pain. If you happen to know all the system registry entries, system files, and settings then you could dig through and remove these one at a time.

The easiest solution is to simply use the program install and uninstall troubleshooter from Microsoft as it is designed to help with failed uninstallations or installs.

Here is the link.

https://support.microsoft.com/en-us/help/17588/fix-problems-that-block-programs-from-being-installed-or-removed

 

Tags: ,

Latest Enhancements to Microsoft PowerBI

Posted by dynamicsnick on August 05, 2016
PowerBI / Comments Off on Latest Enhancements to Microsoft PowerBI

Straight From the Microsoft PowerBI Update for July here is the latest updates. Wow…

Report View:

  • Predefined table styles
  • ShapeMap can use custom maps

 

Data Connectivity:

  • New Data Connectors:
    • Amazon Redshift (Import + DirectQuery) (Preview)
    • Impala (Import) (Preview)
  • Improvements to existing data connectors:
    • Support for specifying a Command Timeout via the UX
    • CSV/Text – Support for Fixed-Width delimited files
    • SAP BW connector improvements:

 

Query Editing Improvements:

  • Ability to use R scripts in Query Editor
  • Query Parameters – List Query output as “allowed values” for a parameter
  • Ability to overwrite existing user-defined functions

For a summary of the major updates, you can watch the following video:

Report View

Predefined table styles

A couple of months ago, we introduced configurable styling of the table visual, allowing Desktop users to control many aspects of the table’s look. In this release we are introducing a set of predefined table styles that allow you to quickly choose the look of your table. Once selected, the style will set the needed formatting properties of the table and allow you to fine tune the look by modifying any of the individual properties available.

To select a table style, edit the Format -> Table style properties.

Note that this feature is currently available in Power BI Desktop and will be available on the Power BI service shortly (within a few days).

More details about predefined table styles in the following video:

Shape Map can use custom maps (Preview)

With the addition of custom map usage, Shape Map is enabled with its defining feature.

To use a custom map with Shape Map it must be in the TopoJSON format.  If it is in another format, you can use online tools like Map Shaper to convert your shapefiles or GeoJSON maps to the TopoJSON format.

Once you have a custom TopoJSON map, you can use it with Shape Map.  Simply add the ShapeMap visual to your report, and add some data to the Location and Values buckets.  Then under Format | Shape options, select the Add Map button and then your TopoJSON file.

The map will display the data on your custom map.

If you are having issues mapping your data to the map regions, you can select View Map Keys to see all the region keys the selected map is using to match to the data.

More details about using custom maps with Shape Map in the following video:

Data Connectivity Features

New Data Connectors

We have added two new data connectors in this release: Amazon Redshift and Impala. These two connectors are currently available as Preview and only supported in Power BI Desktop at the moment. Support for PowerBI.com and Enterprise Gateway refresh will come in a future release.

Amazon Redshift (Preview)

This connector provides connectivity to Amazon Redshift in Power BI Desktop, including both Import and DirectQuery connectivity modes, enabling full flexibility in terms of connectivity options for Report Authoring.

In order to try this connector, users have to first enable the Preview feature. This can be done via the Options dialog (File -> Options and Settings -> Options), under the “Preview Features” tab.

After enabling this Preview feature, the Amazon Redshift connector can be found in the “Get Data” dialog, under the “Database” tab.

 

Impala (Preview)

The second new connector this month is the Impala connector. This connector enables users to import data from an Impala cluster. In this release, only Import connectivity mode is supported, but we plan to also enable DirectQuery soon.

In order to try this connector, users have to first enable the Preview feature. This can be done via the Options dialog (File -> Options and Settings -> Options), under the “Preview Features” tab.

After enabling the Preview feature, the Impala connector can be found in the “Get Data” dialog, under the “Database” category.

 

Improvements to existing data connectors

In addition to lighting up new data connectors every month, our team also gives high importance to improve existing connectors based on customer feedback.

This month, we’re improving 4 of our existing connectors: Web, CSV, Text and SAP BW.

 

Web – Support for specifying a Command Timeout via the UX

In this release, we’re enhancing the Web connector to allow users to specify a Command Timeout value from the connector UX dialog. Before this release, this could only be achieved by customizing the underlying M query.

In the Web connector, users can switch between Basic and Advanced modes. In the Advanced mode, users can now optionally specify a Command Timeout value.

 

CSV & Text Connectors – Support for Fixed-Width delimited files

Users can now easily import data from fixed-width delimited CSV and Text files. With this release of Power BI Desktop, users can specify a list of positions to split by in the Table Preview dialog, as part of the Text/CSV import experience.

 

SAP BW Connector Improvements

The SAP BW connector has been available for a few months as a Preview connector. During this period, we have been listening to customers’ feedback and made a number of improvements to the connector. This month we’re making a few additional enhancements to this connector based on your feedback:

  • Support for NetWeaver driver: Before this update, the SAP BW connector required users to install the librfc32.dll from the SAP support portal. Starting with this update, the SAP BW connector will instead rely on the SAP NetWeaver driver. Please note that you will have to ensure that this driver is configured in your machine in order to continue running existing reports, both via Power BI Desktop and the Power BI Enterprise Gateway. The SAP NetWeaver driver can be downloaded from the SAP Support portal, and it is usually deployed as part of the SAP BW Client Tools installation so for many end users this requirement might already be met in their machines.
  • Ability to specify a language when connecting to an SAP BW server: With this release, users can now optionally specify a language code for their SAP BW server when establishing a connection. Before this release, the SAP BW language code was not customizable. If no language code is specified, the Current File locale will be used.
  • Error messages are now localized: Before this release, SAP BW connector error messages were English only. With this release, they’re now localized and will match the Power BI Desktop installation language.

 

Query Editing Improvements

Use R scripts inside the Query Editor

You can now take advantage of R inside the Query Editor to perform data cleansing, advanced data shaping, and analytics in datasets including completion of missing data, predictions, and clustering, just to name a few.

To add an R script to your query processing, select Run R Script from the Query Editor, Transform tab:

In the pop-up you can enter your R script:

You can expect your dataset to be updated with the changes made by the script.

Note that you need to have R installed locally in order to take advantage of this feature. You will also need to change the privacy setting of all data sources to public in order for the script to be performed on those data sources.

Look out for an in-depth blog post on this subject coming soon to this space.

 

Query Parameters – List Query output as “allowed values” for a parameter

One of the areas of feedback about the Query Parameters feature that we introduced a couple of months ago was being able to dynamically calculate the list of “allowed values” for a given parameter based on another query, instead of having to provide a static list of values in the “Manage Parameters” dialog. With this month’s update, customers can link to another query from which the list of Allowed Values for a Query Parameter should be retrieved.

After defining which List Query to use for retrieving the list of allowed values for a parameter, users will get the list of values in the “Edit Parameters” dialog or as part of the “Import Template” experience.

Note that only queries that yield a List are supported for this feature and that this “dynamic list” is only supported in Power BI Desktop consumption scenarios. When providing Query Parameter values in PowerBI.com, users will have to manually input the desired value in a text input field, rather than being able to pick from a list of values.

 

Ability to overwrite existing user-defined functions

Last month, we released a new feature that allows users to create a function based on an existing query. If such query contained any Query Parameters, those parameters would become function parameters. This feature can be accessed as a right-click menu option in the Queries pane within the Query Editor.

This month, we’re making it possible for users to overwrite functions when exporting multiple times from the same query.

That’s all the updates for Power BI Desktop in July. We hope that you find these features useful and continue sending us feedback on how to make Desktop even better.

Tags: ,

Microsoft CRM 2016 SQL error when upgrading Org to Service Pack 1 (2016.01)

Posted by dynamicsnick on July 21, 2016
CRM 2016 / Comments Off on Microsoft CRM 2016 SQL error when upgrading Org to Service Pack 1 (2016.01)

When performing an update today to a development environment i hit the following error when attempting to upgrade the Organization DB. I have a couple on the dev DB in this case one of them would not update.

In the log i found the following error message.

Update Organization with Id=<snipped> failed with Exception:
System.Exception: Error.ActionFailed Microsoft.Crm.Tools.Admin.InstallDatabaseUpdatesAction —> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.Data.SqlClient.SqlException: Cannot drop index ‘cndx_PrimaryKey_OpportunityProduct’ because it enforces the full-text key for table or indexed view ‘OpportunityProductBase’.

 

Apparently, the release is still a bit buggy so i wanted to share this for any other users out there. If you manually drop the indexes before you upgrade the DB in deployment manager it will continue on. It appears to be a sequencing issue with the update wizard. If you are not comfortable working in SQL and CRM i would reccomend filing a support incident. If you are handy with SQL there here is what you do next. Also, but keep in mind that your indexes will be rebuilt which will make it a little slow until they rebuild.

1.) First we need to create a copy of all the indexes in place so that they can be recreated at the end of this process. Do this by running the following query. Export the output of this script and save it in a safe location. Name it recreateindexes.sql or something relevant.

 

declare @catid int
select @catid=fulltext_catalog_id from sys.fulltext_catalogs where name=’CRMFullTextCatalog’
declare c cursor for
select sys.tables.name, sys.fulltext_indexes.unique_index_id from sys.fulltext_indexes inner join sys.tables on sys.fulltext_indexes.object_id = sys.tables.object_id where sys.fulltext_indexes.fulltext_catalog_id=@catid
open c
declare @TableName varchar(200), @UniqueID as integer
fetch next from c into @TableName, @UniqueID
while @@fetch_status = 0
begin
declare d cursor for
select sys.indexes.name, sys.tables.object_id from sys.tables inner join sys.indexes on sys.tables.object_id = sys.indexes.object_id where sys.tables.name=@TableName and sys.indexes.index_id = @UniqueID
open d
declare @KeyIndex varchar(200), @object_id as integer
fetch next from d into @KeyIndex, @object_id
if @@FETCH_STATUS <> 0
begin
Print ‘Error with’ + @TableName
end
while @@fetch_status = 0
begin
BEGIN TRY
Print ‘CREATE FULLTEXT INDEX ON [dbo].’+@TableName+’ KEY INDEX [‘+@KeyIndex+’] on([CRMFullTextCatalog]) WITH (CHANGE_TRACKING AUTO)’
Print ‘GO’
declare e cursor for
select sys.columns.name from sys.columns inner join sys.fulltext_index_columns on sys.columns.object_id=sys.fulltext_index_columns.object_id and sys.columns.column_id=sys.fulltext_index_columns.column_id where sys.columns.object_id=@object_id
open e
declare @ColumnName varchar(200)
fetch next from e into @ColumnName
while @@fetch_status = 0
begin
Print ‘ALTER FULLTEXT INDEX ON [dbo].’+@TableName+’ Add (‘+@ColumnName+’)’
Print ‘GO’
fetch next from e into @ColumnName
end
close e
deallocate e
END TRY
BEGIN CATCH
print ‘Error’ + @KeyIndex
END CATCH
fetch next from d into @KeyIndex, @object_id
end
close d
deallocate d
fetch next from c into @TableName, @UniqueID
end
close c
deallocate c

2.) Only after you have saved the output run the next script below and it will create the output for DROPPING the indexes from your Organization DB.

declare @catid int

select @catid=fulltext_catalog_id from sys.fulltext_catalogs where name=’CRMFullTextCatalog’

declare c cursor for

select sys.tables.name, sys.fulltext_indexes.unique_index_id from sys.fulltext_indexes inner join sys.tables

on sys.fulltext_indexes.object_id = sys.tables.object_id where sys.fulltext_indexes.fulltext_catalog_id=@catid

open c

declare @TableName varchar(200), @UniqueID as integer

fetch next from c into @TableName, @UniqueID

while @@fetch_status = 0

begin

declare d cursor for

select sys.indexes.name, sys.tables.object_id from sys.tables inner join sys.indexes

on sys.tables.object_id = sys.indexes.object_id where sys.tables.name=@TableName and sys.indexes.index_id = @UniqueID

open d

declare @KeyIndex varchar(200), @object_id as integer

fetch next from d into @KeyIndex, @object_id

if @@FETCH_STATUS <> 0

begin

Print ‘Error with’ + @TableName

end

while @@fetch_status = 0

begin

BEGIN TRY

Print ‘DROP FULLTEXT INDEX ON [dbo].’+@TableName+’;’

Print ‘GO’

END TRY

BEGIN CATCH

print ‘Error’ + @KeyIndex

END CATCH

fetch next from d into @KeyIndex, @object_id

end

close d

deallocate d

fetch next from c into @TableName, @UniqueID

end

close c

deallocate c

 

3.) Run the output that is generated against your CRM OrganizationDB and it will drop all the indexes needed.

4.) Now, go back into deployment manager and select to update the organization and it should complete this time.

5.) Once the update completes (it will take a while if you have a large db), the full text indexes back to CRM. You do this
by running the output from the script you created on step 1. The script should be named recreateindexes.sql or something similar.

Tags: ,

Microsoft Dynamics Pricing

Posted by dynamicsnick on May 28, 2016
Microsoft Dynamics CRM / Comments Off on Microsoft Dynamics Pricing

Note this is for commercial pricing for the US market. Other markets and pricing can be located here.

Product Price Term Segment
Microsoft Dynamics CRM Online Additional Storage $9.99 USD / GB / month Commercial
Microsoft Dynamics CRM Online Additional Production Instance $549.00 USD / instance / month Commercial
Microsoft Social Engagement Additional 10k Posts (minimum 10 licenses) $70.00 USD / 10k / month Commercial
Microsoft Dynamics Marketing Sales Collaboration $2.00 USD / user / month Commercial
Microsoft Social Engagement Enterprise $125.00 USD / user / month Commercial
Professional Direct Support for Microsoft Dynamics Marketing $9.00 USD / user / month Commercial
Parature Additional Records $50.00 USD / 500k / month Commercial
Parature Enterprise $125.00 USD / user / month Commercial
Enhanced Support for Microsoft Dynamics CRM Online $5.00 USD / user / month Commercial
Microsoft Dynamics CRM Online Essential $15.00 USD / user / month Commercial
Microsoft Social Engagement Additional 10k Posts $100.00 USD / 10k / month Commercial
Microsoft Dynamics CRM Online Additional Instance $549.00 USD / instance / month Commercial
Dynamics Marketing SMS Dedicated Short Code for US Market $2,000.00 USD / short code / month Commercial
Parature Additional File Storage $20.00 USD / user / month Commercial
Microsoft Dynamics Marketing Additional Storage $2.00 USD / GB / month Commercial
Microsoft Dynamics CRM Online – Portal Add-On $500.00 USD / user / month Commercial
Microsoft Dynamics Marketing Additional Email Marketing Messages $20.00 USD / 10k / month Commercial
Parature Additional Departments $200.00 USD / department / month Commercial
Microsoft Dynamics CRM Online Enterprise $200.00 USD / user / month Commercial
Microsoft Dynamics CRM Online – Field Service User Add-On $35.00 USD / user / month Commercial
Microsoft Dynamics CRM Online Basic $30.00 USD / user / month Commercial
Enhanced Support for Microsoft Social Engagement $5.00 USD / user / month Commercial
Microsoft Dynamics CRM Online – Additional Portal Page Views $50.00 USD / user / month Commercial
Microsoft Dynamics CRM Online Professional Add-On to Office 365 $50.00 USD / user / month Commercial
Microsoft Social Engagement Professional $75.00 USD / user / month Commercial
Microsoft Dynamics Employee Self Service $3.00 USD / user / month Commercial
Professional Direct Support for Microsoft Social Engagement $9.00 USD / user / month Commercial
Dynamics Marketing SMS Dedicated Short Code for Canadian Market $4,000.00 USD / short code / month Commercial
Microsoft Dynamics Marketing Mobile Marketing $200.00 USD / 10k / month Commercial
Professional Direct Support for CRM Online $9.00 USD / user / month Commercial
Microsoft Dynamics Marketing Enterprise $125.00 USD / user / month Commercial
Enhanced Support for Microsoft Dynamics Marketing $5.00 USD / user / month Commercial
Enhanced Support for Parature $5.00 USD / user / month Commercial
Microsoft Dynamics CRM Online Professional $65.00 USD / user / month Commercial
Microsoft Dynamics CRM Online Additional Non-Production Instance $150.00 USD / instance / month Commercial
Parature Additional Page Views $50.00 USD / 500k / month Commercial
Microsoft Dynamics CRM Online Additional Storage $9.99 USD / GB / month Commercial
Professional Direct Support for Parature $9.00 USD / user / month Commercial
Microsoft Social Engagement Additional 10k Posts (minimum 100 licenses) $40.00 USD / 10k / month Commercial

Tags: , , ,

Intellisense in Visual Studio for Microsoft Dynamics CRM 2016

Posted by dynamicsnick on May 18, 2016
CRM 2016, Javascript / Comments Off on Intellisense in Visual Studio for Microsoft Dynamics CRM 2016

If you do much development in CRM and use visual studio for your JS development and deployments you will find yourself missing the native intellisense feature that is so handy to have when using the IDE. However there is a useful solution for those that have also had this issue.

It is an additional .js file that can be added at the beginning of your code that can help with this in Visual Studio. The js library itself is created from the team that created the MSXRMToolkit and can be downloaded at the following location here. http://msxrmtools.com/Xrm.Page/MSXRMTOOLS.Xrm.Page.2016.js

All you need to do is add the file in your visual studio JS file deploy it as a resource and then you can reference it in your other .js files to activate intellisense in your code by dragging it in VS to your js file.

Optionally you can just add the following reference on each of your JS files that you would like to see intellisense in.

/// <reference path=”MSXRMTOOLS.Xrm.Page.2016.js” />

Now you should be able to activate the intellisense options in VS by simply typing in XRM. as shown in the image below.

CRM JS Visual Studio Intellisense Example

 

 

Tags: , ,