What causes the database to update fields to "Index Maximal"

[notmybag]

I am using Fmdiff to compare 9.0 versions of the database for SOXA change control. Several fields have shown up with a change from nothing to Index Maximal. I'm trying to figure out what would have triggered the change and what it is? Pardon me, but I am fairly new to FM. Any ideas? Thanks in advance.

[Vaughan]

A field will be indexed if it is used in a find, or if it's used in a relationship.

[notmybag]

So, even if we did not set the field to be indexed are you saying that FM will set it automatically if it deems it necessary? In one case the field had an index, but it showed the change and in the other two cases there it was not set at all. (I have to explain the changes since these were not directly touched by the team.) Thanks again,

[Vaughan]

"So, even if we did not set the field to be indexed are you saying that FM will set it automatically if it deems it necessary?"

Yes.

By default, field indexing is set to "none" with "automatically index as needed" selected. That way, if a field is used in a find (or used for a relationship) it will get indexed.

[notmybag]

Thanks for your info, that helps explain the reporting.