Using your Dynamics 365 portal in an iframe

There might be certain scenarios where you want to utilize certain parts of Dynamics 365 portals functionality within other applications. Most often this is where another content management system (CMS) is already in place but you want to enhance its abilities and add new functions that work with your CRM. Instead of writing customizations in that CMS it can be easy to configure your desired functionality with the out of box functionality of Dynamics 365 portals.

With Dynamics 365 portals through you might run into a issue with embedding the site in an iframe. If trying to embedding your portal in an iframe you will end up with a blank frame. Opening up Chrome’s developer tools and view the console you will notice the following error providing a hint as to the issue.

Refused to display 'https://mps155013.microsoftcrmportals.com' in a frame because it set 'X-Frame-Options' to 'SAMEORIGIN'.

X-Frame-Options is part of the HTTP response header and can be used by the web server to control who can display your content directly in an iframe. This is important if you want to prevent any sort of embeds of your site as well as limit it to an allowed list of sites. You can read more about X-Frame-Options on the Morilla Developer Network Documentation.

The following are the X-Frame-Options directive options:

  • DENY – blocks all iframe requests
  • SAMEORIGIN – allows iframe’s from the origin site
  • ALLOW-FROM https://example.com/ – allows iframe’s from the URL

You can manipulate the X-Frame-Options of your Dynamics 365 portal through the site setting HTTP/X-Frame-Options, inserting in the value one of the options above. New portals should include the setting by default in all portals with the default value set to SAMEORIGIN. If you do not have the site setting from an older portal that has upgraded, you can add it but it requires the supporting portal code version (v8.2).

Some other considerations when embedding your portal will also be the display of the page. Most likely the site your embedding into will already have a header with navigation and also a footer, so it might not make sense to include these type of components on the pages your iframe will display.

You can handle this in various ways with the portal, either through simply putting some CSS only on iframe pages that hide elements, keep in mind that the Bootstrap CSS uses the width of your frame and not the parent window so you may be in a mobile layout inside the iframe. Another option is to use the Page Template with the Use Website Header and Footer when using the Web Template type. Leaving this option set to false will only render the contents of the liquid template, it will leave out all portal scaffolding like Bootstrap CSS, and JavaScript libraries. If you need those type of components you will need to add them back through your own references in your web template. The web template option is great for data display type options, if you want to use entity form or list then you will require that portal scaffolding for those components to work.

usewebsiteheaderfooter

There is a hidden rewrite template that does not have a header or footer you can use if your only need is an entity form. Create a new page template with the type Rewrite and set the Rewrite Url to ~/Areas/Portal/Pages/Form.aspx. This page template is used by entity list to display modal dialog forms for entity list create and edit functions. This page template if you look at the v7 code only contains an entity form control and sets the content controls for header and footer to blank, it does not even include the page copy.

norewrite

Based on the functions you want to accomplish and the security you require for the content in your iframe you will need to select the best method for displaying your page.

What’s New in Dynamics 365 portals

A number of the Dynamics 365 application services; Field Service, Project Service and portals, all became generally available this week following the release of Dynamics 365 earlier this month. These all offer a number of improvements and new features from their previous iterations under Dynamics CRM. Previously called CRM portals, now Dynamics 365 portals, has received some significant updates, even some functionality that starts to bring the 3 application services together with Project and Field Service functionality now in some portals. Let’s take a look at some of the largest changes in this release:

  • Multilingual support for a single portal
    Any of the now 43 languages can be configured on a portal and no longer requires a completely separate portal service for each language.  This functionality also significantly differs from how multilingual support was included in the legacy Adxstudio Portals. You will find a new entity, Website Languages that adds an additional layer, this instead of duplicating the entire web site using the old web site copy tool.  The page copy section is no longer directly on the web page information form but now available through a localized content relationship which will display the web page in a new content mode and other content data entities like content snippet or site settings also have new relationships to the website language.

    mlp_webpage
    There are also new liquid extensions to support this functionality within your own templates, website.languages will provide a collection of all the language items, pages.languages is a list of languages for the current page available, and website.selected_language will identity what language the site is currently being shown in.
  • Charts displayed in the portal
    You can now embed your CRM/Dynamics 365 charts directly on the web with a new liquid extension.  For an example of charts, if you install the latest partner portal there is a new web template called “Partner Dashboard” that provides an example of embedding multiple charts, entity lists and other components on a single page to give a rich interface to portal users. The liquid extension makes it very easy to add a chart anywhere in a page, all you need is the chart ID and view ID the chart should use for its data source.

    {% chart id:"chart-guid-without-braces" viewid:"view-guid-without-braces" %}
    
    <!-- Est. Revenue by Est. Close Date (Day) - Opportunities Closing Next Month --> 
    {% chart id:"EB02E9AA-5580-E611-80D8-00155DFE75F9" viewid:"00000000-0000-0000-00AA-000010003002" %}
    

    portalcharts

  • Content Access Level Security for Knowledge Management Articles
    Content Access Level or CAL is a feature that has been added to allow for securing access to knowledge articles to different groups of users. In Dynamics 365 with a portal installed you will find some sample CALs but you can also define your own and associate them to contacts and articles. Article content will be secured regardless of how you try accessing the content, either browsing via navigation elements, direct URL or via the Portal Search, all will respect the security rules defined by the CAL.
  • Project Service and Field Service Portal Extensions
    If you provision a new Partner Portal and have either Project Service or Field Service installed you will see some new options available that allow you to enable portal functionality for these components, there are also new actions if you have an existing portal to install the new portal extensions.

    provision_psaThese extensions bring some components to the portal, with PSA your able to view customer and partner related projects or resources. With Partner Field Service extension you can see related field service agreements, assets, service requests, and work orders.
  • Partner Portal Improvements
    There are a number of improvements and new functionality added to the popular partner portal including a new partner onboarding/application, multi-partner collaboration, and also deal registration.

These are all great improvements for this release and continue to look forward to further updates with the monthly updates to Portal Service in the new year. If you want to check out these features and more you can try the latest version yourself by requesting a trial.

For more information about what’s new for Field Service and Project Service a breakdown is available on the What’s New for Dynamics 365 Help and Training site.

Note: This post also appears on Adoxio Business Solutions Team Blog.

Adxstudio Portals v7.0.0023 Released

A new version of Adxstudio Portals has just been released on the Adxstudio Community site. You can head over to download the latest version, 7.0.0023 here.

This version has a number of much needed fixes to bugs that were introduced in v7.0.0022. One in particular that was keeping a lot of implementations away from 7.0.0022 was the anonymous web forms bug. From the release notes posted they look to have addressed this and a number of other fixes.

Another major addition in this release is the web notifications can now be configured directly in CRM for what entities will cause a notification to the portal. The default in previous releases was all entities unless you manipulated this through the plugin registration tool. There is now a Web Notifications Entities that the web notification plugin will use to determine whether to send the message or not. This should be a huge boost to portal performance but now be-aware to add your new custom entities to this list if you want that data also invalidated on the portal. You can read more about this configuration here.

This release unfortunately does not fix the compatibility of Adxstudio v7 and Dynamics 365 but this new release is still very welcome with all the improvements and new cache invalidation functionality.

Update 12/1/2016: Andrew Chan from Adoxio –
Please be aware that a “settings.xml” file is packaged with the sample project under the App_Data folder. Please remove this file when you spin up a new project. Without doing so, this file will cause the Portals to try and connect to an already configured CRM organization that isn’t available, and it will ignore a CRM specified in the connection string in web.config.

Note: This post also appears on Adoxio Business Solutions Team Blog.

Dynamics 365 and Adxstudio Portals Compatibility

Update 2/1/2017:
Microsoft has release CRM SDK 6.1.2 which fixes compatibility between Adxstudio Portals v7 and Dynamics 365! Read more here.

With all the changes in Dynamics 365 there are updates in the SDK and service that now make Adxstudio Portal v7.x incompatible. Outlined below are some of the issues you may run into, with some temporary workarounds if you want use Dynamics 365, and the potential pitfalls of these current solutions.  As a result of the current status of support with Dynamics 365, it would be recommended that if you have an Adxstudio Portals v7.x implementation using CRM Online that you currently do not upgrade past CRM 2016 Update 1.

Update 12/27/2016:
It looks like a fix is going to be coming soon! Posted over at the Dynamics 365 Team Blog about SDK backwards compatibility a new CRM 2013 SDK version that supports the new authentication will be released as SDK v6.1.2. With this updated SDK version you would be able to swap the reference DLLs in Adxstudio Portals v7 without the negative impact to functionality that switching to v8.2 SDK has. No date was provided for this update, but we may also see v7.0.0024 released with this fix in the new year.

Dynamics 365 SDK Backwards Compatibility

One of the changes that is causing some issues is that the ACS endpoint is no longer being provisioned on online instances.  This started with some CRM 2016 Update 1 instances but now seems to be rolling out more broadly.  You might receive the following error when attempting to have your portal connect to the CRM.

ACS10002: An error occurred while processing the SOAP body. ACS50000: There was an error issuing a token. ACS50001: Relying party with identifier ‘https://instancename.crm.dynamics.com/’

Some instances of this could be resolved by changing the instance URL which would potentially cause the ACS endpoint to be rebuilt, but not always.  You could also log a ticket with Microsoft Support for them to restore the ACS endpoint to your instance.

Adxstudio Portals v7.x ships as a solution compatible with CRM 2013, 2015, and 2016.  As such it ships with the CRM 2013 SDK DLLs (v6.0 SDK).  With the release of Dynamics 365 and SDK v8.2 the CRM 2013 SDK DLLs are no longer compatible, and you actually need to upgrade to the v8.1 SDK DLLs to connect with a Dynamics 365 instance.  If you do try to connect Adxstudio Portals with its default CRM SDK 6.0 DLLs then you would likely see the following error message:

The Organization Service URL is invalid. Metadata contains a reference that cannot be resolved: 'https://instancename.crm.dynamics.com/XRMServices/2011/Organization.svc?wsdl=wsdl0'. There is an error in XML document (1, 1298). The maximum nametable character count quota (16384) has been exceeded while reading XML data. The nametable is a data structure used to store strings encountered during XML processing - long XML documents with non-repeating element names, attribute names and attribute values may trigger this quota. This quota may be increased by changing the MaxNameTableCharCount property on the XmlDictionaryReaderQuotas object used when creating the XML reader. Line 1, position 1298.

This can be solved by replacing both the Microsoft.Xrm.Sdk.dll and the Microsoft.Crm.Sdk.Proxy.dll with the versions from the v8.1 SDK, changing the MasterPortal project to .NET Framework 4.5.2 and adding the following dependent assembly references.

<dependentAssembly>
  <assemblyIdentity name="Microsoft.Xrm.Sdk" publicKeyToken="31bf3856ad364e35" culture="neutral"/>
  <bindingRedirect oldVersion="0.0.0.0-8.0.0.0" newVersion="8.0.0.0"/>
</dependentAssembly>
<dependentAssembly>
  <assemblyIdentity name="Microsoft.Crm.Sdk.Proxy" publicKeyToken="31bf3856ad364e35" culture="neutral"/>
  <bindingRedirect oldVersion="0.0.0.0-8.0.0.0" newVersion="8.0.0.0"/>
</dependentAssembly>

However while this will solve your connection issue it will come with unknown issues to other Adxstudio components like Entity List and the portals front-side editor. The change in SDK version does have impact on the portal functions due to the differences between SDK 6.0 (CRM 2013) and SDK 8.1 (CRM 2016 Update 1) and the dependencies the portal components have.

At this time it would probably be recommended if you have a Adxstudio Portals v7.x implementation using CRM Online that you do not upgrade past CRM 2016 Update 1. If you run into the ACS endpoint error explained above then open a support ticket with Microsoft Support and request that the ACS endpoint be restored. If you have already been upgraded, or want to use Dynamics 365 and still need Adxstudio Portals v7, then your best option is to do the DLL upgrade and try to work around the current issues with the reference change.

Note if you start a trial or demo with the intent on showing Adxstudio Portals you can change to a previous version with the following guide.

Microsoft has been notified and aware of the issue.  We are working with them to see what resolution options are available.  As more information on a potential update to resolve these issue becomes available from Microsoft I will update this post. Below is currently a running list of known issues using SDK 8.1 with Adxstudio Portals v7.0.0022, this is in no way a complete comprehensive list.

  • Entity List – grid configuration Edit action – will not appear on entity list rendering for Target Types ‘Web Page’ and ‘Url’, if using Target Type ‘Entity Form’ will result in error:
    Cannot create and populate list type Microsoft.Xrm.Sdk.KeyAttributeCollection. Path 'EditActionLink.EntityForm.KeyAttributes', line 1, position 2877.
  • Entity List – grid configuration Details action – will cause error if using Target Type ‘Entity Form’ as indicated above
  • Front-side editor – ‘Object reference not set to an instance of an object’ when Creating a new web page, or editing a page, or editing a snippet, or modifying a web link set.

If you discover other issues please let me know through comments, Twitter, email or however else and I will update this listing.

Note: This post also appears on Adoxio Business Solutions Team Blog.

Change your Dynamics 365 Trial to a Previous Version

When you create a new trial of Dynamics 365 it will always come as the latest available copy of CRM or now Dynamics 365. Often when a new version is released the trials are the first to get access to the new build so that it can easily be showcased. With every new version there will be incompatibilities with 3rd party or legacy components due to changes in the SDK or functionality within the CRM interface. For these reasons you may want to have a previous version for your CRM trial so you can still showcase that functionality that has not been updated for the latest release.

With the CRM Online/Dynamics 365 Administration Center you can administer trial instances to edit their URL or even reset them to an earlier version.

  1. With your trial account login to https://portal.office.com.
  2. On the tile selection, select the Admin tile.
  3. If you are prompted to enter a backup email or phone number you can simply cancel this screen and it will return you to the admin center.
  4. On the left hand navigation, select Admin Centers and CRM or Dynamics 365.
  5. You should now be at the CRM Online/Dynamics 365 Administration Center where it lists your trial instance. Highlight your instance and select Edit.
    d365admin
  6. To be able to reset your instance to an previous release we need to put it in Sandbox mode, from the Instance Type drop down, select Sandbox, and then click Next, and Save.
    instancetype
  7. You should be returned the Administration Center instances and your trial instance should now show as a Sandbox type, and you should have a reset button when it is selected. Select Reset.
    d365admin-reset
  8. On the reset instance screen, you have a target version dialog where you can select the version of CRM you want your instance to be. Select your desired version.
    targetversion
  9. You can then select your desired scenario, if you just want a blank CRM then select none of these. You can also change your CRM URL if you wish. Note this will not change your tenant name (tenantname.onmicrosoft.com).
  10. Select the reset and then carefully read the prompt. This process will delete any existing and customizations currently in the instance. Once ready, confirm yes in the dialog.

You will then have to wait 10 – 15 minutes for the instance to reset to the target version but once done you can navigate to your previous version of CRM and perform whatever tasks you needed to.