Business rule bug for attribute with NVARCHAR(5) could not set to Blank - by MSIT Justin Li

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 775855 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 1/5/2013 12:04:02 AM
Access Restriction Public


When I create a business rule to set an attribute (Say it's 'CFlag') to Blank, if the attribute 'CFlag' type is NVARCHAR(5), it will give error message '245: Conversion failed when converting the nvarchar value '~NULL' to data type int.' while Apply Rules.
While check the background code in the system generated Stored Procedure [mdm].[udp_SYSTEM_5_153_CHILDATTRIBUTES_ProcessRules], it will set the 'CFlag' = '~NULL~', but attribute 'CFlag' only has 5 chars, so it will cut the string to '~NULL'.
Sign in to post a comment.
Posted by Microsoft on 1/10/2013 at 9:11 AM
No, this is really just an unintended consequence of a design choice. The same issue may be encountered when using staging to set values to null when the attribute width is less than 6. I submitted a Community Comment to this doc page:
Posted by MSIT Justin Li on 1/10/2013 at 12:13 AM
Hello, Lynn:
Just want to confirm, is there any online document or product document mentioned the minimum width should be 6 for MDS attribute?
Thanks a lot.
Posted by Microsoft on 1/9/2013 at 4:33 PM
Hi Justin,
Thank you for reporting this issue. It's always great to hear from customers, even if it's about a problem they are having. In this case, as you observe, your attribute is not wide enough to hold the intermediate value. The minimum width is 6. We are closing this issue but marking it for consideration in a future release.