Unsupported Customizations in CRM 2015

Posted by on December 19, 2014 in   |  Microsoft Dynamics CRM,   |  Microsoft Dynamics CRM 2015,   |  Microsoft Dynamics CRM Online  |  commentsComments (0)

Microsoft has been rolling out CRM 2015 for Online organizations (On-prem download can be found here) but before you perform the update you will want to review the new list of unsupported customizations in 2015 to see if you are currently using any of them.

Earlier in the year, in the 2013 SDK, Microsoft provided a list of things that will be changing in the next release which can also be found here in the MSDN.  Only 3 functions are being removed, getServerUrl (use getClientUrl), isOutlookClient (use client.getClient) and isOutlookClientOnline (use client.getClientState).  The Xrm.Page.ui.getFormType call will no longer return 5 for Quick Create and 11 for Read Optimized as those types of forms were removed/deprecated in earlier releases.  Also be sure that your customizations are no longer using the old 2007 endpoint as it is removed in CRM 2015.  To help detect if you are using the 2007 endpoint, you can run the Legacy Feature Check tool against your organizations.

Lastly, there have been some changes to the web application requirements for CRM 2015.  Support for IE8 and IE9 has been removed with the new version.  See below for a list of all the supported browsers:

  • Internet Explorer 10
  • Internet Explorer 11
  • Mozilla Firefox (latest publicly released version) running on Windows 8.1 or Windows 8, or Windows 7
  • Google Chrome (latest publicly released version) running on Windows 8.1 or Windows 8, or Windows 7, or Google Nexus 10 tablet
  • Apple Safari (latest publicly released version) running on Mac OS X 10.8 (Mountain Lion), 10.9 (Mavericks), or Apple iPad

And the supported versions of Microsoft Office:

  • Microsoft Office 365
  • Microsoft Office 2010
  • Microsoft Office 2013

As always be sure to perform the upgrade first in a development or sandbox org to verify that your customizations are still functioning post-upgrade before upgrading your production environment.

Poodle and your CRM

Posted by on December 2, 2014 in   |  Microsoft Dynamics CRM,   |  Microsoft Dynamics CRM 2011,   |  Microsoft Dynamics CRM 2013,   |  Microsoft Dynamics CRM 2015,   |  Microsoft Dynamics CRM Online,   |  Salesforce.com  |  commentsComments (0)

Today I am co-blogging with Blake Scarlavai, Development Principal and Microsoft Dynamics blogger at Sonoma Partners.

Nathen:

Recently a vulnerability in SSL 3.0 known as “Poodle” gained some significant attention, with many companies responding in various ways to ensure their customers’ data is protected. It can be confusing to keep track of what companies are doing what, and what is expected of you as a customer to ensure you are not vulnerable. Below are the summaries of the responses that Salesforce and Microsoft have taken.

Salesforce’s Response

Salesforce is in the process of disabling SSL 3.0 on their platform. By the end of December, you will no longer be able to use SSL 3.0 visit Salesforce’s platform. For the most part, we don’t expect this to affect our clients as the browsers which needed SSL 3.0 still enabled (IE 6 mainly) are already not supported by Salesforce. You can get the full list of the disable schedule and more information about the changes on Salesforce’s help page.

Blake:

Microsoft’s Response

Microsoft is in the process of remediating their online services for the SSL 3.0 vulnerability.  Below is a time table for each of the CRM services:

Service

SSL v3.0 Mitigation Status

Microsoft Dynamics  CRM Online

7-Dec

Microsoft Dynamics Marketing

7-Dec

Microsoft Social Listening

Completed

Parature for Microsoft Dynamics

Completed

Microsoft Dynamics Lifecycle Services

7-Dec

Online Services for Microsoft Dynamics

7-Dec

 

Microsoft also recommends disabling SSL 3.0 in your browser.  The following resources can be used for your respective browser:

For more information on Microsoft’s response, click here.

Dynamics CRM 2015 is Released!

Posted by on December 1, 2014 in   |  Microsoft Dynamics CRM,   |  Microsoft Dynamics CRM 2015,   |  Microsoft Dynamics CRM Online  |  commentsComments (0)

The much anticipated release of Dynamics CRM 2015 is here!  CRM 2015 is now available for download for on-premise.  CRM Online trials are going live with CRM 2015 as well, so head here to signup.

Curious to find out what is new in CRM 2015?  Head here to the Customer Center to see a list of new features in 2015.  In preparation for the release, we have also been covering the new features in detail:

Hit us up in the comments and let us know what you think of CRM 2015 as well as any topic you would like covered further!

Dynamics CRM 2015 Sales Module Enhancements

Posted by on December 1, 2014 in   |  Microsoft Dynamics CRM,   |  Microsoft Dynamics CRM 2015,   |  Microsoft Dynamics CRM Online  |  commentsComments (1)

Microsoft recently announced new features coming out with their next version of Microsoft Dynamics CRM 2015 (previously code named Vega).  Check out the Dynamics CRM 2015 Release Preview Guide to see what features are coming with 2015. 

Next up for our review are the changes being made to the Sales Module.  The following list of enhancements are being made with CRM 2015 and we’ll dive into a few of them a little bit deeper:

  • Product Bundles
  • Cross Sell / Up Sell (via relationships between products)
  • Product Families
  • Territory Specific Default Price List
  • Import/Export Settings via the Configuration Migration Tool provided with Leo
  • Families/Products/Bundles all show up in one grid
  • Clone Families/Products/Bundles (field values and all current product property values – including overridden values).
  • Product Form Preview (displays the product properties so you can preview how it’d look when selling the products)
  • New System Settings Configuration Options
  • Override default pricing engine via code/SDK

Now lets dive a bit deeper into some of these features.

Bundles

If you’ve used Product Kits in the past, you’ll be familiar with Product Bundles.  Bundles are an enhanced version of Product Kits (e.g., you cannot view Kit Items when selling a Kit, but you can with a Bundle – see the Opportunity screenshot below).  Product Kits will not be going away with CRM 2015, but instead Bundles will be an additional option users can use along with Kits.

Within a Bundle you can specify what Products are mandatory or not when selling the Bundle.  They can also be tied to Product Families (more information below) but are not required to be.  Finally, Products within Bundles have Properties that can be edited (e.g., what is the default value, is the property editable when being sold, etc.).

image

When adding the Bundle to an Opportunity, Quote, or Order, you’ll see the Bundle with the individual Products indented underneath.  You‘ll also have the availability to edit the properties of the Products in that bundle for the specific Opportunity, Quote, or Order you’re working with.

image

Cross Sell and Up Sell

As stated above, using a relationship between Products, you can define Cross Sell and Up Sell products.  This Product Relationships area is a sub-grid directly on the Product form.

image 

When on an Opportunity, Quote or Order selling products, there will be a Suggestions Link that when clicked, will show the Cross Sell and Up Sell products that an administrator has defined for your organization.  The user can click on Pick and then Add to List to add the suggested product to their opportunity immediately.

image

Product Families

Product Families are another way to group products and create product hierarchies.  The Child Products in a Product Family inherit the properties of the Product Family when they’re added to the Product Family, but can be overridden.  Then, when adding the Product to an Opportunity, some of these properties can be modified by the Sales Person, while others may not be (defined in the Settings of the Product Family setup).  The properties can be Read Only, Required, or Hidden.

Product Families are similar to Bundles, but the user cannot add a Product Family to an Opportunity, Quote, or Order like they can with Bundles.  Instead, Product Families are used for administration of Products themselves.

image 

New System Settings Configuration Options:

There are a handful of new System Setting Configuration Options coming with CRM 2015 that should be called out separately.  The following settings can be configured per CRM organization:

  • Indicate if the Default Price List is set via an inbuilt rule.  If this is set to yes, then the default price list will be selected for an opportunity based on the default price lists defined for territories.
  • Max # of Products in a Bundle
  • Use system pricing calculation (override default pricing) – customers can use the SDK to have a custom pricing engine built in
  • Discount calculation method:  Per Unit (new option) or Line Item (previous option)
  • Max # of Properties for a Product/Bundle

image

Some great new additions are being added to 2015 as you can see from above.  However, with these new enhancements, there are still a few limitations you should be aware of:

  • You cannot have bundles of bundles (only products are allowed to be added to bundles)
  • Only active / retired products can be imported/exported via the configuration migration tool

Dynamics CRM 2015 SLA Enhancements

Posted by on November 3, 2014 in   |  Microsoft Dynamics CRM,   |  Microsoft Dynamics CRM 2013,   |  Microsoft Dynamics CRM 2015,   |  Microsoft Dynamics CRM Online  |  commentsComments (1)

Microsoft recently announced new features coming out with their next version of Microsoft Dynamics CRM 2015 (previously code named Vega).  Check out the Dynamics CRM 2015 Release Preview Guide to see what features are coming with 2015. 

Next up for our review are the SLA enhancements being made. Pre-CRM 2015, users could take actions if First Response By and Case Resolved By aren’t met.  CRM could also be setup to send warnings if First Response By and Case Resolved By are approaching.

With 2015, a few new enhancements have been made to make the SLA experience a bit more rich.

Automatically Pause/Resume the SLA time Calculation:

Now with CRM 2015, administrators can setup specific Active Case Status values that will automatically pause the SLA timer if the Case is moved into one of the statuses selected.  When the Case is moved out of that status, the timer will resume and continue.  This is configured from Settings –> Service Management –> Service Configuration Settings.

In the example below, if a Case is moved into On Hold or Waiting for Details, the SLA timer will pause (and this will reflect on the Case form).  When the Case is moved back to In Progress or Researching, the SLA timer will continue where it left off.  This functionality is only available with Enhanced SLAs (described in more detail in the next section).

image

image

The On Hold time is tracked per Case record so you can get a glimpse of how long a case has been on hold to follow up and provide better service to your customers.

There may be scenarios where you don’t want your KPIs to be paused, and this can be turned off at the SLA level.  Therefore even though the Case moves to one of the statuses to pause the timer, cases using those SLAs will continue to count down and will not be paused.

Success Actions:

Success actions are new with 2015 and are only available for Enhanced SLAs (described below).  The Success Action can be defined by an administrator, and indicates a set of actions that will be executed whenever the success criteria of a Service KPI is met before the failure time.

image

Enhanced versus Standard SLA:

In Spring 2014, the SLA functionality that was delivered with Leo was Standard SLA functionality.  Now with 2015, you have the ability to define an SLA as Enhanced.

With the Standard SLAs delivered with Leo, you cannot use the new pause/resume functionality of the timer, and you cannot define Success Actions.  Standard SLAs cannot be converted to Enhanced SLAs.

Also, with Standard SLAs, all data is tracked on the individual case record (First Response By, Resolve By, etc.).  With Enhanced SLAs, this information is all tracked on a related SLA KPI Instance records, and quick view forms are used to show specific information directly on the case (e.g., the First Response In and Resolve In timer controls below).

image

If you wanted to create additional KPIs that your business tracks in addition to First Response By and Resolve By, you can do this by creating new SLA KPI relationships to the Case.  Doing so will automatically allow you to create SLA Items against your SLA, and define the Warning / Failure / Success criteria and actions for the new KPI.

With the new SLA KPI Instance records, you can create charts and dashboards to be able to quickly get counts of cases based on the KPI Status, and have a better understanding of how your service department is performing at a high level.

image

Dynamics CRM and Chrome v38 Lookup Issue Fixed!

Posted by on October 29, 2014 in   |  Microsoft Dynamics CRM 2011,   |  Microsoft Dynamics CRM 2013,   |  Microsoft Dynamics CRM Online  |  commentsComments (0)

You may have heard about an issue with Lookups not working correctly with a recent version of Chrome (v38).  Microsoft documented the issue here in a KB article earlier this month.

Last week we noticed that in a new CRM Online trial org with a version of (6.1.1.1621) (DB 6.1.1.1610), the Chrome v38 Lookup issue was resolved so it seems that Microsoft was working on a patch.  Today though we have noticed that with the latest version of Chrome (v38.0.2125.111) the Lookup issue is fixed across the board in CRM Online, CRM 2013 On-prem and CRM 2011 On-prem. 

So if you or your users were stuck on v38 of Chrome then be sure to go to Settings –> About and make sure you’re updated to the latest version to fix the Lookup issues.

image

 

To check your CRM Online version, click the Gear icon at the top right and then click About.

image

 

image

CRM 2013 Navigation: Easily Find the Tile You Are Looking For

Posted by on October 28, 2014 in   |  Microsoft Dynamics CRM 2013,   |  Microsoft Dynamics CRM Online  |  commentsComments (0)

One of the biggest pain points in CRM 2013 for an organization with a lot of custom entities, is the navigation.  The user can only see a few navigation tiles per Site Map area depending on their resolution.  This requires the user to scroll horizontally to find the desired tile.  Being able to use the mouse wheel to easily scroll through the list of tiles is definitely nice but sometimes, with a lot of tiles, it is easy to miss the one you are looking for. 

Thankfully we are here to help ease your pain!  Follow the steps below in any browser for a quick, easy, and native way to find the tile you are looking for.

First, click on the main area that your desired tile is in, such as “Sales”.

image

Then hit CTRL + F to use the browser’s search function.

image 

Then type in the display name of the tile you are looking for such as “quick campaigns”.

image

And there you have it!  The browser finds the text of the tile and takes you right there so you can easily click on it and navigate to that Site Map area.

Dynamics CRM 2015: Tablet Client (MoCA) Enhancements

Posted by on October 22, 2014 in   |  Enterprise Mobility,   |  Microsoft Dynamics CRM,   |  Microsoft Dynamics CRM 2015,   |  Microsoft Dynamics CRM Online  |  commentsComments (0)

Microsoft recently announced new features coming out with their next version of Microsoft Dynamics CRM 2015 (previously code named Vega).  Check out the Dynamics CRM 2015 Release Preview Guide to see what features are coming with 2015.

Next up for our review is reviewing the changes being made to the Mobile Client Application (MoCA).  The first version of MoCA filled a much needed gap to have a native tablet application, but with the improvements below, it’s clear Microsoft see’s mobile as the direction they want to continue to head as they make investments in improving the product.

The following improvements were made with CRM 2015:

Offline Drafts:

  • Users will now have the ability to create and update records while offline.
  • The create/edit mobile experience will use the Quick Create Form defined for the entity
  • A Draft button will appear in the sitemap while offline, taking the user to the Draft Page (+ icon that appears on lists will do the same)
  • The Draft Page will display a count of draft records on the Site Map
  • Users can discard or update drafts while offline
  • Drafts are deleted when the user signs out of MoCA for security reasons (warning displayed first)
  • No lookups / party list support while offline:  However, there’s a workaround to populate lookups while offline by starting at the parent entity and creating a child record from the parent (e.g., creating an Opportunity from a Contact defaults the Contact lookup for the new Opportunity)

You can see from the screenshots below that I have the ability to create records offline (in this instance a Lead), and see a count of how many draft records (creates/updates) that have yet to be uploaded to the CRM server.

If I click on the Draft Records link from the Site Map, I’ll see a list of all the records that have changes that have yet to be uploaded and if I wanted to, I can make further changes to them from this list.

imageimage

image

It’s important to note that with the Offline Drafts, users can only modify records that they created offline.  Users will still be unable to go to a record that they had previously viewed while online, and modify that record while offline.

Also, when the user goes online, they will have to save the Draft records manually (they’ll no longer appear on the draft page).  This isn’t an automatic action that’s taken when a user reconnects online

Mobile Analytics:

Microsoft now allows you to have any and as many dashboards on your tablet (system or personal).  Previously you were able to just have the one “Sales Dashboard” on the Tablet Client, but now Microsoft allows administrators to configure multiple. 

A new “Enable For Tablets” checkbox has been added to dashboards to allow it to show up in MoCA (this field is solution aware and can be toggled via the SDK).

image

There’s a new “Dashboards” Site Map entry that you’ll notice when clicking around the Tablet Client.  Also, the default dashboard users see when initially logging onto the tablet client (prior to personalizing their experience) is defined and configurable by the Site Map XML.

image

When on a Dashboard, users can:

  • Set as Home:  when users click the Home icon, this dashboard will show
  • Pin to Win 8 Start
  • Pin to Home:  you can pin Dashboards to your Home Dashboard similar to how you pin records – this means you could have a Home Dashboard be one dashboard, and have other dashboards pinned on it for easy access.
  • Select Dashboard to select a different Dashboard

image

image

image

With all these changes, there are few other notes that users should be aware of regarding the Tablet Client:

  • There are no storage limitations (the same limitations will apply to MoCA that apply to the device)
  • All improvements in 2015 / Vega will work on Win 8, Android, and iPad devices (except the “Pin to Start” will be Win 8 devices only)
  • Plugins are still not supported on the device, but when data hits the server they’ll run (no offline plugins)

Dynamics CRM 2015 Hierarchical Security

Posted by on October 1, 2014 in   |  Microsoft Dynamics CRM,   |  Microsoft Dynamics CRM 2015,   |  Microsoft Dynamics CRM Online  |  commentsComments (0)

Microsoft recently announced new features coming out with their next version of Microsoft Dynamics CRM 2015 (previously code named Vega).  Check out the Dynamics CRM 2015 Release Preview Guide to see what features are coming with 2015. 

Next up for our review are the changes being made to the security model.  Note that the functionality below are simply additions to the security model.  The previous security of business units, access teams, ownership teams, security roles, etc. will remain in place.

Field Level Security Improvements:

First off we’ll briefly discuss some changes being made for Field Level Security (FLS).  FLS will now be available to work off of System Fields.  Previously this only was available for Custom Fields

FLS also has extended for additional attribute types such as address fields (out of the box only) and email address fields (custom or out of the box fields).

Now lets review the the new major change to security that’s coming in CRM 2015, the Hierarchical Security Modeling.

Hierarchical Security Modeling

With CRM 2015, Microsoft introduces a new version of security they label Hierarchical Security Modeling.  With this security modeling, granular record level access can be granted for an organization without having to create and manage business units.

With the introduction of hierarchical security modeling, Microsoft has moved the Security functionality to its own area of CRM.  You can now get to everything security related by going to Settings –> Security (previously this was in the Administration section).

image

You’ll notice a new Hierarchy Security link on this page as well as a Positions link.  If you click on it you’ll notice the following options:

  • Enable Hierarchy Modeling:  Let’s you turn this on or off globally in your organization
  • Select Hierarchy Modeling:  You can set this to either Manager or Position (more on these options below)
  • Hierarchy Depth:  This indicates how many levels up the hierarchy chain does the read permissions get granted to.  More on this below especially regarding performance.
  • Selected Entities:  This is where you’d select entities that you want the to EXCLUDE in the hierarchy security model.

image

Manager Hierarchy uses the existing Manager field on the System User record.  However, with this hierarchical model, you’re required to be in the same Business Unit hierarchy for it to apply successfully.  This is why the Position Hierarchy Model was built which we’ll describe below.  A good Use Case for the manager model is if a manager needs to take actions upon records their reports have access (for example the report goes on vacation)

Position Hierarchy on the other hand allows you to go across business units.  CRM Administrators can and add users to any given position to be included in that position.  A good Use Case for the position model is organizations that have a “Sales Team” and “Sales Management” team that span across business units yet these positions should have access to subordinate records.

As stated earlier, Position Hierarchy can be configured where an Administrator can define Positions, define the Parent Positions, and also add users to Positions so that the Position Hierarchy security method is executed to your specific business needs.

image

It is strongly recommended that Hierarchical Security be used with the other security tools (e.g., security roles, teams, business units, etc.).  The Hierarchical Security model does grant additional permissions based on users, managers, and positions:

  • Read Access:  Propagates up the chain to a specific configurable level (as shown above in the Settings screenshot
  • Write, Update, Append, Append To: This is granted just to the direct parent of the user/positions

There are also some performance considerations to keep in mind when enabling hierarchy security:

  • Use with other security methods (e.g., security roles, business units, teams, etc.) for more complex scenarios
  • Target 4 levels of hierarchy (1 manager with 3 reports, and 100-200 potential users underneath)
  • Performance is tied to the # of users (not the depth) in the parent’s chain:
    • 1 manager with 4 reports and 1 level in the chain, is the same as
    • 1 manager with 1 report and 5 levels in the chain

With all the security methods provided out of the box by Dynamics CRM now with 2015, I can see some organizations with very complex security requirements being easily achievable using native security methods.

Dynamics CRM 2015 Calculated and Rollup Fields

Posted by on September 26, 2014 in   |  Microsoft Dynamics CRM,   |  Microsoft Dynamics CRM 2015,   |  Microsoft Dynamics CRM Online  |  commentsComments (6)

Microsoft recently announced new features coming out with their next version of Microsoft Dynamics CRM 2015 (previously code named Vega).  Check out the Dynamics CRM 2015 Release Preview Guide to see what features are coming with 2015. 

Prior to Dynamics CRM 2015, in order to perform calculations / rollups, you had to write code in order to do so which meant you had to invest in a developer which isn’t always possible for our customers.  However, with Dynamics CRM 2015, Microsoft has provided the ability for power users / administrators to create and update calculated fields and rollup fields using the CRM web client and customizations area within Settings.  Below we’ll discuss both Calculated Fields and Rollup Fields in more detail, their uses, and current limitations.

When you’re defining your custom fields, at that time you can indicate if the field will be Simple (pre 2015 calculated fields that we’re all used to) Calculated (new for 2015), or Rollup (new for 2015).  Based on the Data Type of the field will determine what values you can select in the Field Type drop down.  This value can only be set upon field creation.  Once the field is created the Simple/Calculated/Rollup flag may not be updated.

Calculated Fields:

You can create a calculated field for any data type, except Multiple Line of Text, Image, or Lookup fields.  When you create the field, an “Edit” link will appear next to the Field Type.

 image

When you click the Edit button, you’ll be taken into the editor where you can edit your calculations.  When you’re editing the calculation, you can use any field from the current entity, or any N:1 entity in your calculation or conditions.  You can also use AND and OR in your conditions to make more complex conditions.  However there is a limitation to this functionality (see limitations section below).

The UI of the edit page is similar to the modern UI when modifying Business Rules or Business Processes.  So your admins will have a consistent look and feel amongst all of these customization tools.

image

The calculation designer also supports intellisense so when you’re editing the calculation, you’ll see hints of what you can select from and what you need to enter as you type.

image

These fields are stored in the database and can be used and displayed like any other physical field in views / reports / charts / forms / Field Level Security.

When modifying fields that affect the calculation, the calculated field is calculated synchronously after a Save is performed.  The the end user will get immediate feedback that data has changed after the form is refreshed.

Rollup Fields:

Rollup fields are used to perform record level aggregation from related records.  For example, if you wanted to have a field on the Account that rolled up the Estimated Revenue for all Open Opportunities related to the Account, you could easily identify at the Account level what the Total Open Revenue was and then know what Accounts you should focus most of your time and energy on.

Similar to Calculated Fields, Rollup Fields do not support all data types.  Rollup fields are only available for Whole Number, Decimal Number, Date & Time, and Currency fields.  The table below shows how you can rollup child data using the rollup fields for the different data types.

Data Type

COUNT

MAX

MIN

SUM

Whole Number

x

 

 

 

Decimal

x

x

x

x

Currency

 

x

x

x

Date & Time

 

x

x

 

Similar to Calculated Fields, when you’re creating your field, you’ll see an Edit button appear if you choose Rollup for Field Type.

image

When you click on the Edit button you’ll see a similar modern UI as when you edited your Calculated Fields, Business Rules, or Business Processes.

When editing the Rollup Field, you can select to use a hierarchy or not.  If you select to use the hierarchy, then what will happen is that all related records that are related to any record in the hierarchy will be used in the rollup (you can optionally filter records in the hierarchy as well).  An example here would be if you want to find the Total Open Revenue for Opportunities that are related to any Account in a hierarchy (versus those Opportunities that are just related to the current Account).

image

The calculation of a Rollup Field is different than a Calculated Field.  Whereas the Calculated Field was performed synchronously immediately after clicking Save on a record, a Rollup Field is calculated using asynchronous jobs.  This is performed automatically every hour, but if you’d like, you can kick off the calculation manually by hovering over the rollup field on your record form, and clicking the icon of the two arrows on the right of the field that states “Recalculate” when you hover over the icon.  You can also use the API to recalculate rollup fields on demand using code.

Similar to Calculated Fields, Rollup Fields are stored in the database and can be used and displayed like any other physical field in views / reports / charts / forms / Field Level Security.

You can solve some pretty complex business use cases using both Calculated Fields and Rollup Fields.  Rollup Fields can be a part of a Calculated Field, and a Calculated Field can be a part of a Rollup Field.

When modifying fields that affect the calculation, the calculated field is calculated synchronously after a Save is performed.  The the end user will get immediate feedback that data has changed after the form is refreshed.

Limitations:

Like all new features, it’s important to note the limitations and areas that hopefully Microsoft will improve upon with future releases:

  • General:
    • Workflows aren’t trigger by field updates
    • Latest values not available in plugin create/update pipeline
  • Calculated Fields:
    • Can only go 1 level up in N:1 relationships
    • Can only have all ANDs or all ORs in Conditions
    • Not available for offline
    • Have to save the record first before calculated field is updated when form refreshes
    • Only Calculated fields using all simple fields can be sorted
  • Rollup Fields
    • Only available using a single directly related 1:N entity
    • Complex calculated fields cannot be used in rollups
    • Rollup using other rollup fields is not supported

Contact Us for a Quote, or Personalized Demonstrationof Salesforce.com or Microsoft Dynamics CRM for Your Business.

Contact Us