AC Lite Guide - Revision history

Sagecrmw at 08:01, 29 August 2025

2025-08-29T08:01:14Z

← Older revision		Revision as of 09:01, 29 August 2025
Line 1:		Line 1:
	'''Accelerator Lite Edition'''		'''Accelerator Lite Edition'''

	This edition of Accelerator (AC) has no server side install and ~~only~~ requires the AC Lite Client.		This edition of Accelerator (AC) has only a simple Sage CRM Component server side install and requires the AC Lite Client.

			The AC Lite Client is now available in Classic and the Microsoft appsource store. For the Microsoft appsource store CRM is required to be accessible from https and externally.

	For 365 see [https://accelerator.crmtogether.com/index.php?title=Install_ACLite_on_Microsoft365 Install on 365].		For 365 see [https://accelerator.crmtogether.com/index.php?title=Install_ACLite_on_Microsoft365 Install on 365].

Sagecrmw at 13:01, 16 June 2025

2025-06-16T13:01:24Z

← Older revision		Revision as of 14:01, 16 June 2025
Line 2:		Line 2:

	This edition of Accelerator (AC) has no server side install and only requires the AC Lite Client.		This edition of Accelerator (AC) has no server side install and only requires the AC Lite Client.

			For 365 see [https://accelerator.crmtogether.com/index.php?title=Install_ACLite_on_Microsoft365 Install on 365].

	View a comparison sheet at [https://crmtogether.com/accelerator-pro-vs-lite/?utm_source=aclite&utm_medium=achelp&utm_campaign=achelp&utm_id=fromhelp AC Pro Vs AC Lite here]]		View a comparison sheet at [https://crmtogether.com/accelerator-pro-vs-lite/?utm_source=aclite&utm_medium=achelp&utm_campaign=achelp&utm_id=fromhelp AC Pro Vs AC Lite here]]

Sagecrmw at 08:59, 8 April 2024

2024-04-08T08:59:08Z

← Older revision		Revision as of 09:59, 8 April 2024
Line 223:		Line 223:
	If you find that the Entity search is not working you may need to fix a corrupt index as per Sage's own documentation		If you find that the Entity search is not working you may need to fix a corrupt index as per Sage's own documentation

	[https://help.sagecrm.com/on_premise/en/2023R2/Administration/Content/Troubleshooting/TS_RecreatingQuickFindIndex.htm]		[https://help.sagecrm.com/on_premise/en/2023R2/Administration/Content/Troubleshooting/TS_RecreatingQuickFindIndex.htm 'Rebuilding the Quick Find index']

Sagecrmw at 08:58, 8 April 2024

2024-04-08T08:58:43Z

← Older revision		Revision as of 09:58, 8 April 2024
Line 216:		Line 216:
	* Person: order by pers_lastname asc		* Person: order by pers_lastname asc
	* Communications: order by comm_createddate desc		* Communications: order by comm_createddate desc

			----

			'''Quick Find/Search not working'''

			If you find that the Entity search is not working you may need to fix a corrupt index as per Sage's own documentation

			[https://help.sagecrm.com/on_premise/en/2023R2/Administration/Content/Troubleshooting/TS_RecreatingQuickFindIndex.htm]

Sagecrmw at 09:05, 19 July 2023

2023-07-19T09:05:26Z

← Older revision		Revision as of 10:05, 19 July 2023
Line 210:		Line 210:
	----		----

	Data displayed in Tabs (Opportunity/Case/etc lists within the context of an Entity (not the search) are ordered as follows		Data displayed in Tabs (Opportunity/Case/etc) lists within the context of an Entity (not the search) are ordered as follows

	* Opportunity: order by oppo_createddate desc		* Opportunity: order by oppo_createddate desc

Sagecrmw at 09:04, 19 July 2023

2023-07-19T09:04:50Z

← Older revision		Revision as of 10:04, 19 July 2023
Line 207:		Line 207:

	libr_active: "Y"		libr_active: "Y"

			----

			Data displayed in Tabs (Opportunity/Case/etc lists within the context of an Entity (not the search) are ordered as follows

			* Opportunity: order by oppo_createddate desc
			* Cases: order by case_createddate desc
			* Person: order by pers_lastname asc
			* Communications: order by comm_createddate desc

Sagecrmw at 10:52, 13 July 2023

2023-07-13T10:52:18Z

← Older revision		Revision as of 11:52, 13 July 2023
Line 180:		Line 180:
	----		----

	Communications - Required fields at table level		Communications/Documents - Required fields at table level

	If you have any fields required at the table level this wil prevent Emails from being saved.		If you have any fields required at the table level this wil prevent Emails from being saved.

Sagecrmw at 10:51, 13 July 2023

2023-07-13T10:51:29Z

← Older revision		Revision as of 11:51, 13 July 2023
Line 58:		Line 58:
	e. Users emails are set up in Sage CRM against their CRM user.		e. Users emails are set up in Sage CRM against their CRM user.

	f. There are no required fields against the communication/comm_link tables within CRM at the entity level.		f. There are no required (or Readonly) fields against the communication/comm_link tables within CRM at the entity level.

			g. There are no required (or Readonly) fields against the Library (Documents) tables within CRM at the entity level.

	In newer versions of Sage CRM you can check these from within the Sage CRM application itself.		In newer versions of Sage CRM you can check these from within the Sage CRM application itself.
Line 186:		Line 188:
	When Communications(emails) and Library(attachments) records are saved certain default (hard coded) values are set. Some of these default values are based on selection lists so if they have been altered this will affect if/how the value is displayed.		When Communications(emails) and Library(attachments) records are saved certain default (hard coded) values are set. Some of these default values are based on selection lists so if they have been altered this will affect if/how the value is displayed.

	* Communications		* Communications (none of these fields should be set to READONLY)

	Comm_priority: "Normal"		Comm_priority: "Normal"
Line 198:		Line 200:
	* NOTE: Really for Emails (in/out) they should be set as "Email" and not "Task" but the CRM REST API does not allow this currently		* NOTE: Really for Emails (in/out) they should be set as "Email" and not "Task" but the CRM REST API does not allow this currently

	* Library		* Library (none of these fields should be set to READONLY)

	libr_type: "EmailAttachment"		libr_type: "EmailAttachment"

Sagecrmw at 10:49, 13 July 2023

2023-07-13T10:49:25Z

← Older revision		Revision as of 11:49, 13 July 2023
Line 4:		Line 4:

	View a comparison sheet at [https://crmtogether.com/accelerator-pro-vs-lite/?utm_source=aclite&utm_medium=achelp&utm_campaign=achelp&utm_id=fromhelp AC Pro Vs AC Lite here]]		View a comparison sheet at [https://crmtogether.com/accelerator-pro-vs-lite/?utm_source=aclite&utm_medium=achelp&utm_campaign=achelp&utm_id=fromhelp AC Pro Vs AC Lite here]]

			* Note that Accelerator Lite is only recommended for simple non-heavily customised systems as the screens cannot be customised. It is mainly to allow you file emails against an entity.

	A Sage CRM component install is required to allow email attachments be uploaded.		A Sage CRM component install is required to allow email attachments be uploaded.

Sagecrmw at 11:59, 5 July 2023

2023-07-05T11:59:56Z

← Older revision		Revision as of 12:59, 5 July 2023
Line 193:		Line 193:

	Comm_Type: "Task"		Comm_Type: "Task"

			* NOTE: Really for Emails (in/out) they should be set as "Email" and not "Task" but the CRM REST API does not allow this currently

	* Library		* Library