Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

v3.0 - updating a field based on another field

v3.0 - updating a field based on another field

v3.0 - updating a field based on another field

My company purchased an add-on package. There is a field in Accounts that uses javascript to hide some sections on the form based on this yes/no field. We actually require three choices, but two of the choices should yield the same form view as the yes option.
Since we're not 100% sure that this field doesn't drive any other events, we would like a way to update this field with a yes or no value based on the choice made in a new field we would create on the form.

Is there a way to update a field easily based on the choices made in another field? js in the onChange event for our new field? (i'm not a js guy, but we have one available).


Braccae tuae aperiuntur...

RE: v3.0 - updating a field based on another field

You could easily put it in a trigger on the DB - BUT OFFICIALLY MS does not like people messing around in the DB

I do it all the time since it is worth any risk of them not supporting us to have the data as we need it.

make sense?

RE: v3.0 - updating a field based on another field

Excellent idea that I considered as I've been accused of being trigger happy for years. My real worry was getting the form to change based on that first field being changed by my new field. I couldn't get the onChange event to actually fire, but was looking into it further. The builders of the add-on wired a lot of stuff into the value of that field and unfortunately it's not just a yes/no thing.

Our installation partner actually wrote MS's book on CRM, and their was some examples in there showing the setfocus and fireonchange methods that i was going toexplore further, but they went back to the builder and got them to agree to build an extra field that suits our needs (and will be their problem come upgrade/support time).

Thanks as always all who pondered this.


Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close