TeamScope CRM Reporter Revision History
2/14/07 v5.0.101
· Added Workgroup functionality
xRunLog added "Workgroup"
xFolderStatus added “Workgroup”
· Added "Shared Workgroup" to xConfig which is then set in the Options. Default is <blank>
· Added “TimeStamp Offset” to xConfig which allows for time to be offset from the LastRun time for each folder to make sure that any recent edits are pickup up. Default is 15 mins. This value in not in the Options.
· Added requirement for "CreationTime" for all Data tables as defined in xFieldMapDef
· Fixed bug when only 1 item was in a folder it would not be recorded
· Status now always scrolls down to show latest status
· Updated help: Workgroups, Launching Reports, Creating Reports, Security tips
· Tested on Vista and Office 2007
12/26/06 v5.0.2
· Removed "Full Sync" checkbox. Data Transfer now always runs this as has been the default.
· Fixed repeating "Projects" field issue if one was using the original MDB from the prior version. Not an issue with the revised MDB that is shipping.
· Added check in CRM config for ReportDatabaseFileFolder location. If that is blank then it will use the basic App.Path
· Also now checks for proper MDB connection state. Prior version just returned what appeared to be a blank DB if the connection was bad.
· Updated help that shows how to "upsize" to SQL server.
· Help has been updated (See revision history)
12/01/06 v5.0.1
· Support for new 5.0 Project data format
· "Projects" keyword field automatically added to each Table/Folder. Name of field is set by the "ReferenceField" in the Projects options.
· Unfortunately this means that all of your MDB data needs to be retransferred so there is little need for any data compatibility
· Consider importing xCustomFields, custom Queries and Reports as needed if you made any changes to the prior MDB file
· Other minor fixes
6/16/06 v4.0.0.9
· Added code to generate normalized "Activities:Categories" table
6/13/06 v4.0.8.1
· Fixed "OutlookCRM" references in the VB code within the MDB
6/07/06 v4.0.8
·
Added MDB
compatibility so that existing users will be automatically upgraded so they can
keep their old database.
(Note that the Reports form that the user gets will still say "OutlookCRM
Reports". It is easy for the User/Admin to change but not easy to do
programmatically it turns out)
· List of Data Changes (automatic) for new version
xFolderStatus
Can (should) now be empty and it will be filled automatically
xCustomFields (added)
ID Name Type Folder Description
18 Action olText Email The type of Email. Simiar to the Type (Action) field in a Journal
xFieldMapDef (Added)
ID Folder Field Required Default
122 Projects CreationTime No No
123 Projects StartDate No Yes
124 Projects Status No Yes
125 Tasks StartDate No Yes
126 Tasks Status No Yes
128 Tasks CreationTime No No
129 Calendar Organizer No Yes
130 Email ReceivedTime No Yes
131 Email SentOn Yes Yes
133 Email Action No Yes
134 Email To Yes Yes
135 Email Companies Yes Yes
xLookup (new table)
Table Field ValueIn ValueOut
Tasks Importance 0 Low
Tasks Importance 1 Medium
Tasks Importance 2 High
Email Flag 0 None
Email Flag 1 Complete
Email Flag 2 Marked
Email Sensitivity 0 Normal
Email Sensitivity 1 Personal
Email Sensitivity 2 Private
Email Sensitivity 3 Confidential
Tasks Status 0 Not Started
Tasks Status 1 In Progress
Tasks Status 2 Complete
Tasks Status 3 Waiting
Tasks Status 4 Deferred
xOutlookFields (added)
ID Name Class ReadOnly Type Include Description Version Display,CanQuery,IsProperty,SpecialProperty,BaseField
1029 Companies IPM.Note No olText No Used for link to the CRM User item 2000 No No No No
xRunLog (Added two new columns - for better error logging)
Field Name Data Type
Folder Text
Item Hyperlink
xSyncErrors (not used anymore)
5/25/06 v4.0.6
· Error logging option now allows for error to just be logged and not reported via a dialog
· New combined Activities table - combines all tables into one (not just Journal and E-mail)
·
New optional
Lookup (off by default) allows for numeric values to be replaced with human
values. For instance Task.Status = "Complete" instead of
"2"
(User must manually change the data type in their tables if they want to use
this feature)
· New Auto Trim option now allows for the data to be trimmed without any warning
· New options dialog for new options
3/27/06 v4.0.X
· Error logging now writes out to Outlook with GUID links to items - Access Application is no longer launched
· Improved error diagnostics/handling
· E-mail History and Journal aggregate table is now put into a common "Activities" table
· Renamed to "TeamScope CRM Reporter"
8/27/05 v4.0.X
· Fixed very nasty issue where the folder selection grid was still enabled while the program was running. You could easily select a folder while another was running which would cause a number of problems.
8/21/05 v4.0.5
· New startup dialog offers to automatically build all the tables, load the data and set the categories
· Error handling in the Reporter form in Access - empty tables and other issues give a nice message as to what is missing
· Custom fields for Opportunity reports were not set to be included by default - updated xFieldDef table
· Projected Revenue, Sales Cycle Stage, Probability, Adjusted Revenue
· Added/fixed olCurrency data type in xCustomFields
· Field mapping form was not properly handling custom fields automatically to be included
· Esc (cancel) now cancels all transfers as opposed to just the current one.
· Fixed issues with other support forms potentially falling behind main window.
· MDB and Help updated.
7/28/05 v4.0.2
· Compiled for OL 2000 and up
· MDB updated per changes below
5/31/05 v4.0.?
·
Added support
for new E-mail History folder.
Data Transfer tool EXE updated
xOutlookField: add EntryID for IPM.Note
xFolderStatus: add "Email"
xMapFieldDef: add various defaults that are needed
5/1/05 v3.3.10
· Fixed bug in Main.FRM in the the Update Keywords module. Removed the n>0 check which was preventing lookup tables from being created
· Also fixed the MDB to set the "Contact Type" to olKeywords instead of olText in the xCustomFields table.
1/27/05 v3.3.9
· Cleaned out M:1 and Categories starter tables that are not needed in the MDB. Not a problem but potentially confusing to users.
· Imporved the Map fields dialog: Form resizes, colums can resize, changes to selections are properly saved in all cases.
1/21/05 v3.3.8
· Added size checking for fields mapped to standard text fields (255 max) so that they can get trimmed to fit and then continue on if desired.
· Improved status during Keywords build
· Added olCurrency data type to Custom Fields dialog
· Fixed Field Mapping dialog focus issue related to security pop-up
11/13/2004 ======================= Help 3.0.b updated "3.0" release =================
9/11/04 v3.3.4
· Support for missing olFolderNotes and just use "Notes"
· Added GetItem check for Outlook.Application
· Fixed issue with Keywords table creation
8/02/04 v3.2.1
· Some minor but important fixes to some error handling cases
· Added CreationTime to defaults in Leads and Contact of the xFieldMapDef
|
ID |
Folder |
Field |
Required |
Default |
|
106 |
Leads |
CreationTime |
Yes |
Yes |
|
107 |
Contacts |
CreationTime |
Yes |
Yes |
7/16/04 v3.2.0
· Added automatic creation of Category and Keyword break out M:1 tables.
·
Dramatic
improvement in duplicate item cleanup speed
(requires EntryID index to any existing tables)
· Added pseudo olTextMemo type for custom fields to have them map to Access Memo fields
ID Name Type Num OL Type DAO Mapping ADO Mapping
78 olTextMemo 1 Yes 10 203
· Categories and Keyword fields are now defaulted to Memo types
6/14/04 v3.1.0
· Added ability to allow for missing fields to continue or cancel transfer. This is to allow for multiple forms in a single folder with different fields ... like in a Project.
5/19/04 v3.0.2
· Fixed issue to properly set defaults for custom fields in xFieldMapDef
5/09/04 v3.0.1
· Fixed some 3.0 bugs that were stopping proper data transfer for anything other than IPM.Contacts
3/29/04 v3.0.0
· Improved support for custom fields. New custom field table editor and support for defining required custom fields.
· xFieldTypes Table: olKeywords are mapped to Access "Memo" fields
ID Name Type Num OL Type DAO Mapping ADO Mapping
12 olKeywords 11 Yes 10 203 (was 202)
11/12/2003 v2.0.21
·End fix for OL2003. Reporter would remain in tasks even after it was closed.
8/31/2003 v2.0.20
·Fixed update bug in OL 2003 (possibly 2002 also).
·New Jet ADO causes error in update of record related to StoreID > 255 and was not saving record at all. Removed updating the field as it is not acually needed anyways.
·Fixed issue with expired license and registration form not being displayed
8/9/2003 v2.0.19
·Added menu hook for Reference Guide CHM
8/1/2003 v2.0.18
·Fix for Full Index Check when running on PST files.
^^(This would typically be a rare situation... but then its Steve Dittmar who ran into this.)
5/14/2003 v2.0.17
·Had a rather nasty date bug that I introduced in the last version.
5/9/2003 v2.0.13
·Fixed some date formatting issues (similar to international issues)
·Now display xSyncError table as needed
·Fixed reset time ... now 7 days in the past, not 7 days in the future!!!
5/1/2003 v2.0.12
·CDO is no longer required. New TeamScopeSupport with Tables is required.
·Currently the help is not avaiable ... will try and make something this weekend.
·Only 1 or 2 reports are currently in the MDB but the UI framework is there.