forcing a field to reindex

[silver_surfer]

Hi

Does anyone know how to force FM to reindex an indexed field?

I want to create a key that points at either the date in the record or if the record in over due to point to today. As today's date is an unstored calc, I had to use a getField() in the key so that FM will index it. This worked but now it won't update itself (ie today's date) as it is stored in the index.

Any ideas?

Thanks

[comment]

Well, yes - it cannot be indexed if it's not stored, and if it's stored it will not update. Try moving the unstored current date to the left side of the relationship.

[silver_surfer]

I am aware of that. That's why I was asking about the reindex. I need the key on the right so that it will appear in a portal of the users tasks for today

[comment]

The conclusion does not follow from the given. If you have a relationship:

cToday => TaskDueDate

the portal will show today's and past due tasks. cToday is an unstored calculation of Get (CurrentDate).

You will need to add another criterion to the relationship to filter out completed tasks, or create a calculation field =

Case (IsEmpty ( CompletionDate ) ; TaskDueDate )

and use that in the relationship instead of TaskDueDate.

[silver_surfer]

cool sounds like a good option, will give it a go.

thanks

[silver_surfer]

that nearly fixed it just needed to stop it picking up the blank field values from Case (IsEmpty ( CompletionDate ) ; TaskDueDate ) in cToday => TaskDueDate Rel

and it did the trick.

[comment]

Ah, yes - a blank is smaller than today. Should have been:

Case ( IsEmpty ( CompletionDate ) ; TaskDueDate ; Date ( 12 ; 31 ; 4000 ) )