Type Mismatch Error in the History Tab of the Info Sheet

Type Mismatch Error in the History Tab of the Info Sheet

PROBLEM

  • When going into the Info Sheet, you get a “Type Mismatch” error.

CAUSE

This is caused by the History containing too many items and Gorilla not being able to sort them all.

SOLUTION

To get past this, you just need to filter out some of the History.

Most offices don't need more than the last year viewable at any time, so it is recommended to change the filter to only show the last years’ worth of content.  This should keep the error from occurring.




    • Related Articles

    • Info Sheet - Keywords Tab

      QUESTIONS THAT APPLY TO THIS TOPIC What is the Keywords tab? What can I use the Keywords tab for? What information can I get from the Keywords tab? What actions can I do from the Keywords tab?  ANSWERThe Info Sheet’s keywords tab provides information ...
    • Type Mismatch Error on Login

      PROBLEM After clicking “OK” on Gorilla login screen, you get a “Program error intercepted: ‘type mismatch’” error. SOLUTIONYou will need to send your database in for repair. Call Software Support at 801-553-9888 for assistance with sending in your ...
    • Type Mismatch Error during Import

      PROBLEM When importing a list or a Campaign, you get a “Type Mismatch” error. CAUSE This is usually caused by importing the wrong file type or trying to import a zipped file. SOLUTION Campaigns If the Campaign downloaded came in a compressed (zipped) ...
    • History Missing from the Tree View of the Info Sheet

      PROBLEM When viewing History items in the Info Sheet, some of the items only appear in the List View and not in the Tree View. CAUSE This can occur if you change the due date for a folder History item within the Scheduler instead of through the Info ...
    • Type Mismatch when Adding a New Opportunity

      PROBLEM When adding a new Opportunity to a Contact Group in Gorilla®, you receive the message "Type Mismatch" and the Due Date for the Opportunity only shows as being 12:00 AM. CAUSE This is caused by the Region and Language settings being set to a ...