UDT Handler Filters

Respondida

Comentarios

6 comentarios

  • Avatar
    SSP Automation
    Thank you for your request. It has been scheduled for review by the development team that will get back to you should there be questions.
    (Please note that as we are user-driven we can't guarantee that your request will be met unless it gets many votes and/or fit the product vision)
    Read more about the Feature Request process here
    [Internal Id: 16432]
    Acciones de comentarios Permalink
  • Avatar
    Ronni Gaba

    Hi Matthew,

     

    Currently there are no plans to expand the filtering options, as the WHERE condition is the most flexible way of allowing people to do custom filtering.

    Are we perhaps misunderstanding your request? What is the business case you wish to use this functionality in?

    Acciones de comentarios Permalink
  • Avatar
    Matthew Brown

    The business case is that we will have millions of records in a udt where the main key is the itemcode. The UDT handler can be launched from the item master and filtered on ItemCode, we know this. However this will still bring back 100,000's of rows. So to further filter we are looking at additional filters based on where clauses other than "equals", or even the need to use a sub-select to aid with filtering.

    We have had some success with adding to the where clause under the "Advanced" button, my question is, is this the best method to achieve this. We want to filter the results shown by the UDT handler rather than using the "Foreign Key" functionality. 

    What options do we have?

    Acciones de comentarios Permalink
  • Avatar
    Rasmus Jensen

    There is nothing wrong with using the Where condition in the Advanced button... It will never go away or anything, even if we someday would add other filters.

    That being said, based on your description with 100.000+ records this (UDT Handler) might not be the right tool for the job... If a user needs to get an overview of 100.000 records (if that is even humanly possible) then IMHO you need a custom tool to achieve this.

    Could UDT Handler show 100.000 rows... Yes; but the more important question is: Should it/Does it give the user a good solution?... We have always seen it as a tool to take care of the small data-set, but despite me de-selling my own product here I'm a firm believer of "The right tool for the job" and UDT handler is IMHO not the right tool for the amount of data you mention here.

    Acciones de comentarios Permalink
  • Avatar
    Matthew Brown

    I agree.

    With the additional filtering against the "advanced" button we would expect approx 70 or less records being retrieved. Which makes the UDT Handler quite effective. Also the user would only be updating not adding or deleting rows. 

     

    Thanks.

    Acciones de comentarios Permalink
  • Avatar
    Rasmus Jensen

    OK... 70 rows seem more manageable so sounds like your solution is the Advanced button IMHO

    Acciones de comentarios Permalink

Iniciar sesión para dejar un comentario.