8 Replies Latest reply on Oct 14, 2016 2:19 PM by David Moyer

# How to create a field that will input the largest number from 9 other fields

Hi all,

Hoping to create a field that will look at 9 specific fields, determine the largest number, and put it into the field.

Any ideas?

Thanks!

• ###### 1. Re: How to create a field that will input the largest number from 9 other fields

Look at the Max() function.

You can use it either in a Calculation field, or as an Auto-Enter calculation for a field.

1 of 1 people found this helpful
• ###### 2. Re: How to create a field that will input the largest number from 9 other fields

thank you!

• ###### 3. Re: How to create a field that will input the largest number from 9 other fields

Sounds like a homework problem.

• ###### 4. Re: How to create a field that will input the largest number from 9 other fields

Nine different fields walk into a bar, the bartender, Max, says ...

• ###### 5. Re: How to create a field that will input the largest number from 9 other fields

On a serious note, I wonder why you have nine different fields (data points) to evaluate.  Are they all in the same table?  As an FYI, the Max function also works with related data ... e.g. Max ( RelatedTable::dataPointValue )

• ###### 6. Re: How to create a field that will input the largest number from 9 other fields

basically the 9 fields are scores for each record and i want a field that will tell me the high score without looking

thanks everyone!

• ###### 7. Re: How to create a field that will input the largest number from 9 other fields

At least it's not an eigenvector problem with a 5x5!

Phew!

• ###### 8. Re: How to create a field that will input the largest number from 9 other fields

The Max ( field1; field2; etc. ) will work for you as you require. (Max(repeating field) will also work.)

However, many of the experts here would suggest that your data model is wonky in that you should have a separate table for your nine scores, related to a parent record.

It's not a simple improvement/solution; but if your tables get very large, you should consider it.