1. listopadu 2011 1:24
Has anyone come across the error "ERR210003 Error - The AttributeValue references a member that does not exist or is inactive." where the AttributeValue is populated with the namespace of the MemberIdentifier?
The AttributeValue is a reference to a Domain-based attribute, that if it doesn't exist we handle by creating an Orphan member in the reference entity that will later be updated when the actual data flows in to MDS.
2. listopadu 2011 12:43Moderátor
here are some populating examples:
Updating attribute values
You can use the Attributes staging table (tblStgMemberAttribute) to update attribute values. For more information about the fields in this table, see Attributes Staging Table.
The following example shows how you could update an attribute for a leaf member, a consolidated member, and a collection.
INSERT INTO mdm.tblStgMemberAttribute (ModelName, EntityName, MemberType_ID, MemberCode, AttributeName, AttributeValue) VALUES
(N'Product', N'Product', 1, N'BK-M101', N'DaysToManufacture',N'4'),
(N'Product', N'Product', 2, N'MW', N'Owner', N'Gisli Olafsson'),
(N'Product', N'Product', 3, N'JR', N'Description', N'John Yokim''s Products')
but this example doesn't show for a domain based attribute update,so :
when you update a domain based attribute entityname should be the name of the child entity
membertype_id, by default is "leaf".
membercode will be the code of your domain based (parent) attribute member.
attributename will be the name of the domain based attribute field that you want to update.
attribute value will be the domain based attribute field value that you want to update.
Microsoft Community Contributor
Avanade , FRANCE
If a post answers your question, please click "Mark As Answer" on that post and "Vote as Helpful".
- Označen jako odpověď Challen FuModerator 7. listopadu 2011 10:37
7. března 2012 8:04