Can someone explain how the UD Member property "Is attribute member" works?
I would like to assign to my UD5 members some attributes and be able to create CubeView base on the attributes.
As an example, my UD5 could be Customers and the attribute I would like to assign to each Customer is the type of Customer (Retail, non-retail etc).
I thought I would use the "Text 1" property of my Customer members to input the type of costumers. I would then create a separate UD5 dimension "CustomerAttributes" and list all the attributes. Finally, enable the "Is attribute memeber" property of my "CustomerAttributes" dimension members and do a comparison between the value in the Text 1 of my Customer members and the value in the "Comparison Text 1" of my attribute members.
Solved! Go to Solution.
From a performance perspective, we've been building some benchmarks on the impact of using Attribute members. As a precaution of turning on Attributes on members, there is some considerations. Below is a chart representing a 12 month consolidation when turning on X amount of Attribute members for a data volume of ~ 392,000 data records. In the testing, ~ 25 Attribute members will start impacting consolidation times. So if you plan on using more than 25 Attribute members, I would suggest doing performance testing in an environment that has equivalent resources to Production. Make sure that deciding to use this feature doesn't adversely effect other processes already in place without testing.