none
Business rules - "if is not equal to blank" condition incorrectly identifies blank values as not blank RRS feed

  • Question

  • Using SQL 2012 MDS

    For some reason, when I create business rules that are dependent on a value not being blank they incorrectly find legitimately blank values as not blank.

    Is this a bug or am I missing something?


    Tuesday, July 8, 2014 3:53 PM

Answers

All replies

  • Could you give an example or elaborate some more on what you are trying to build.
    Wednesday, September 3, 2014 10:19 AM
  • Hi Fredrik

    The rule I've created goes "If field A is not equal to blank AND (field A = field B), then field A is not valid".

    The problem is when both fields A and B are blank, validation fails.

    Wednesday, September 3, 2014 11:35 AM
  • Matt, is this still an issue?

    Thanks!


    Ed Price, Azure & Power BI Customer Program Manager (Blog, Small Basic, Wiki Ninjas, Wiki)

    Answer an interesting question? Create a wiki article about it!

    Monday, January 26, 2015 9:30 PM
    Owner
  • Hi, this issue should be fixed in the latest CU release for SQL2012 and SQL2014. If haven't, please install the latest CU update.

    Thanks,

    Sherry

    Tuesday, January 27, 2015 11:30 PM
    Moderator
  • As of SQL Server 2012 SP2 CU 4 which I believe is the latest the "is Blank" condition will fail to equate to empty strings.  It does correctly catch NULL values.  Right now I don't have a work around for this issue.

    "Attribute is equal to Blank" will catch NULL values.

    "Attribute is equal to Blank" will not catch empty string values.

    Right now I don't know of a way to get this working.  You could set all empty strings to ~NULL~ in the staging process and your comparison should work.



    Thursday, January 29, 2015 6:52 PM
  • Hi, the current MDS behavior that "is equal to Blank" will match to NULL but will not match to empty string. We will consider to support this in the next version of release.  If you think this is an important case that blocks you now, please file the bug through Connect and we will triage accordingly.

    Friday, January 30, 2015 12:07 AM
    Moderator
  • Had a related issue with a business rule controlling the maximal length of an attribute. It messed up when the field was blank. My solution was to add a "stupid" business rule executed before my control:

    "IF field A is equal to blank THEN field A is equal to blank"

    silly when you read it, but it worked for me...

    Wednesday, February 4, 2015 12:06 PM
  • Sherry,

    Thanks for you feedback.  I tried to add this to Microsoft Connect but I don't see any "left pane" in my search results when the directions on that page say..

    1. If your issue is not listed, click "Submit Feedback" on the left pane of the search results page.

    In any case it would great to have more transparent control over NULL and empty string matching in the Master Data Services web interface as its very easy to create empty string values and right now I don't have a way to check for them.  I can only test NON-empty string values and that's using contain's pattern with a regex.


    Friday, February 6, 2015 6:50 PM
  • Hi, please don't worry about Left pane. There is a "Submit Feedback" button under the search field. You can click on that to submit your feedback. In parallel, we are looking into the possible solutions on this as well.

    Thanks,

    Sherry

    Sunday, February 8, 2015 7:14 AM
    Moderator
  • IsBlank is only equal to NULL.

    To match the empty string or string only contains whitespace, you can try to use "contains the subset".

    For example, "\s*" should match all empty or whitespace string.

    https://msdn.microsoft.com/en-us/library/ee633870.aspx

    Wednesday, February 25, 2015 3:10 AM
    Moderator