I’m new to Cloud and have asked the same question recently, @matt.watters.  I have so far received a variety of replies including one that advised the filtering logic was different depending on which screen you were in.  Some screenshots below which have also been passed to me. 

In this instance (Shop Orders), you have to ask “how recent” ...

This is the Customer Orders translation

Has this improved since you posted?  Can we harness the power of the collective community get a request/idea to IFS for some consistency on this, do you think?  It would get my ‘up-vote’.

Linda

In general, the purpose with this functionality is to increase performance by ignoring old “dead” records that is unlikely that you are interested in.

If you click (i) you can see a a more detailed explanation about the filter criteria applied when this is enabled.

Thanks for the tip, @Björn Hultgren, and the fact it is different depending on the screen (CO = 100 days, SO = 365 days).  Is there any reason for the difference, do you know?  

The current description we have in Customer Orders took me a couple of reads through before I got it.  I guess the translation aspect isn’t easy but I would have found “Invoiced/Closed” (in line with the actual status) easier to follow than “invoiced closed”

@PRODQ No I don’t think there’s any specific reason behind the different dates. It’s just up to the designer of the page to determine how old the data should be do be excluded with this toggle, may of course be different depending on the data, but might also be so that different designers just have taken different decisions.

How curiously ‘random’ to not have any standard policy/approach!  That’s going to be fun when training new users 

Thanks for engaging

Linda

In general, the purpose with this functionality is to increase performance by ignoring old “dead” records that is unlikely that you are interested in.

If you click (i) you can see a a more detailed explanation about the filter criteria applied when this is enabled.

 

I don’t understand why you would be searching for them if you weren’t interested in them?

Our users keep falling for this ‘feature’ on a regular basis. Apart from being annoying it’s more or a hindrance than a help.

E.g.

1. Shop Orders screen, search for a part
2. Three shop orders are returned
3. I want to look at the details of the oldest shop order
4. I select the line and click on shop order
5. A page loads with the correct search criteria but everything else on the screen is empty.
6. User A asks User B to try the same, then they get the same issue.
7. Then it gets reported to IT to investigate.

In summary it just wastes everyone's time and saves no ones time.

Can we default this to OFF for all users?

Thanks

Hi, 

In my company, users keeps complaining about this toggle. So I'm reacting to this comment because I have exactly the same question. Can we default this to OFF for all users ?

Thanks !!

Soumia

I have a user who could not see Shop Order Analysis records when they hopped from the Shop Order/Operation to the Analysis so thought the records had somehow been corrupted by IFS and our update to Cloud from Apps9.  They have for some while been logging in to a copy we have of our Apps9 environment to find the data they believed lost on old Shop Orders.  The data in question is a serial number etched onto the assembly at the point of Inspection - critical for warranty purposes.  

Is there any progress/respite/change/update/workaround where we can choose to switch this off?

Linda

While we appreciate IFS going for extra mile and getting such flexibility in the system, Also to note 
customers are finding it hard and confusing. Example, you RMB from Customer Order window to Invoice/s. Sometimes you find no records due to the 100 days filter applied by default, and then suddenly with the toggle you find all records. I think there is a save search functionality and companies can push default search options for performance affected forms. Please think of implementing and promoting such solutions (My suggestion for IFS). Also we noted different versions behaving differently with toggle on/off. Could this be explained as well?