Org Settings on LinkeD365 Blog

D365 Org DB Settings - Other

Sun, 03 Nov 2019 00:00:00 +0000

This is the second of a series where I try to document all the rarely used settings available to your Dynamics organisation to tweak the standard behaviour.

If you want to tweak your settings, see my previous post, or if you want to use a canvas app, see this post.

Alternatively, I have created an XrmToolBox tool to do this, documented here.

ActivityConvertDlgCampaignUnchecked

Default Value	True
Type	Boolean
Description	Controls the default value of the Record Closed Campaign Response option. When you convert an activity to an opportunity, this default option controls whether the source campaign is set or not. False- Record Closed Campaign Response checked and source campaign will be set. True - Record Closed Campaign Response not checked and source campaign is not set.
Min Version	5.0.9690.2720
Max Version

When you convert activity to an opportunity, you have the option to populate a related campaign and also record a closed campaign response. This setting implies that you can default the Record a closed campaign response to true, forcing the selection of a campaign, but in my environment, it isn’t working.

Someone prove me wrong

ActivateAdditionalRefreshOfWorkflowConditions

Default Value	False
Type	Boolean
Description	Enables an additional refresh of workflows that contain wait conditions and that may have to be resumed. This is required to be enabled to enable a fix that was originally released as a Critical On Demand hotfix, and was publically released starting with Update Rollup 13. When events in a Wait Until condition are met, the condition is not triggered as documented in KB 2918320 .
Min Version	5.0.9690.3445
Max Version	5.0.9690.3731

Redundant fix for what looks like an issue in a specific version

allowRoleAssignmentOnDisabledUsers

Default Value	False
Type	Boolean
Description	Enables the assignment of a security role for user accounts with a disabled status. This allows for scenarios where stub users can be created and assigned a different security role. This is needed when a stub/disabled user account needs to own records, especially when these records are from custom entities where custom security roles are required. False - By default, a security role cannot be assigned to users with disabled status. This is shipped by default. True - Allows security role to be assigned to users with disabled status.
Min Version	9.1.0.5610
Max Version

There are lots of times, particularly around migrating systems, where you are not ready for users to have access to a new system but want to import their data. Think about where you are migrating department by department. The long-term goal would be for users to all have access, so temporarily assigning the records to another user or a system user may not be appropriate. Ownership is usually an indicator and first point of contact in most systems and a driver for security, etc.

Toggling this setting to true allows assignment of roles, therefore records to disabled or stub users.

Set to false, it displays this error message when you save any changes.

ChangeDoubleQuoteToSingleQuote

Default Value	false
Type	Boolean
Description	Changes double quotation marks to single quotation marks within KB articles when the article is viewed.
Min Version	5.0.9690.3541
Max Version

This setting will do as it says, convert double quotes to single, but is only relevant for the old Knowledgebase Articles in your system, superseded by Knowledge articles that now have an appropriate WYSIWYG editor, this becomes redundant.

ClearSystemUserPrincipalsWhenDisable

Default Value	True
Type	Boolean
Description	Clear and/or populates SystemUserPrincipals values for systemUsers when they're disabled/enabled
Min Version	6.1.1.123
Max Version

ClientUEIPDisabled

Default Value	False
Type	Boolean
Description	Disables the sending of customer experience feedback for the organization. This option can also be disabled from the user settings area for each user. False - Enables the sending of experience feedback. True - Disables the sending of experience feedback.
Min Version	5.0.9688.583
Max Version

This, apparently, disables the option to send feedback to Microsoft when you get an error, great little setting, but until I get a repeatable error, can not see it in action

CreateSPFoldersUsingNameandGuid

Default Value	True
Type	Boolean
Description	True: creates SharePoint folders using the format of {Name}+{GUID}.- false: Creates SharePoint folders using just the name
Min Version	6.0.0.809
Max Version

When you integrate SharePoint, a folder in the site is created for each defined entity, normally with the name of the record and a GUID of the record. This can be ugly and not necessary if you have account names that are pretty unique. This setting allows you just to use the record name.

This screenshot shows with the setting as the default, true, at the top and the setting as false for JKL Sales

DefaultHeightForWizardReports

Default Value	8.25
Type	Double
Description	With a default value 0: CRM will use 8.25 inches (A4), any other double value will override the default of 8.25. Some printers may reject printed reports if the height is any less than the height of the paper loaded in the tray, this setting will override the height used
Min Version	5.0.9690.3541
Max Version

Printing can be problematic with different paper sizes etc. Not really a problem with modern printers, but this setting allows you to configure default printing sizes to ensure printing works for your organisation.

DisableIECompatMode

Default Value	False
Type	Boolean
Description	Changes the server-side, automatic, IE Compatibility Mode Flag for Internet Explorer browsers. If you want pages to render in the most recent version of Internet Explorer set this to True. If you have form scripts or other customizations that require earlier versions of Internet Explorer this should be set to False. This is also controlled via Settings \| Administration \| System Settings \| Customization
Min Version	5.0.9690.3233
Max Version

Compatibility mode was a big thing, particularly in the IE10 / 11 era. Making sure your website properly displayed across multiple browsers with inconsistent approaches to standards can still be a big gripe, but thankfully a thing of the past, with modern browsers adhering to standards a lot better.

DisableInactiveRecordFilterForMailMerge

Default Value	False
Type	Boolean
Description	When you perform a mail merge, inactive records are not included. This option lets you override that functionality. False - Inactive records will not be included in the mail merge. True - Inactive records will be included in the mail merge.
Min Version	5.0.9688.583
Max Version

Mail Merge is a deprecated function, but if you still use it, when you call a mail merge from a campaign, inactive contacts or leads are not included.

Mail merge is similar to the quick campaign, and I checked that this flag does not override the selection for quick campaigns, but it seems to have no effect.

EnableActivitiesTimeLinePerfImprovement

Default Value	False
Type	Boolean
Description	1 to enable, 0 to disable(preserve existing behavior)
Min Version	9.1.0.1639
Max Version

In 2019 Wave 2, October 2019, enhancements were made to the timeline, to improve the density of activities and allowing the user to filter by multiple types etc. Details here .

The new timeline can be seen below, which is toggled with EnableActivitiesFeatures described below. This setting toggles improvements to the performance of the new timeline, which may have an impact on your application.

Thought the official line is that this is disabled by default, in any new environment it seems to be enabled.

EnableActivitiesFeatures

Default Value	False
Type	Boolean
Description	Bitmask to Enable various activities feature in UCI; 1 to enable, 0 to disable(preserve existing behavior)
Min Version	9.1.0.1639
Max Version

In 2019 Wave 2, October 2019, enhancements were made to the timeline, to improve the density of activities and allowing the user to filter by multiple types etc. Details here .

The new timeline can be seen below, toggled on and off by this setting.

Thought the official line is that this is disabled by default, in any new environment it seems to be enabled.

EnableBulkReparent

Default Value	True
Type	Boolean
Description	Disables and reparents using a one record at a time approach
Min Version	6.0.0.809
Max Version

I am not sure this is relevant any more. I assume this is for where you have large datasets and on premise, that could (with cascading) lead to large data changes for each ownership change, but with my environment, I did not notice any change between the two options.

EnableQuickFindOptimization

Default Value	1
Type	Int
Description	For more information, see the "Optimizing the Performance of Quick Find Queries" section in the Optimizing and Maintaining the Performance of a Dynamics CRM 2011 Server Infrastructure.
Min Version	5.0.9690.2720
Max Version

Another one I assume has gone the way of the dodo for D365, this was initially configured to roll back the changes made to Quick find back in CRM 2011. I have toggle this on a new system and can not find any effect. This may be because of my minor data load etc and the optimisations that Microsoft has done since 2011.

EnableRetrieveMultipleOptimization

Default Value	0
Type	Int
Description	For more information, see the "Optimizing the Performance of Queries against Large Datasets section" in the Optimizing and Maintaining the Performance of a Dynamics CRM 2011 Server Infrastructure.
Min Version	5.0.9690.1533
Max Version

This is another one that is probably redundant for anyone not on CRM 2011, and I would think those that are administering these systems already know about these settings. There is a full table of the configuration for this setting in the linked document, tweaking the way (away from the default) for returning multiple records in a list.

As I do not have a CRM2011 environment and also don’t have the data volumes to see the effect, not sure I can or should add to this.

ExportedExcelRetentionWindow

Default Value	5
Type	Number
Description	The number of days to temporarily store Excel exported Office Document Records. 30 days max was selected arbitrarily as this is only a cache. Must be at least 2.
Min Version	7.1.0.1065
Max Version

Learning is great isn’t it? Researching this one led me to a great article from Bhavesh Shastri about the settings that may affect storage size, which has this setting in it.

Basically, when you export a data set into Excel, D365 stores the result in a temporary table so that you can get back to the result quickly. There is a deletion service that goes and tidies up these temporary tables and this setting defines how old these records are before it removes them. If you have a very active system, these records could adversely effect the size of your instance.

ExpireChangeTrackingInDays

Default Value	30
Type	Number
Description	Maximum number of days to keep change tracking deleted record ID's. You want this value larger than the max# of days any change tracking dependent services sync with your system. Default is 30 days.
Min Version	7.1.0.0
Max Version

This is another storage related one like the previous, again jump over to Bhavesh’s blog to get more detail. This setting doesn’t appear in the Microsoft KB article where the others are, even more confusing and makes me wonder what else Microsoft are hiding

If you have change tracking services running and worry about deleted records, this setting can be configured to increase the time these records are stored. Obviously, this will impact on storage if nothing else.

EnableTDSEndpoint

Default Value	False
Type	Boolean
Description	Enable a SQL TDS Endpoint for your CDS Environment NOTE: your region will also have to support TDS endpoints, the regions with support for TDS may vary (as documented in the docs url provided here).
Min Version	9.1.0.17162
Max Version

This, as it says, allows you to enable the CDS SQL TDS Endpoint, which allows you to use SQL Studio to query your live CDS environment. This is only recent, but is a great addition if you need more complexity in your queries.

Mark Carrington did a great set of posts on it’s usage here

ForceRetrievePublishedMetadataForRetrieveAllEntities

Default Value	False
Type	Boolean
Description	All RetrieveAllEntities requests will ignore the AsIfPublished flag so that it always retrieves the published metadata from cache.
Min Version	8.1.1.1020
Max Version

FullTextSpecialCharactersToRemoveFromSearchToken

Default Value	null
Type	string
Description	This allows an organization to remove certain characters from a fulltext search string. Example: To remove a wildcard character from a FullText search, add “”. To remove multiple characters, add them all together in a single string value “.’#”. The characters are separated by ToCharArray
Min Version	8.1.1.1020
Max Version

GrantFullAccessForMergeToMasterOwner

Default Value	True
Type	Boolean
Description	When two records owned by the same team are merged, the final record is shared with the owner of the record it was merged from. This creates redundant POA records, as a result, if the owner of the record is changed in the future it will be visible to team members of the previously owning team. To do this, set to false.
Min Version	5.0.9690.4449
Max Version

Another one of those security options that most people don’t know about. I would hazard to guess that most people don’t know that the owner of a subordinate record in a merge has the new master shared with them. Mark Carrington has a great explanation of this setting and the next in his blog here

The default setting puts a row in the Share table for the original owner, even if it is same as the new owner, which is useful in a lot of cases, but also could break your security model if the owner changes again.

With the setting put to false, the original owner does not have the record shared with them

The wording of this setting implies that only the master owner will have the sharing stopped, but it seems that the original does as well.

GrantSharedAccessForMergeToSubordinateOwner

Default Value	True
Type	Boolean
Description	To turn this setting off, this must be set to false. Records are shared with inherited access to subordinate owners during merge. This will not occur when set to false.
Min Version	5.0.9690.3911
Max Version

If you have a contact and merge the account, the contact will be moved to be owned by the master owner, but the owner of the contact will have the master record shared with them too. Obviously, this just makes the system work, but doesn’t help if you have a specific security prinicple in place.

Please see Mark’s blog to fully understand these values.

HideStageAndUpgrade

Default Value	1
Type	Int
Description	Changing this setting to 0 will allow users to see the upgrade solution option in solution import wizard when importing solutions with higher version than previously imported. This setting has a default of 1 which hides the option to perform a stage for upgrade.
Min Version	9.1.0.3
Max Version

Back in 2016, Microsoft gave us the ability to stage an upgrade solution, which means we can more easily remove parts of a managed solution, rather that using holding solutions.

Nishant Rana has an excellent blog here that describes the process. The process relies on having the Stage for upgrade tick box available to you, which is now hidden by default presumably because Microsoft has provided us the ability to create patches for solutions and it is no longer needed.

HierarchyLevelForHierarchyFeature

Default Value	3
Type	Number
Description	The hierarchy level used for hierarchal security
Min Version	7.0.0000.3027
Max Version

Another security tweak. There are 2 security models that may be in use in your instance, namely managerial or positional security.

Both can take into account a number of managers above you who have the same access to records that you do, which is traditionally 3, and anything above this can cause performance issues. As you can set the hierarchy level on the hierarchy configuration, this setting is now redundant I think, as any change you make to the org setting is not reflected in the setting on the Hierarchy setting screen.

IfdAuthenticationMethod

Default Value	null
Type	String
Description	Changes the request sent to the ADFS server, this settings default value
Min Version	5.0.9690.2835
Max Version

This setting is for on premise only, as it defines which SSO an internet facing deployment (an external facing on premise deployment) uses to establish the user has the right access credentials.

This blog has a more detailed explanation.

IncludeHTC

Default Value	true
Type	Boolean
Description	Set whether forms should support HTML component. The CRM 4.0 API uses this feature which is deprecated and will no longer be included after the next major release. If you have javascript code relying on CRM 4.0 javascript API's you should enable this and work to update your code to support CRM 2011. This is also controlled via Settings \| Administraton \| System Settings \| Customization. This setting is NOT SUPPORTED IN CRM 2013
Min Version	5.0.9690.3233
Max Version

This setting is only applicable to CRM 4, I know there are still users out there, but I can not get access to a system to try out this setting & assume even the CRM 4 people won’t be using this feature still

inheritedRolePrivilegesFromTeamRoles

Default Value	true
Type	Boolean
Description	Disables the Azure AD Group team functionality of the organization in an event that there is a performance related issue. The Azure AD Group team feature is shipped enabled by default. False - Disable Azure AD Group Team and members of group teams are required to have their own security role assigned to them directly. Run-time calls to Azure AD to obtain the user’s AAD groups are stopped. True - Azure AD GroupTeam is enabled and members of group teams shall inherit user/basic privileges directly and user privileges are derived at run-time. Run-time calls to Azure AD to obtain user’s AAD groups are invoked.
Min Version	9.1.0.4632
Max Version

Earlier this year, Microsoft gave us the ability to give security permissions to all the members of an Azure AD group, rather than having to duplicate security across Azure and Dynamics. This can be a time consuming god-send for your administrative staff, but also can impact performance. Setting this value to false forces the old method of security, with each user having to be configured with a role in D365.

Debajit Dutta has an excellent walkthrough on how to utilise this functionality here.

IdsCountBeforeUsingJoinsForSecurity

Default Value	1000
Type	int
Description	Not documented in optimization paper.
Min Version	5.0.9690.2720
Max Version

IdsCountForUsingGuidStringsForSecurity

Default Value	20
Type	int
Description	Not documented in optimization paper.
Min Version	5.0.9690.2720
Max Version

IntegratedAuthenticationMethod

Default Value	null
Type	string
Description	Changes the request sent to the ADFS server, this settings default value
Min Version	5.0.9690.2835
Max Version

An On-premise property, which I can not find anything on.

JumpBarAlphabetOverride / JumpBarNumberIndicatorOverride

Default Value	null
Type	string
Description	How to customize the Alphabet Bar for the CRM Application Grids for Microsoft Dynamics CRM 4.0
Min Version	5.0.9690.2243
Max Version

I didnt know this was a thing, but only for CRM 4.0. Basically, you could override what appears at the bottom of a search display.

Shivam Dixit has a walkthrough here

ListComponentInstalled

Default Value	False
Type	Boolean
Description	If CRM and SharePoint use ADFS and users click to create a folder for a record in CRM 2011, intermittently, the SharePoint page is shown instead of the list part grid page causing confusion with users. This setting allows you to force CRM to use the installed list grid component in SharePoint when using ADFS. false: use the standard method of detecting Sharepoint Authentication true: If CRM and SharePoint have ADFS enabled, force CRM to use the grid display.
Min Version	5.0.9690.3911 6.1.0.581
Max Version

This was a bug fix to force display of the SharePoint list instead of the page in a SharePoint created folder when a list is available.

LookupNameMatchesDuringImport

Default Value	False
Type	Boolean
Description	Importing a solution that was created from an upgraded 4.0 deployment fails. Changing this setting makes the import solution look up the names for forms, views, workflows and security roles.
Min Version	5.0.9690.583
Max Version

I have no access to CRM 4 to create a solution to test this out, but if anyone can create me screenshots, I’ll add in.

MaximumChildUsersCountLimitBeforeUsingJoinForHSM

Default Value	80
Type	Number
Description	Maximum Child/Subordinate Users Count Before Using a Join Query for Heirarchical Security Model
Min Version	7.0.0000.3027
Max Version

As mentioned, hierarchical security model gives your manager (or managers manager etc) the same access to your data that you have. As a manager with lots of reports, this can cause performance problems, so limiting the maximum unions it makes when deciding on your access makes sense. After this number is reached, an outer join will be used to improve performance.

If you have scenarios that require that number of child users to a manager, I would recommend not using Hierarchical security.

MinRowCountForFKIndexCreateInReferencingEntity

Default Value	100
Type	Number
Description	Setting min row count in referencing table for ForeignKey index creation
Min Version	7.0.0000.3027
Max Version

In the D365 world, the back end SQL optimisation is out of an administrators hands mostly, with indexes automatically been created for Primary keys or alternative keys for example. This setting tweaks the creation of indexes for FK keys.

If an account has a foreign key to a location entity, there needs to be more than 100 rows (by default) before the system will create an index on the account table using the location foreign key.

OfficeDocumentPersistenceTimeInDays

Default Value	7
Type	Number
Description	The number of days to temporarily store Office Document Records. 30 days max was selected arbitrarily as this is only a cache.
Min Version	7.1.0.1059
Max Version

When an office document is retrieved from the database, it is stored in the cache, by default for 7 days. This can be altered. This is one option that impacts the size of your tenant.

PageSizeForHierarchyFeature

Default Value	5
Type	Number
Description	The hierarchy page size used for hierarchal security
Min Version	7.0.0000.3027
Max Version

I assume that this is used in the same way as the MaximumChildUsersCountLimitBeforeUsingJoinForHSM setting, but I can not find any documentation for it

ReassignAllExtendedTimeout

Default Value	0
Type	Number
Description	Increase script timeout for reassigning all records of a user or team - this allows you to exceed the default extended timeout value. Default extended timeout is 1000000 ms (roughly 15 minutes). WARNING: Care should be taken when increasing this value above the default - always double check the number of minutes before setting this to a value higher than the default
Min Version	7.1.2.1020
Max Version

If you have a security model that relies on a cascade of ownership, when a parent owner is changed, this ownership is also done for children and children of children etc.

This can be a time-consuming process which you can increase the time-out for, possibly temporarily if you have an occasion that required it, though the default 15 minutes is a very long time.

RecordCountLimitToSwitchToCteSecuritySql

Default Value	75000
Type	Int
Description	For more information see the Optimizing the Performance of Queries against Large Datasets" section in the Optimizing and Maintaining the Performance of a Dynamics CRM 2011 Server Infrastructure.
Min Version	5.0.9690.2720
Max Version

I didnt know this was a thing, but only for CRM 4.0. Basically, you could override what appears at the bottom of a search display.

This setting is for On-premise only, impacting the switching to use a temporary table or CTE (Common Table Expression) to generate the results. I have not got enough data to check if this still has an impact on D365 environments.

The linked paper has a lot of good stuff about optimisations, that thankfully the more modern SAAS environments have taken care of.

RetrieveMultipleSharingCountThreshold

Default Value	1000
Type	Int
Description	For more information, see the "Optimizing the Performance of Queries against Large Datasets section" in the Optimizing and Maintaining the Performance of a Dynamics CRM 2011 Server Infrastructure.
Min Version	5.0.9690.2720
Max Version

This is another setting that is for optimisation of the on-premise architecture, defining the number of shared records the user has for the entity being searched for (either direct or via teams) that the system will convert the query to joins rather than table value functions.

As sharing with individuals should be an increment to your security model rather than the main part, having 1000 shares per entity would be pretty rare.

SecurityQueryHint

Default Value	1
Type	Number
Description	Used to hint the query within GetRightsFromPrincipalObjectAccess. 0=None; 1=Recompile (default); 2=OptimizeForUnkown
Min Version	8.1.0.141
Max Version

I can’t find any information on this. Will update when I find out.

SharingLimitForPOASnapshotTable

Default Value	10
Type	Int
Description	Not documented in optimization paper.
Min Version	5.0.9690.2720
Max Version

I can’t find any information on this. Will update when I find out.

skipAadGroupObjectIdValidation

Default Value	False
Type	Boolean
Description	Disables the validation of Azure AD Group objectID and allows application to create Group team in CDS. This is used to mitigate the latency in the Azure AD distributed cache where a newly created Azure AD group cannot be validated if the subsequent Azure AD Group graph call goes to a distributed cache server that does not have the new Azure AD group yet. False - do not skip Azure AD group objectID validation during Group Team creation. This is shipped by default. True - skip Azure AD group objectID validation to allow application to create Group team.
Min Version	9.1.0.5808
Max Version

If you use the new functionality to connect teams to AD groups, allowing a single location to manage security, setting up the teams needs a link back to the AD group.

As AD group creation takes time to propagate to the various caches, the group you want to link to might not be available, so, by default, no check is made to see if you have got the GUID right. This can be forced if you need that extra piece of mind by setting this value true.

SkipGettingRecordCountForPaging

Default Value	False
Type	Boolean
Description	Disables the record count query. This query is responsible for retreiving the total number of records returned for each view. This query can cause longer search times and may cause SQL timeouts or exceptions. False - Enables record depend on views. True - Disables record depend on views.
Min Version	8.2.0.0503
Max Version

When you have a large dataset, knowing that you have thousands of records rather than just the 100 the view is showing is invaluable, but this query has to be done, as well as the query to retrieve the data, impacting performance

With the setting applied, the query doesn’t display an accurate number, but it does display a number, which is mis-leading in my opinion.

SkipGettingRecordCountForPagingForAudit

Default Value	False
Type	Boolean
Description	Disabled the record count query for just the Audit entity. False enables the record count, and True disables the record count
Min Version	8.2.0.0503
Max Version

This is the same as the previous setting, but just for the auditing views, which are notoriously large.

SkipSuffixOnKBArticles

Default Value	False
Type	Boolean
Description	Disables the suffix from being used on the automatically generated KB article numbers. False - Enables the suffix on KB articles. True - Disables the suffix on KB articles.
Min Version	5.0.9690.1992
Max Version

Pretty self-explanatory, but for old KB articles rather than the new Knowledge Articles.

TabletClientMaxFields

Default Value	75
Type	Number
Description	Maximum Tablet Fields max-500/ min- 1
Min Version	6.0.0.809
Max Version

These tablet settings are not for D365, v9 as Unified interface has removed the limitations

TabletClientMaxLists

Default Value	10
Type	Number
Description	Maximum Tablet Lists max-50/min-1
Min Version	6.0.0.809
Max Version

These tablet settings are not for D365, v9 as Unified interface has removed the limitations

TabletClientMaxMashups

Default Value	3
Type	Number
Description	Maximum Tablet Mashups
Min Version	7.0.0000.3027
Max Version

These tablet settings are not for D365, v9 as Unified interface has removed the limitations

TabletClientMaxTabs

Default Value	5
Type	Number
Description	Maximum Tablet Tabs max-50/min-1
Min Version	6.0.0.809
Max Version

These tablet settings are not for D365, v9 as Unified interface has removed the limitations

traceLogPersistenceTimeInDays

Default Value	30
Type	Int
Description	This sets the amount of time that TraceLog data is maintained before being removed by the Deletion Service
Min Version	8.1.1.1020
Max Version

This is another setting that can impact the size of your instance. The logs are stored by default for 30 days, if you have a heavily used system, this will be a lot of data, so reducing this will reduce costs. Trace logs are part of a separate pricing tier now, but still worth a look.

UseOrganizationServiceForMultiEntityQuickFind

Default Value	False
Type	Boolean
Description	Allows Multi-entity Quick Find to run serially rather than in parallel. This allows plugins to be executed on RetrieveMultiple.
Min Version	8.2.1.0135
Max Version

Retrieve multiple plugins can do a little more security to prevent the display of records or adding in data to a record set if you need it to be really truly accurate.

Whilst this is frowned upon as is a real impact on system performance, it might be necessary. If you need this functionality, quick view doesn’t honour this logic as the queries run in parallel. Toggling this to true makes each quick query run in serial, allowing retrieve multiple plugins to work.

WorkflowXamlValidationErrorReport

Default Value	False
Type	Boolean
Description	WorkflowXamlValidationErrorReport is used to fail workflow loads if the XAML is not valid
Min Version	9.1.0.5808
Max Version

I can’t find any information on this. Will update when I find out.

D365 Org DB Settings - Canvas App

Wed, 16 Oct 2019 00:00:00 +0000

On the back of one of my other posts on the D365 Org DB Settings I thought it would be good to re-imagine the method to update these settings in a Canvas app.

The solution from Sean McNellis is great and has been a big influence on my design, including the settings xml is pretty much a copy. I am hoping that I give users a more visual experience and this is a starter for a bunch of D365 CE admin apps in PowerApps.

I am now looking for people to test it and give me feedback on the solution, so if anyone has a little time to be critical, please contact me on the blog, via Twitter or on GitHub as an issue.

https://github.com/CooksterC/D365-Admin-Tools

Overview

Hope you like green….

On the left is a list of the options for configuration. By default, it only shows the ones that are already configured, but we can alter this to show all settings by toggling the top button. You can also search at the top for the setting you want.

The list is also colour coded, to highlight the ones you have changed, the ones that are configured already and the ones that have no setting.

The grid shows the official documentation of the setting and a link to the KB article.

The Bin button will remove this setting from your configuration, returning it to the default.

The + button will add the setting to your configuration using the default value.

The Value entered can be different controls depending on the value been configured.

At the top right, you can save any configuration changes, which refreshes the list and the bottom right panel, which shows the current configuration

The top panel will display the documentation on the settings. There is also the ability to copy a configuration from another system or manually edit the xml.

NO WARRANTIES GIVEN. If you get this wrong, then don’t blame me!

Installation

The package is a solution, with 2 components, the Canvas App and a custom connector.

As part of the app, the settings xml is cleared before it replaces with the new configuration, using the standard connector gives an error when this is done, so I reverted to doing this via a custom connector. Also, the settings are reliant on the version of your D365, less of an issue now that everyone is on the same version, but for those on premise, the version is required, again not available in a normal connector.

I have found that if I include that in a solution, it has the intended effect of bringing with it the connection to the api that it is configured for. This is great for deploying apps using a common api, but in this scenario, I don’t want you to use my tenant, but your own. Not sure how this could be improved, particularly for ISVs etc. Also, as the solution matures, everytime you import the solution, the connector needs reconnecting, which isn’t ideal.

So there is 2 parts, the Canvas App exported as a package and the connector.

Connector Configuration

Select New Custom Connector / Import as OpenAPI file

Put in your environment link here. This is mine, and the solution method of connectors copies these settings, thankfully it is OAuth, so unless you know my password (and this is a trial).

Next is security. Edit the OAuth 2.0 settings.

You need to enter the Client Id and Client Secret taken from the Azure AD authentication as well as the Resource URL being the address of your environment.I stepped through this when I created my first custom connector for LUIS integration.

Update the connector and move on to testing.

I have only got 3 actions defined here, keeping it to the actions I need for the application and WhoAmI, which is so simple, allows me to confirm the connection prior to worrying about syntax.

As this is OAuth, you need to configure a connection, which is a prompt for you enter your credentials.

Test the operation to prove you have got your connector up and running.

Install the Canvas App

Got to your apps and select Import package. Select the zip file from GitHub repository.

The first time you install, it has nothing to update, so you will need to change the action to “Create as new” and give it a new name if you don’t like it.

On the connector, you should connect it to the one that has just been created

Hit import and you are done! Run the app to see a default configuration.

Like I have said, I would like feedback, particularly on how to improve the installation process. It is rather fiddly, would love to be able to just install a solution and you are done.

D365 Org DB Settings - Email

Tue, 01 Oct 2019 00:00:00 +0000

On a client recently I helped deploy Microsoft D365 App for Outlook. Unfortunately, the behaviour requested by the client and the default behaviour of the Server Side synchronisation was not aligned.

This led to long discussions with Microsoft about some of the DB Org Settings we could utilise to tweak the way SSS works. As I researched these settings and discussed with my colleagues and during networking events, it became clear they remain unknown to most developers and administrators. If your deployment needed to tweak the settings, then people knew, but it is not common knowledge.

Further, there seemed to be very little documentation on what each setting does, apart from Microsoft’s own information here.

This is a series of posts explaining each of the Org settings, understanding how it affects your environment. Hopefully it will raise awareness of these settings.

Bear in mind that there a lot of settings that I can not find any information on or have no experience on. This is frustrating for me, but assume someone in the community will push me in the right direction and I will update the page when I find out.

How to Change Org DB Settings

Sean McNellis has an excellent tool on GitHub here which allows interaction with the org settings via a solution in your environment.

One the solution is imported, selecting the solutions gives you an interface where you can check the current status of each setting and change them.

To change the default, you need to select the Add hyperlink. This creates an XML file including your property which is uploaded to your system to change the setting.

Selecting the Edit link for the attribute now gives you a popup window, where you can edit the value

Also, Sean has included a copy of the Microsoft description with each setting.

On the right side of the grid is a link to to the KB article that mentions the setting, though normally it is just to KB 2691237 which is the central list of all Org settings.

ActivityRollupChildRecordLimit

Default Value	50,000
Type	Number
Description	Limit the number of total aggregated activities to rollup in the Activity Rollup Default:50,000. Used with: VisibleRecordThreshholdSwitchToMultiplelineTVF and TotalRecordThreshholdSwitchToMultiplelineTVF
Min Version	9.1.0.8031
Max Version

This is a new one on me. Activities roll up. You put an email against a contact, the email is available on the account the contact is associated with. This applies to custom entities as well, if you configure the relationship correctly. Inogic has a great post on it here.

This setting must have come about to limit this as the numbers where getting too big for some. I have not got the data to do this one justice unfortunately.

AddressBookMaterializedViewsEnabled

Default Value	True
Type	Boolean
Description	Changes the way the CRM Client queries SQL CE
Min Version	5.0.9690.2903
Max Version

The description doesnt tie up with the title, and when you google it, this setting revolves around a previous setting, Disable MAPI cache, that was around in CRM 2011 and helped improve performance. Not a lot more I can say.

AllowPromoteDuplicates

Duplicates in D365 are not unheard of, but when Outlook sync comes in, there are more chances to get duplicates. When a user syncs an Outlook Contact,

AllowSaveAsDraftAppointment

Default Value	False
Type	Boolean
Description	Setting value to true will provide the capability to create appointments in Dynamics 365 as “draft” without synchronizing with Exchange. Appointment form will have a “Save as Draft” command and a “Send” command, so that you can save, add details and update an appointment activity without synchronizing to Exchange. Default value is set to false to preserve existing behavior.
Min Version	9.0.2.2275
Max Version

This flag opens up the possibility that you don’t always get a meeting correct the first time and allows you to save a draft.

Ulrik Carlsson aka @CRMChartGuy from eLogic solutions has a great article about this attribute.

The default behaviour is that users are not presented with a Save as Draft option for appointments, when a appointment is saved, if you are using SSS it will synchronise to Outlook and send out invites to the attendees as normal.

If you change AllowSaveAsDraftAppointment to true, the users get a different set of buttons.

Both Send and Send & Close buttons behave like the original Save and Save & Close. They will initiate a server side sync one the record is saved.

The new button Save as Draft will save the appointment but not send it to Outlook etc. It adds a [Draft] prefix to the appointment header and also a new field on the appointment, isdraft, is populated with true.

Weirdly, this field can not be added to a form. It just doesn’t appear in the field list. You can add it as view filter criteria, but you can’t display it as a column in a view.

AutoCreateContactOnPromote

Default Value	True
Type	Boolean
Description	Disables the ability of the organization to create contact records automatically when an email message is tracked in CRM. This option can also be disabled from the user settings area for each user. False - Disables the automatic creation of contacts. True - Enables the automatic creation of contacts.
Min Version	5.0.9688.583
Max Version

By default, when a user sets regarding within the Outlook app, if any email address is in the To / CC / BCC etc that D365 does not know about, it creates it automatically.

Most of the time this is fine, but consider when your business process requires a lot more data fields to be populated in the contact, this default process will create a contact that hasn’t got what your business needs. Forcing the contact creation away from this automation may be required.

Users have an option under their personal settings which will mimic this settings, but this does it for everyone.

Setting the AutoCreateContactOnPromote to false removes the option from users and no contacts are created automatically when emails etc are synced.

AutoTrackSentFolderItems

Default Value	False
Type	Boolean
Description	Setting value to TRUE will result in Server Side Sync auto tracking of emails from Sent Items. This setting only applies if the mailbox is configured to track "All Email Messages" Default value is set to False to preserve the existing behavior. To enable functionality on the organization "AutoTrackSentFolderItems" should be set to True.
Min Version	8.2.2.0840
Max Version

This setting works in hand with the selected option under “Select the email messages to track in D365” option under Personal Options.

By default, sent emails are ignored, only picking up emails that arrive to send to D365.

By marking the AutoTrackSentFolderItems to true, sent items will also be tracked, from the next sync, not retrospectively

BackgroundSendBatchSize

Default Value	10
Type	Integer
Description	Sets the number of email messages to download in one batch for the BackgroundSend API.
Min Version	5.0.9690.583
Max Version

ClientDisableTrackingForReplyForwardEmails

Default Value	False
Type	Boolean
Description	Enables a user not to automatically track replies and forwarded email messages. Set this to "True" to disable tracking replies and forwarded email messages. NOTE: This setting only applies to Dynamics 365 for Outlook (not Dynamics 365 App for Outlook).
Min Version	5.0.9690.2903
Max Version

When a user receives a reply to an email that has already been tracked, the reply will also be tracked by default. This is great for keeping the chains of emails all within D365. Unfortunately, this may lead to conversations being tracked that shouldn’t and give visibility to sensitive conversations - a manager receiving an email that was a complaint about a particular email that their report sent for example.

Whilst this is mostly a training exercise, it can be quite embarrassing and this setting stops that. It does mean that you could lose out on a part of a conversation and rely on the user to track a response separately.

This settings, as noted, only works with D365 for Outlook not the App for Outlook.

DisableClientUpdateNotification

Default Value	False
Type	Boolean
Description	Setting DisableClientUpdateNotification to true will disable the outlook client from checking for newer versions
Min Version	7.0.0000.3027
Max Version

Only for the D365 for Outlook, will prevent the application checking for a new version. This will help if you are in a locked down environment and need the stability.

With the D365 App for Outlook, it is a constant deployment rolled out with other fixes by Microsoft.

DisableImplicitSharingOfCommunicationActivities

Default Value	False
Type	Boolean
Description	Changing this to "True" will disable implicit sharing of records to recipients that are added to existing activities.
Min Version	5.0.9690.2903
Max Version

When an email, meeting, phone call etc. is created and an internal user is included in the recipients list, it shares the record with them. This allows the internal user to have visibility of the record within D365.

If your security model has an issue with this, then this implicit sharing can be removed.

Your model may restrict the visibility of activities depending on what record the activity is associated with in a team scenario. If the original recipient is no longer in the team, they should not have access to that information any longer. With the OOTB logic, this activity will still be visible.

This email will still be in the recipients Outlook, nothing changes to the visibility in exchange, it is just the visibility in D365.

DisableLookupMruOnOutlookOffline

Default Value	False
Type	Boolean
Description	LookupMRUItems in UserEntityUISettings can cause a large data volume when going online, setting this to true will stop MRU's from syncing back ONLINE
Min Version	6.1.0002.0106
Max Version

This one is not obvious to me and there is no information online. I’ll update when I find anything out

DisableMapiCaching

Default Value	False
Type	Boolean
Description	When this value is set to "True," users can still pin the views. However, the query is sent to the CRM Server to retrieve the results instead of to the local cache to prevent performance issues. Note This value is not valid with CRM 2013.
Min Version	5.0.9690.2903
Max Version

This was present to prevent server performance issues, typically seen with on-premise solutions, when results are retrieved from the cache of the server, rather than direct from the database. It is unclear if still needed.

DisableSmartMatching

Default Value	False
Type	Boolean
Description	Disables the smart matching functionality and relies on the tracking token on the incoming e-mails for email tracking. False - Enables smart matching. True - Disables smart matching.
Min Version	5.0.9688.583
Max Version

Smart Matching is how Microsoft works out that the email you just sent in belongs to a conversation that you have already synced, hence it will sync that email when it comes in.

In System Settings, you have several options when it comes to matching. Correlation is the default, where it is using a conversation id on each email to match them. You can supplement this with a tracking token and/or smart matching.

Token is generally used for support scenarios, to ensure any replies to an email are tracked against the same case.

Smart matching does what it suggests, using keywords in the subject and an algorithm to determine if the email is linked to a previous conversation.

Using the DisableSmartMatching flag does the same as un-ticking the box on the system settings, where conversation id and tracking tokens are relied on.

DistinctPhysicalAndLogicalDeletesForExchangeSync

Default Value	False
Type	Boolean
Description	Server-Side synchronization needs a mechanism to distinguish between Logical and Physical deletes of entities in CRM False : No distinction between physical and logical deletes for exchange sync delete scenario True : Physical and logical deletes will be distinguished for exchange sync delete scenario
Min Version	8.2.2.0840
Max Version

This is another where security takes over and users expectations can differ from the way Microsoft thinks it should work.

If a user has been invited to a meeting, and it is recorded in D365, a copy of that exists within D365 and Exchange. If, for whatever reason, the user loses access (reas access) to that meeting in D365, the default behaviour would be to delete the copy in Exchange. Makes sense, to keep those in sync.

With the DistinctPhysicalAndLogicalDeletesForExchangeSync set to true, lose of access to any activity does not mean that the activity is deleted in Exchange. Use this with DisableImplicitSharingOfCommunicationActivities to fully get control of activity access.

DoNotIgnoreInternalEmailToQueues

Default Value	Version 5.0.9690.1533 to 8.2.2.1300: False Version 8.2.2.1309 and higher: True
Type	Boolean
Description	If you disable the "Track email sent between CRM users as two activities" setting, email messages from a CRM user to a queue are not delivered. Additionally, if a workflow rule sends an email message to a queue, email messages that are sent by the workflow rule are not delivered. False - Internal email messages to queues will not be delivered. True - Internal email messages to queues will be delivered.
Min Version	5.0.9690.1533
Max Version

This is used in combination with the Track emails sent between Dynamics 365 users as two activities available in the system settings

If you enable the Track as a separate option, normally any email from internal user to a queue mailbox will be ignored. This seems a weird consequence, but they have provided you with an override so that these internal mails are not ignored.

EnableAppointmentBroadcastingForOutlookSync

Default Value	0
Type	Number
Description	Setting for Appointment broadcasting for Outlook Synchronization
Min Version	7.0.1.121
Max Version

I can’t find any information on this. Will update when I find out.

EnableCrmStatecodeOnOutlookCategory

Default Value	True
Type	Boolean
Description	Enables Statecode data on contact sync
Min Version	6.1.0.581
Max Version

EnableSssItemLevelMonitoring

Default Value	False
Type	Boolean
Description	Setting value to True will enable a new dashboard accessible by users and administrators called Server-Side Synchronization Failures. This dashboard allows the owner of a mailbox to have information about all non-synched incoming/outgoing emails and also appointment, contact, and task (ACT) items. Information is provided for the reason items are not synchronized. Default value is set to False to preserve the existing behavior. You can use the ExchangeSyncIdMappingPersistenceTimeInDays setting to control how long the data for failed emails is retained.
Min Version	8.2.2.1661
Max Version

There is a dashboard available to admin already called Server-Side Sync failures, without this setting. Not sure what this does, as the dashboard seems to be available regardless.

ExchangeSyncIdMappingPersistenceTimeInDays

Default Value	3
Type	Int
Description	The number of days for which the ExchangeSyncIdMappings are to be persisted for failed emails. This setting is used in relation to the EnableSssItemLevelMonitoring setting. It is not recommended to increase this value higher than 7 days as it can lead to the table growing very large.
Min Version	8.2.2.2059
Max Version

This setting defines how many days of sync failures are kept, useful when you are troubleshooting, but table will get huge quickly, so only increase if you need to.

ExpireSubscriptionsInDays

Default Value	90
Type	Number
Description	Max number of days before deleting inactive Outlook client subscriptions. We recommend you keep this to the default unless you absolutely need to change it, be mindful of keeping the tracking info too long, or deleting it too soon.
Min Version	6.0.0.0
Max Version

On creating my second post in this series I came across several configurations that were not documented in the KB article and hence were missed when I wrote this.

When you track an contact in Outlook, you are subscribing to changes made to those contacts in D365 so that they are mimicked in your Outlook. This is great, but each subscription is stored in a database record, hence impacting storage costs. There is a deletion service that works through the subscriptions and deletes these expired lines. after the value is reached, with an outlook Client refreshing it’s subcriptions as part of it’s sync routine.the

HideEmailAutoTrackOptions

Default Value	False
Type	Boolean
Description	Default value is false, if it's set to True: do not show the following track options in Personal Options (Email): 'All email messages', 'Email messages from D365 Leads, Contacts and Accounts', 'Email messages from D365 records that are email enabled'
Min Version	9.1.0.1639
Max Version

This setting goes one further to the one below by stripping out “All email messages”, “Email messages from D365 Leads, Contact and Accounts” and “Email messages from D365 records taht are email enabled”, just leaving you with the two below.

HideTrackAllOption

Default Value	False
Type	Boolean
Description	Removes “All email messages” option from users’ Personal Options under Email tab Select the email messages to track in Microsoft Dynamics 365 area. False – "All email messages" option is shown in the dropdown. True – "All email messages" option is not shown in the dropdown. If a user already has "All email messages" selected, their synchronization option is not updated in DB. Administrators will need to update this value via SDK.
Min Version	9.0.2.264
Max Version

Under personalisation settings for each user, they can decide to track all emails they receive from any source. Great for a shared mailbox or customer mailbox, but not for a normal user who receives spam and invites to cake sales etc.

The default here is Email messages in response to D365 mail, but to stop users filling your D365 instance, setting the HideTrackAllOption to true will remove that top option.

Any users that had this setting prior to it’s removal need to be updated manually or via the SDK.

IgnoreCopiedItemsInSSSForMailbox

Default Value	False
Type	Boolean
Description	Ignore creating duplicate for copied items for Server Side Sync
Min Version	9.1.0.11129
Max Version

Normally, when an email or meeting or task is synced, it doesn’t matter where that content came from. If it appears new, it will be created new, even if it is a copy of another item. This will reduce the amount of synced items but may be a concern for your environment.

MailboxStatisticsPersistenceTimeInDays

Default Value	3
Type	Number
Description	If value is 0, dont store ANY MailboxStatistics Data, if the value is greater than zero then store that number of days statistics data. Max value arbitrarily chosen at 1 year, this generates at lot of data so 1 year should be plenty of time
Min Version	8.0.0.1088
Max Version

The Mailbox statistics records how frequently a mailbox is accessed and synced. This way, the more active mailboxes are synced more regularly. A mailbox that is infrequently used will be checked less regularly.

On a high user system, with SSS on, it can get populated quickly, so 3 days will normally be appropriate.

OutlookClientEmailTaggerEnabled

Default Value	False
Type	Boolean
Description	here are 3 values for this Boolean setting - true, false, and NULL (which is the value when NOT set). True: Will override any and all client registry setting to True. False: Will override any and all client registry setting to False. NULL: If the setting is NULL the outlook clients will use whatever is in the registry of the client. TO SET THIS VALUE TO NULL YOU WILL NEED TO CLICK EDIT, THEN REMOVE THE VALUE TO HAVE IT DEFAULT TO NULL.
Min Version	7.0.1.121
Max Version

OutlookSyncDataSubscriptionClientsBatchSize

Default Value	100
Type	Number
Description	This setting is used to determine how many record changes (deletes, inserts, and updates) to send back to a syncing client for each request.
Min Version	7.1.0.1059
Max Version

OverrideTrackInCrmBehaviour

Default Value	0
Type	Int
Description	When this option is Enabled, the ‘Track in CRM’ button functions as the Set Regarding button in Dynamics 365 for Outlook. In Dynamics 365 App for Outlook, ‘Track without regarding’ command is not displayed, with Set Regarding as the only way to synchronize Outlook items to Dynamics 365. 0 - Normal behavior of the "Track in CRM" button not having to set a Regarding record in Dynamics 365 for Outlook. ‘Track without regarding’ command is displayed in Dynamics 365 App for Outlook. 1 - The ‘Track in CRM’ button functions as the ‘Set Regarding’ button, and makes you select a regarding record in Dynamics 365 for Outlook. In Dynamics 365 App for Outlook, ‘Track without regarding’ command is not displayed, with Set Regarding as the only way to synchronize Outlook items to Dynamics 365. NOTE: This setting applies to both Dynamics 365 for Outlook and Dynamics 365 App for Outlook.
Min Version	9.1.0.6200
Max Version

Normally, a user can track an activity to D365 without associating with a record, the Set regarding. This could lead activities in your tenant not associated with a record, orphaned. Depending on your business requirements, disabling this feature could be required.

Normally, under the … under Not Tracked, the user has an option to Track without Regarding

Setting OverrideTrackInCrmBehaviour to 1 will override this behaviour, removing the ellipses button altogether. The user has to establish a link to an existing record to sync the email or activity.

OverrideV5SenderConflictResolution

Default Value	False
Type	Boolean
Description	When multiple records with the same email address exist in the Dynamics CRM Organization and email is automatically tracked, the email address is resolved to the record for the owner record that was created first. This option lets you override that functionality. False - E-mails are tracked to the first record created. True - E-mails are not tracked automatically if there are multiple records with the same email address.
Min Version	5.0.9690.2243
Max Version

Michael Sulz has a good write up on this, here.

Normally, if there are 2 or more contacts with the same email address (data quality is always a problem, however much you take care of it, though data8 do a real good job of removing duplicates and improving your data) the contact chosen is the first contact owned by the syncing user, sorted by create date or the first created if that doesn’t match.

Setting this option to true will force the user to make a decision and not sync the email automatically.

RestrictIRMEmailItems

Default Value	False
Type	Boolean
Description	Setting value to TRUE will result in Server Side Sync NOT synchronizing ALL emails that are marked as IRM emails. Default value is set to False to preserve the existing behavior. To enable this restriction on the organization " RestrictIRMEmailItems " should be set to True.
Min Version	8.2.2.0840
Max Version

Bhavesh Shastri has a great write up of this configuration here

Restricted messages, those that the sender has marked as any of the restricted types in Azure information Protection, may not be suitable to be included in your D365 system.

If you set his flag to true, the user will not be able to sync those that are protected and will be given an error message if they try to.

SecuritySettingForEmail

Default Value	False
Type	Number
Description	1: Display a Warning Message And give an option to open - 2: Display a Warning Message and do not give an option to open 3: Do not display a Warning Message and do not give any option to open. This setting is NOT SUPPORTED IN CRM2013 as of build 809
Min Version	5.0.9690.3731 6.1.0.581
Max Version

The majority of emails that a user receives and hence sync to D365 contain HTML to some degree, whether it is simple formatting or full on marketing emails.

In all scenarios, the interface presents a stripped down version of the email, but formatting etc will be lost.

There is a risk when these are displayed in all their glory in D365, that parts of the email could be nefarious, including scripts etc that could include phishing or other attacks. Microsoft by default warns the user that this is the case, but allows the user to click through to the content, putting the decision in the users’ hands.

If you change the setting to 2, the link to the full content is removed

Changing the setting to 3 removes the message and always shows the full version of the email

SendEmailSynchronously

Default Value	0
Type	Int
Description	If you have a plugin registered on the email send flow, you should change this setting to "1." 0 - Email is sent asynchronously. 1 - Email is sent synchronously.
Min Version	5.0.9690.2720
Max Version

Depending on your logic, you may interact by workflow when an email is sent via Outlook. This setting moves the send email to a synchronous operation rather than asynchronous, allowing a more immediate interaction with the email. This may have a performance impact on the user in Outlook.

SortEmailByReceivedOn

Default Value	False
Type	Boolean
Description	When the Activities tab of the social pane is show, the data ordered by the 'modifiedon' date in descending order, toggling this setting to True will enable the social pane to sort emails by RecievedOn Desc instead of modifiedon
Min Version	8.0.1.79
Max Version

I am not sure that this is a problem any more, in Social pane in D365 we have a lot of options for searching, but back in the legacy UI this allowed you to change the email sorting from the date the email was edited or added to D365 to the date the email was received. This could be several days difference, so it could give a different perspective to the conversation.

TraceExchangeSyncData

Default Value	true
Type	Boolean
Description	Enables exchange sync tracing
Min Version	6.0.0.809
Max Version

Logging of the sync data is essential for any troubleshooting, but it adds to the size of your database. With the separation of log and data in storage costs, I am not sure this should ever be turned off if you are using SSS.

TrackAppointmentsFromNonOrganizer

Default Value	True
Type	Boolean
Description	Enabled users to track appointments organized by another Dynamics 365 user via Dynamics 365 App for Outlook. False – Dynamics 365 App for Outlook and Server-Side Synchronization users cannot track Outlook appointments whose organizer is a Dynamics 365 user. True – Dynamics 365 App for Outlook and Server-Side Synchronization users can track Outlook appointments whose organizer is a Dynamics 365 user.
Min Version	9.1.0.0294
Max Version

You can always track a meeting if it was sent from an external user and by default, you can track any appointment where the organiser is a D365 user. This setting prevents the user from tracking an appointment if it is not them organising it.

TrackCategorizedItems

Default Value	True
Type	Boolean
Description	Setting value to False will remove the category tracking flag and functionality. Default value is set to True to allow category tracking and tracking status visibility for users whom do not use Dynamics 365 for Outlook or Dynamics 365 App for Outlook.
Min Version	8.2.2.0840
Max Version

Using Category based tracking is a great way to allow users to track multiple emails at once. In the App for Outlook, this is the only way.

With the OOTB behaviour, the user gets a new category added and is able to select multiple emails to sync. It also appears as a great indicator in Outlook that the activity is synced.

Setting the flag to false removes this category and ability.

Be warned on this, if you leave any item with the category on it after you have disabled this functionality, re-enabling the functionality will mean that these items will be synced. Also, this category doesn’t respect the fact you upgrade. An email with the category that was synced to an on premise version will create a duplicate if that user is moved to the online version and the originating email was migrated as part of the data migration from on-prem to online.

UseCrmOrganizerForEmptyExchangeOrganizer

Default Value	False
Type	Boolean
Description	Use the CRM Organizer of an Appointment if the Exchange Organizer doesn't exist.
Min Version	8.1.1.1020
Max Version

I think this is more to do with rare cases when the sync doesn’t work correctly, but another one that I can not find any information for.

UseFilteringMethodOfSyncingMailboxOnlyForCorrelation

Default Value	False
Type	Boolean
Description	This is for controlling which users’ filtering settings will be used for correlation. False – filtering method of all recipients of the email will be checked to decide if any user/queue accepts email or not. True – filtering setting of user who synced email to CRM will be used. Filtering setting of other recipients of the emails will be ignored.
Min Version	8.2
Max Version

Each user has a seperate filter list to decide which emails are synced to D365. These can be various settings on what that individual user requires.

The default for this setting, the standard OOTB behaviour, is false, where any user can sync this email if it matches their settings. True means that the user who created the email or synced it will be able to have the email included in the selection for the filter. It is in effect an additional filter for the user to only include emails I have created.

UsePlainTextForEmailTemplateBody

Default Value	False
Type	Boolean
Description	Changes the Email Template to use plain text where otherwise text with the following symbols would not appear <text>.
Min Version	5.0.9690.2720
Max Version

This is one of the older settings, presumably when people had email clients that could not handle html formatted text.