Sage CRM 7.2 - Revision history

Crmtogetherkb at 07:46, 12 June 2013

2013-06-12T07:46:21Z

← Older revision		Revision as of 08:46, 12 June 2013
Line 17:		Line 17:
	----		----
	Component Manager is not scripting mutlitext fields correctly and they are created as nvarchars in sql. Requires running script and then running SQL to drop and recreate the tables as well as editing the custom_edits table to remove the max length limitation.		Component Manager is not scripting mutlitext fields correctly and they are created as nvarchars in sql. Requires running script and then running SQL to drop and recreate the tables as well as editing the custom_edits table to remove the max length limitation.

			----
			On tablet devices using the normal screen you cannot see the buttons on the RHS of the screen as scrolling has been disabled. CRMIO has a fix for this.

Crmtogetherkb at 16:14, 29 May 2013

2013-05-29T16:14:28Z

← Older revision		Revision as of 17:14, 29 May 2013
Line 4:		Line 4:

	If you are upgrading from a version prior to 7.2 the old system of generating ID fields stays the same		If you are upgrading from a version prior to 7.2 the old system of generating ID fields stays the same


			----

			Issue with date pickers on custom screens that scroll

			If you have a long screen that requires scrolling the date picker can appear off of the screen on custom pages.

			To resolve you must have these fields towards the top of the screen.


			----
			Component Manager is not scripting mutlitext fields correctly and they are created as nvarchars in sql. Requires running script and then running SQL to drop and recreate the tables as well as editing the custom_edits table to remove the max length limitation.

Crmtogetherkb at 08:07, 29 May 2013

2013-05-29T08:07:34Z

← Older revision		Revision as of 09:07, 29 May 2013
Line 3:		Line 3:
	ID fields: If you have a fresh install of CRM72 then the eware_get_identity_id stored procedure is no longer in the system.		ID fields: If you have a fresh install of CRM72 then the eware_get_identity_id stored procedure is no longer in the system.

	If you are upgrading ~~the~~ the old system of generating ID fields stays the same		If you are upgrading from a version prior to 7.2 the old system of generating ID fields stays the same

Crmtogetherkb at 08:07, 29 May 2013

2013-05-29T08:07:13Z

← Older revision		Revision as of 09:07, 29 May 2013
Line 1:		Line 1:
	~~Upgrading to~~ CRM 7.2		CRM 7.2

	~~1. The~~ eware_get_identity_id stored procedure is no longer in the system. ~~This may break any customisations~~ you ~~have using custom SQL or stored procedures.~~		ID fields: If you have a fresh install of CRM72 then the eware_get_identity_id stored procedure is no longer in the system.

			If you are upgrading the the old system of generating ID fields stays the same

Crmtogetherkb at 14:37, 30 January 2013

2013-01-30T14:37:43Z

← Older revision		Revision as of 15:37, 30 January 2013
Line 1:		Line 1:
	~~Upgradeing~~ to CRM 7.2		Upgrading to CRM 7.2

	1. The eware_get_identity_id stored procedure is no longer in the system. This may break any customisations you have using custom SQL or stored procedures.		1. The eware_get_identity_id stored procedure is no longer in the system. This may break any customisations you have using custom SQL or stored procedures.

Crmtogetherkb: Created page with "Upgradeing to CRM 7.2 1. The eware_get_identity_id stored procedure is no longer in the system. This may break any customisations you have using custom SQL or stored procedures."

2013-01-30T14:37:30Z

Created page with "Upgradeing to CRM 7.2 1. The eware_get_identity_id stored procedure is no longer in the system. This may break any customisations you have using custom SQL or stored procedures."

New page

Upgradeing to CRM 7.2

1. The eware_get_identity_id stored procedure is no longer in the system. This may break any customisations you have using custom SQL or stored procedures.