Change of Attribute length is not consistent - by Doktor_kermit

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 2108307 Comments
Status Resolved Workarounds
Type Bug Repros 0
Opened 12/9/2015 1:20:07 AM
Access Restriction Public

Description

The ability to change the length of an attribute in MDS, is not consistent.
In web interface, we can change it from 1 char to 4000 char if it's a text field.
In excel add-in we can change it from 1 to 1000, and not at all see properties of the attributes if the length exceeds 1000 char.

This have been a problem from the first version of MDS.

Please look at http://funkylab.com/found-a-possible-bug-in-mds/ for a full walk-through

Conclusion:
Something is not right here, there are some inconsistency in the way MDS behaves in regard to attribute management.

Changes to an attributes length is not supported in web interface
Changes to an attributes length is supported in Excel Add-In
Changes to an attributes length is limited to max 1000 in Excel Add-in
New attributes support a length of max 4000 in web interface
New attributes support a length of max 1000 in Excel Add-in
It is not at all possible to change an attributes length once it is set to 4000
I have not yet tried this scenario on SQL Server 2016 MDS, but I hope that it has changed.

Tested on SQL 2016 CTP3.1
The issue is the same on SQL server 2016 CTP3.1, well almost!

Changes to an attributes length is supported in Excel Add-In
Changes to an attributes length is limited to max 1000 in Excel Add-in
New attributes support a length of max 4000 in web interface
New attributes support a length of max 1000 in Excel Add-in
It is not at all possible to change an attributes length once it is set to 4000 in Excel Add-In
Sign in to post a comment.
Posted by Microsoft on 12/22/2015 at 4:59 PM
The resolution for this issue will be provided in upcoming monthly release of SQL Server 2016 - CTP3.3