Appointments - Revision history

Sagecrmw at 12:35, 20 March 2023

2023-03-20T12:35:39Z

← Older revision		Revision as of 13:35, 20 March 2023
Line 61:		Line 61:

	* Note: We mimicked how the Sage Exchange sync creates the records in CRM.		* Note: We mimicked how the Sage Exchange sync creates the records in CRM.

			----

			Limitations:

			1. Recurring appointments are not supported

2023-02-13T17:14:08Z

← Older revision		Revision as of 18:14, 13 February 2023
Line 3:		Line 3:
	-----		-----

	Users must link the ~~email~~ to store it into CRM. The system will only send these linked items to CRM and not all Outlook appointments. This is to allow the user privacy control over their appointments and what is stored in CRM.		Users must link the Appointment to store it into CRM. The system will only send these linked items to CRM and not all Outlook appointments. This is to allow the user privacy control over their appointments and what is stored in CRM.

	If the "New Appointment" menu item is clicked from the task pane then this will add in a link.		If the "New Appointment" menu item is clicked from the task pane then this will add in a link.

2023-02-13T12:58:49Z

← Older revision		Revision as of 13:58, 13 February 2023
Line 59:		Line 59:

	and you see those listed here.		and you see those listed here.

			* Note: We mimicked how the Sage Exchange sync creates the records in CRM.

2023-02-13T11:48:34Z

← Older revision		Revision as of 12:48, 13 February 2023
Line 42:		Line 42:
	[[File:apptsample1.png]]		[[File:apptsample1.png]]

	And we link this to CRM (1-search and select an entity) and then TAG it (2 and 3) against an entity		And we link this to CRM (1-search and select an entity) and then TAG it (2 and 3) against an entity.

			* Note: If no TAG is set then there will be no primary company/person set

	[[File:apptsample2.png]]		[[File:apptsample2.png]]

2023-02-13T11:43:57Z

← Older revision		Revision as of 12:43, 13 February 2023
Line 42:		Line 42:
	[[File:apptsample1.png]]		[[File:apptsample1.png]]

			And we link this to CRM (1-search and select an entity) and then TAG it (2 and 3) against an entity

	[[File:apptsample2.png]]		[[File:apptsample2.png]]

			This makes the banner yellow (1) and inserts a tag (2)

	[[File:apptsample3.png]]		[[File:apptsample3.png]]

			Then send or save the outlook meeting as normal and within CRM the Tagged item is the main CRM entity (1 and 2).

			Click on External Attendees (3) then

	[[File:apptsample4.png]]		[[File:apptsample4.png]]

			and you see those listed here.

2023-02-13T11:38:06Z

← Older revision		Revision as of 12:38, 13 February 2023
Line 33:		Line 33:
	8a0c2af9-fc60-439d-be58-42f2415d467e		8a0c2af9-fc60-439d-be58-42f2415d467e
	is used to identity the record in CRM. This is stored in the "comm_outlookEntryID" field		is used to identity the record in CRM. This is stored in the "comm_outlookEntryID" field

			-----

			How the data is reflected in CRM.

			So if we create a sample outlook item

			[[File:apptsample1.png]]


			[[File:apptsample2.png]]


			[[File:apptsample3.png]]


			[[File:apptsample4.png]]

2021-06-16T10:56:34Z

← Older revision		Revision as of 11:56, 16 June 2021
Line 1:		Line 1:
			This feature is not applicable to the Office365 manifest integration due to limitations of the API currently in use there.

			-----

	Users must link the email to store it into CRM. The system will only send these linked items to CRM and not all Outlook appointments. This is to allow the user privacy control over their appointments and what is stored in CRM.		Users must link the email to store it into CRM. The system will only send these linked items to CRM and not all Outlook appointments. This is to allow the user privacy control over their appointments and what is stored in CRM.

2021-06-15T10:58:12Z

← Older revision		Revision as of 11:58, 15 June 2021
Line 5:		Line 5:
	[[File:apptnew1.jpg]]		[[File:apptnew1.jpg]]

	In this case the link to CRM and a TAG will be added		In this case the link to CRM and an Entity TAG will be added

	[[File:apptnew2.jpg]]		[[File:apptnew2.jpg]]

2021-06-15T10:57:44Z

← Older revision		Revision as of 11:57, 15 June 2021
Line 20:		Line 20:
	Here is an example tag.		Here is an example tag.

	****Powered by CRMTogether.com**8a0c2af9-fc60-439d-be58-42f2415d467e**demo.crmtogether.com****Do not Remove		****Powered by CRMTogether.com**8a0c2af9-fc60-439d-be58-42f2415d467e**demo.crmtogether.com****Do not Remove

	The section		The section

2021-06-15T10:57:25Z

← Older revision		Revision as of 11:57, 15 June 2021
Line 14:		Line 14:

	Within CRM itself the record will be created also setting any external attendees. Other CRM users will be identified by their email addresses.		Within CRM itself the record will be created also setting any external attendees. Other CRM users will be identified by their email addresses.


			The Appointment TAG

			Here is an example tag.

			****Powered by CRMTogether.com**8a0c2af9-fc60-439d-be58-42f2415d467e**demo.crmtogether.com****Do not Remove

			The section
			demo.crmtogether.com
			is used to make sure it is this tag is from the correct server.

			The number
			8a0c2af9-fc60-439d-be58-42f2415d467e
			is used to identity the record in CRM. This is stored in the "comm_outlookEntryID" field