none
wildcard char is again deprecated on set/group filters in R2 RTM? RRS feed

  • Question

  • Hi, Looks like the wildcard char (*) is again deprecated in R2 RTM?. It was available in Update 2...does anyone know R2 RTM will have the replacement functionality like isPresent?

    Release Notes: http://technet.microsoft.com/en-us/library/hh322889#pre_install 

    I'm sure many FIM deployments are still using wildcard chars for critical sets and criteria based groups, and fixing these will be  a real challenge and time consuming. 

    Release Notes also says the below, does it mean we can use still use % wildcard char for checking IsPresent? i'm confused, pls help.

    FIM Service: Contains, Starts-With, and Ends-With searches on String and Text attributes are implemented using the TSQL LIKE operator with standard SQL wildcard behaviors
    This means that the following characters %, _, [, ^ are treated as wildcards http://msdn.microsoft.com/en-us/library/ms179859.aspx. If your use cases require these characters to be treated as literals, then you must escape them per the TSQL LIKE documentation by enclosing the wildcard character in brackets.


    • Edited by Prakaaz Tuesday, June 5, 2012 2:36 PM additional info
    Tuesday, June 5, 2012 2:20 PM

Answers

  • Prakaaz,

    The wildcard characters were deprecated (automatically escaped) in Update 2. But, due to customer feedback, the wildcards were reintroduced in R2 RTM. If you have sets that rely on the wildcard characters to be treated as wildcards, then you do not need to update any of those sets. If, however, the sets rely on the wildcard characters to be treated as literals, then you will need to update those sets.

    Note: only the starts-with and ends-with predicates support wildcard characters.


    • Edited by BinomialShelf Tuesday, June 5, 2012 8:51 PM Clarifying the last statement.
    • Marked as answer by Prakaaz Wednesday, June 6, 2012 12:28 AM
    Tuesday, June 5, 2012 8:48 PM

All replies

  • Prakaaz,

    The wildcard characters were deprecated (automatically escaped) in Update 2. But, due to customer feedback, the wildcards were reintroduced in R2 RTM. If you have sets that rely on the wildcard characters to be treated as wildcards, then you do not need to update any of those sets. If, however, the sets rely on the wildcard characters to be treated as literals, then you will need to update those sets.

    Note: only the starts-with and ends-with predicates support wildcard characters.


    • Edited by BinomialShelf Tuesday, June 5, 2012 8:51 PM Clarifying the last statement.
    • Marked as answer by Prakaaz Wednesday, June 6, 2012 12:28 AM
    Tuesday, June 5, 2012 8:48 PM
  • Thanks. This helps. in my case, i'm using wildcard char % on the sets and groups along with Starts-with. so R2 won't break anything for me..

    thanks again.

    Wednesday, June 6, 2012 12:27 AM
  • we will be fixing the relnote.

    thanks for pointing that out


    The FIM Password Reset Blog http://blogs.technet.com/aho/

    Wednesday, June 6, 2012 3:07 AM
  • "due to customer feedback"....what customer feedback?  Provide specific examples.  Names and Numbers please!  The only gripes or complaints I've ever seen, and I'm all over this forum, are from users that want to treat those characters as wildcards....NOT LITERALS....why is it that Microsoft seems to be listening to some small group and ignoring the giant field of users/engineers that actually want to use these characters the way SQL intended?  AS WILDCARDS
    Wednesday, June 6, 2012 1:34 PM
  • customer == you guys...

    i was the one that forward som of the posts from this forum back to the feature team, and we reverted some of the changes

    >_<"


    The FIM Password Reset Blog http://blogs.technet.com/aho/

    Wednesday, June 6, 2012 5:18 PM
  • This whole post is now officialy confusing :)
    Wednesday, June 6, 2012 5:26 PM
  • we are fixing the online relnote and should be updated soon

    The FIM Password Reset Blog http://blogs.technet.com/aho/

    Wednesday, June 6, 2012 5:30 PM
  • RelNote is updated

    FIM Service: Starts-With, and Ends-With searches on String and Text attributes are implemented using the TSQL LIKE operator with standard SQL wildcard behaviors
    This means that the following characters %, _, [, ^ are treated as wildcards (http://msdn.microsoft.com/en-us/library/ms179859.aspx). If your use cases require these characters to be treated as literals, then you must escape them per the TSQL LIKE documentation by enclosing the wildcard character in brackets.


    The FIM Password Reset Blog http://blogs.technet.com/aho/

    Thursday, June 7, 2012 9:49 AM