Skip to main content
Solved

setup "prompt (Services)" : parameter "Enable Use of Obsolete Products"

  • September 16, 2025
  • 4 replies
  • 59 views

Forum|alt.badge.img+7
  • Sidekick (Partner)

Hi, in the setup "prompt (Services)", if the parameter "Enable Use of Obsolete Products" is switched OFF then if the user wants to add an obsolete product in a Demand Material of a service order, Alliance send him a message that he can’t use an obsolete product. When the user add a new Demand Material in a Service order and he enters the beginning of a product Id in the “Product Id” field, Alliance shows obsolete and non obsolete products. Is there a way to eliminate those obsolete products directly in this list showed to the user ?

Thanks by advance

Best answer by Phil Seifert

Hi Philippe,

This functionality is not supported as standard for the quick lookup dropdown list when inserting values used for lookup. While the lookup dialog screens offer more filtering options, the dropdown list is intended solely for quick value selection. You can always click the lookup action button to apply additional filters or retrieve more information to support your decision-making.

Implementing the behavior you're suggesting would require custom code changes, which are not part of the standard functionality—and it may not stop there. In your case, you want to exclude obsolete products, but other filters might also be relevant, such as inventory type or showing only available inventory (though backordering may still be desired). The key point is that no filtering is applied to the quick lookup, and different businesses may have varying requirements.

If I'm not mistaken, the code behind this is part of a general application layer, meaning the quick dropdown functionality is shared across multiple modules. While filtering out obsolete items might be useful in one module, another module may require access to those same items. Therefore, even with custom code, implementing such filters would require maintaining module-specific logic, which adds complexity and overhead.

 

4 replies

Reid Gilbert
Superhero (Employee)
Forum|alt.badge.img+15
  • Superhero (Employee)
  • September 16, 2025

Hi Philippe,
I tested in the latest standard V15.4 release and I didn’t see a way to eliminate those from the lookup, you may be able to add the is_obsolete field via the Alliance customizer to the QBE screen in order to get those to not display (or you could do it as a small customization).
Thanks,
Reid


Forum|alt.badge.img+7
  • Author
  • Sidekick (Partner)
  • September 17, 2025

Hi Reid, 

thanks for your answer, I think It’s the same for the Drop-down list of the “Product Id” field in the demand Material, it’s not possible to eliminate obsolete products..

Thanks

Philippe


Phil Seifert
Ultimate Hero (Employee)
Forum|alt.badge.img+24
  • Ultimate Hero (Employee)
  • Answer
  • September 17, 2025

Hi Philippe,

This functionality is not supported as standard for the quick lookup dropdown list when inserting values used for lookup. While the lookup dialog screens offer more filtering options, the dropdown list is intended solely for quick value selection. You can always click the lookup action button to apply additional filters or retrieve more information to support your decision-making.

Implementing the behavior you're suggesting would require custom code changes, which are not part of the standard functionality—and it may not stop there. In your case, you want to exclude obsolete products, but other filters might also be relevant, such as inventory type or showing only available inventory (though backordering may still be desired). The key point is that no filtering is applied to the quick lookup, and different businesses may have varying requirements.

If I'm not mistaken, the code behind this is part of a general application layer, meaning the quick dropdown functionality is shared across multiple modules. While filtering out obsolete items might be useful in one module, another module may require access to those same items. Therefore, even with custom code, implementing such filters would require maintaining module-specific logic, which adds complexity and overhead.

 


Forum|alt.badge.img+7
  • Author
  • Sidekick (Partner)
  • September 17, 2025

Hi Phil, 

thanks for your answer, it was the requirement for one of our customers, they will see if they really need this behavior

Best regards

Philippe