When logging into GMME: Cases are not available in the currently open database.
To use Cases, log in to GoldMine Premium Edition on the server used for GoldMine Mobile Edition and open the (xxx.dbo) database.
[STEPS TO REPRODUCE]
1. Browse the GoldMine Mobile web site (usually http://servername/goldmine)
2. Log in as the user having access to GoldMine Mobile
A message appears
'Cases are not available in the currently open database. To use Cases, log in to GoldMine Premium Edition on the server used for GoldMine Mobile Edition and open the xyz.dbo) database.'
[CAUSE]- Within GoldMine, several Contact Sets can be used and opened by users via Tools > Databases > Open Database when they are made available.
Typical examples for such scenarios are the main contact set and an archive contact set.
- The Service Center / Cases feature within GoldMine is only available within the main contact set, means the same database where the contact tables (CONTACT1, CONTACT2, etc) and also the GoldMine Base tables reside (CAL, OPMGR, MAILBOX etc), so it will not be available in any other contact sets.
- Once the user has a different Contact Set opened than this main contact set and tries to access the Service Center (via Go To >> Service Center or via the left bottom navigation pane icon Service) a message appears within GoldMine
'GoldMine has detected that the current Contact Set "Archive:" is different from the main GoldMine database "GMPE201410412LargeUSDemo:".
The Service Module requires the Contact Set to have the same alias and be in the same database as the main GoldMine database tables.
Please go to Tools >> Databases >> Open Database" and open the Contact Set "GMPE201410412LargeUSDemo:" in order to use Service Module.'
- The same applies to GoldMine Mobile and almost the same message appears when logging into GoldMine Mobile due the same reason.
- The current opened contact set within GoldMine Mobile is also the last opened Contact Set database (from the USER.INI > COMMONDIR entry) if the user never opened the GoldMine windows client or the USER.INI's COMMONDIR entry was removed then the COMMONDIR entry from the GM.INI is used instead.
[RESOLUTION]- Although it would be possible to work further with GoldMine Mobile but not using the Cases module, many times even the user does not really want to work in the different contact set within GoldMine Mobile.
- In order to change this ‘for’ the GoldMine Mobile client
1. Make sure to be logged out of GoldMine Mobile
2. Log into GoldMine Premium Edition as the specific user
3. Tools > Databases > Open Database
4. Highlight the main Contact set database
Note: If the user is unsure, the alias can be verified prior to performing this steps via Help > About GoldMine > System Button > Alias - in the row GoldMine Files
5. Open via double click or button Open
6. Close GoldMine Premium Edition.
7. Log into GoldMine Mobile and verify again
- While it was a common and necessary practice in very old versions of GoldMine (lower than GoldMine 6.5) to have several contact sets for different contact types like customers and suppliers, today usually different contact sets are only used for archiving purposes, this means contacts which are moved out to the active contact set as they are not valid anymore but the information should not be deleted. In order to use and setup different types of contact records within GoldMine, GoldMine contains a feature called Record Typing where per contact record type fields can contain different labels, the default views are different, so that different contact set databases are not necessary anymore.
- Many areas of GoldMine work with different Contact Sets properly but for example
a. When opening Case / Service Management a message appears 'GoldMine has detected that the current Contact Set xyz: is different from the main GoldMine database....'
b. Setup Outlook integration will also refer to the originally set Contact Set and if this should be changed a new 'Read GoldMine Settings' for the Outlook Integration would be necessary