Dynamics:Best Practices - Revision history

Admin at 14:58, 27 September 2018

2018-09-27T14:58:11Z

← Older revision		Revision as of 14:58, 27 September 2018
Line 1:		Line 1:
	[[Dynamics ~~CRM~~\|← Dynamics ~~CRM~~]]		[[Clean Suite for CRM:Dynamics\|← Clean Suite for CRM:Dynamics]]
	{{CustomTOC}}		{{CustomTOC}}
	==Installation==		==Installation==
Line 96:		Line 96:


	[[Category:Dynamics ~~CRM~~]]		[[Category:Clean Suite for CRM:Dynamics]]

Admin at 23:43, 5 March 2018

2018-03-05T23:43:02Z

← Older revision		Revision as of 23:43, 5 March 2018
Line 88:		Line 88:

	Please note that these versions of Dynamics CRM will have limited functionality. The majority of our development is done in a Dynamics CRM 8.1 environment and new features in these new environments are not reverse compatible.		Please note that these versions of Dynamics CRM will have limited functionality. The majority of our development is done in a Dynamics CRM 8.1 environment and new features in these new environments are not reverse compatible.


			==Legacy Form Rendering==
			Our solutions that function in the Dynamics CRM 2016 environment, or any version of Dynamics more recent than this version, require that the legacy form rendering option be turned off. You can find this option in your System Settings as pictured below. This is due to the fact that some of the methods our solutions use do not exist on the legacy forms for those specific solutions and may cause the solution to error.

			[[File:CRM_BP_LegacyFromRendering.png\|CRM_BP_LegacyFromRendering.png]]


	[[Category:Dynamics CRM]]		[[Category:Dynamics CRM]]

Admin at 00:13, 13 December 2017

2017-12-13T00:13:24Z

← Older revision		Revision as of 00:13, 13 December 2017
Line 73:		Line 73:

	Please note that checking override input will replace the appropriate fields from the service.		Please note that checking override input will replace the appropriate fields from the service.


			==Dynamics CRM Supported Versions==
			We support the following versions of Dynamics CRM:

			Dynamics CRM 2013 6.1
			Dynamics CRM 2015 7.0
			Dynamics CRM 2015 7.1
			Dynamics CRM 2016 8.0
			*Dynamics CRM 2016 8.1
			*Dynamics CRM 2016 8.2
			*Dynamics CRM Online
			*Dynamics 365

			Please note that these versions of Dynamics CRM will have limited functionality. The majority of our development is done in a Dynamics CRM 8.1 environment and new features in these new environments are not reverse compatible.


	[[Category:Dynamics CRM]]		[[Category:Dynamics CRM]]

Admin at 22:06, 13 September 2017

2017-09-13T22:06:20Z

← Older revision		Revision as of 22:06, 13 September 2017
Line 47:		Line 47:

	In order for our solution to function properly, please keep this field on the form.		In order for our solution to function properly, please keep this field on the form.


			==Input Fields==
			Our plugin generally takes advantage of the following out-of-box CRM fields:

			*Address 1: Line 1
			*Address 1: Line 2
			*Address 1: City
			*Address 1: State/Province
			*Address 1: Postal Code
			*Address 1: Country
			*Address 2: Line 1
			*Address 2: Line 2
			*Address 2: City
			*Address 2: State/Province
			*Address 2: Postal Code
			*Address 2: Country
			*Telephone1
			*MobilePhone
			*Email
			*Websiteurl
			*TicketSymbol
			*Number of Employees
			*Annual Revenue

			Please note that checking override input will replace the appropriate fields from the service.


	[[Category:Dynamics CRM]]		[[Category:Dynamics CRM]]

Admin at 21:19, 7 July 2017

2017-07-07T21:19:10Z

@@ Line 45: / Line 45: @@
 The current versions of the solutions all require the following field on the form:
 *Hide Button
 In order for our solution to function properly, please keep this field on the form.

Admin at 20:18, 7 July 2017

2017-07-07T20:18:21Z

← Older revision		Revision as of 20:18, 7 July 2017
Line 47:		Line 47:

	Here is an example of the Hide Button field on the Account form:		Here is an example of the Hide Button field on the Account form:
			[[File:Dynamics_BP_FormHideButton01.png\|link=]]


	Here are the details of the Hide Button field:		Here are the details of the Hide Button field:
			[[File:Dynamics_BP_FormHideButton02.png\|link=]]


			[[File:Dynamics_BP_FormHideButton03.png\|link=]]

Admin at 20:14, 7 July 2017

2017-07-07T20:14:22Z

@@ Line 38: / Line 38: @@
 *Order
 *Quote
 [[Category:Dynamics CRM]]

Admin: Created page with "← Dynamics CRM {{CustomTOC}} ==Installation== In order to guarantee that our solutions are behaving as intended, please only install one of our solutions..."

2017-05-04T21:40:13Z

Created page with "← Dynamics CRM {{CustomTOC}} ==Installation== In order to guarantee that our solutions are behaving as intended, please only install one of our solutions..."

New page

[[Dynamics CRM|← Dynamics CRM]]
{{CustomTOC}}
==Installation==
In order to guarantee that our solutions are behaving as intended, please only install one of our solutions at a time. We are working to allow for compatibility of installing more solutions at one time in order to help fit specific needs, but as of now, installation of only one solution at a time is recommended. If more than one solution is installed, the solutions may not function properly. If another solution is desired, please delete the solution from your Solution Explorer and import the desired solution. Please note, the information stored in our custom fields associated with the specified solution will be deleted when the solution is deleted.

*After installation of our solution, we recommend you publish all customizations immediately after the import is complete.
*We highly recommend that the solutions that are installed are always up to date with the latest version.

==Configuration==
Immediately after installation and publishing, the configuration entity must be set with an appropriate license before the solution is able to properly function. Please open the solution explorer, open our solution, and click Configuration to view the configuration options. When the options are set to the desired values, please click the “Set” button at the bottom of the configuration page.

==System Roles==
Our solutions require access to certain forms at installation. Most of our solutions may make changes to the following entities:

*Account
*Address
*Competitor
*Contact
*Invoice
*Lead
*Order
*Quote

In order to use our solutions, users will require at the very minimum read privileges to our custom configuration entities. In order to make changes to the entities, we recommend allowing users read and write privileges to the custom configuration entity.

==Form Customization==
We understand that Dynamics CRM allows for a large amount of customization especially with regards to the format of the form of each entity. Our solutions will run without issue on the main form, which is where our custom fields are stored. Currently, our solutions generally affect the main form of the following entities:

*Account
*Address
*Competitor
*Contact
*Invoice
*Lead
*Order
*Quote

[[Category:Dynamics CRM]]