[kspitler]

HELP!!!
Our Gift Entry person is trying to enter gifts and keeps getting the following error message "Invalid Campaign: Campaign ID"

I have checked that the campaign ID is active. Also I was able to enter the gift with no problems.

It appears that when entering in batch that as she tabs over the Campaign ID field changes from numbers to the description. It does not happen to all gifts just a select few.

Is there something I missed?

[Witch]

If she is using defaults, make sure they did not get changed somehow. You can see them on the first line.

I have had something similar happen with my data entry people and this was the problem at that time.

[kspitler]

The default for Campagin ID is empty, but the original pledge (they have all been pledge payments) fill in the field automatically.

[Tom Mills]

Sounds like a Security issue, since you can do it.....

[kspitler]

It works fine when I log in as her on my computer.

[Peter Gulka]

check the campaign record to see if it is restricting input from certain funds only.

[kspitler]

No funds are listed

[Melissa Siobhan]

Data entry in batch for campaign, fund and appeal are determined to either be ID or Description based on user options. Your user options may be different than your DE person. Could this be the problem?

Check the user options under records to see if they are set to be description or ID and change it to whatever your DE person prefers to use.

I HATE that it is done this way because we prefer to data enter based on ID but report based on description and both are determined by this same user option. We need to remember to change it back and forth.

[DrewAllen]

Quote:

Originally Posted by Melissa Siobhan

Data entry in batch for campaign, fund and appeal are determined to either be ID or Description based on user options. Your user options may be different than your DE person. Could this be the problem?

Check the user options under records to see if they are set to be description or ID and change it to whatever your DE person prefers to use.

I HATE that it is done this way because we prefer to data enter based on ID but report based on description and both are determined by this same user option. We need to remember to change it back and forth.

In addition, I think that the user options are stored locally, so they don't carry over from one workstation to another, so the same user can have different options set on different computers.

It should be fairly easy to have the lookup use both the ID and the Description. Since the ID is (or should be) indexed, it can do an indexed lookup on the ID. If it doesn't find it under the ID, then it can scan for the Description. Millennium uses this method in looking up constituents.

Drew

[ida]

Are you sure user options are stored locally? You can change other people's user options from your own pc in security...

[kspitler]

To give all an update on the situation.

After trying everything I could IT came in and "reburned the image" on her desktop and then did other IT magical things and it seems to be working.


For now that is....

[DrewAllen]

Quote:

Originally Posted by ida

Are you sure user options are stored locally? You can change other people's user options from your own pc in security...

I know that there are some things that are stored locally, I just can't remember what they all are. For instance, the list of most recently accessed records is stored locally.

Drew