Showing posts with label Sage Pastel Evolution. Show all posts
Showing posts with label Sage Pastel Evolution. Show all posts

Friday, 19 September 2014

Sage Evolution Job Costing: Error Loading Template - "QryARFind: Field 'iCurrencyID' not found"


This error pops up when a particular user in Sage Evolution attempts loading a template in the Job Costing module and persists until Evolution is restarted.

If other users can load templates without getting the error on the same workstation, a solution would be to delete the problem user from the registry.

Nb: The windows registry contains sensitive info needed for the proper functioning of your computer. You may take a backup of the registry before making any changes or get someone who is more technically apt, to help you with the steps below:

You do this by following the steps below:


1. On the workstation, Start "Run" and type "Regedit"




2. From the Registry Editor, Open the folder HKey Current User | User | Software | Softline | Evolution | Agents

3. Select and delete the folder for the problem user (Rosemary, in my case)



4. Once this is done, close the Registry Editor and re-login with the user's credentials. The problem should be resolved.

5. Note that this resets any custom settings such as printer layouts and custom grid views for that particular and must be reset where applicable.


3
Share:

Monday, 19 May 2014

Sage Evolution "Error Initialising Report Data" when running Accounts Payable Age Analysis


The above error may be encountered when a user tries running the Accounts Payable Age Analysis report in Sage Pastel Evolution.

The first probable cause of this error may be that a custom layout is being used. Corruption in the custom layout may throw this error.

If a custom layout is being used, you may try previewing the report using a standard layout to see if the error still pops up. If it doesn't, then you can be sure that the error is from the custom layout. You may then review the design and code of the custom layout to isolate the cause of the error.

In the unlikely event that the error still pops up, you may remedy this by creating a new evolution common database and linking it to the company. Any customizations may then be redone.

Share: