How can I avoid "duplicate value found" errors when build / deploy cube in ssas 2012

How can I avoid "duplicate value found" errors when build / deploy cube in ssas 2012.  I've created views based on tables, created datasources, datasource view, dimension and cube.  But when I deploy cube I get error that duplicate value found for "status dimension"  I linked the status dimension to calls fact table based on concatenated key of call#/status  (i.e. #0123/Closed)
conardbAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rainer JeschorCommented:
Hi,
could you please post the exact error message?
As well as some Information about the dimension Attribute properties, data types etc.

Thanks
Rainer
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
conardbAuthor Commented:
Thanks, I haven't abandoned this... I didn't get an email to my second (work account)  The message was that there was a duplicate CallID field which is one of the key fields from the fact to a dim.... I ended up limiting the view to exclude any non-related values in either the fact or dim and I was able to create a cube with only 2 dimensions (date, call status).  I started to look at using rollup aggregaate for the fact view and started experimenting with using the cube aggregate in a view.  I'd be thankful for any suggestions or best practice advice on creating a cube for a help desk system.  Calls are recorded in a call_log table and there are related lookup tables for status, category etc but the foreign key would be the actual value (ie statusdim pk = closed, fk in fact)  and there are some values in fact that are null
0
conardbAuthor Commented:
Thanks, I haven't abandoned this... I didn't get an email to my second (work account)  The message was that there was a duplicate CallID field which is one of the key fields from the fact to a dim.... I ended up limiting the view to exclude any non-related values in either the fact or dim and I was able to create a cube with only 2 dimensions (date, call status).  I started to look at using rollup aggregaate for the fact view and started experimenting with using the cube aggregate in a view.  I'd be thankful for any suggestions or best practice advice on creating a cube for a help desk system.  Calls are recorded in a call_log table and there are related lookup tables for status, category etc but the foreign key would be the actual value (ie statusdim pk = closed, fk in fact)  and there are some values in fact that are null
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.