I believe the recommendations made at your other thread are correct. Try to trim/clean the data and set to all upper or lower case (if applicable) before doing a remove duplicates step. You may also be able to improve the uniqueness of your key if you add an index and merge before removing dups, but again, this will depend on your exact scenario and data.
Well in fact I have over 11 "Imports" i need to figure out the relationships on.. and right now I am just trying with the two.. I have managed to create a relationship between these 2, but whenever I drag a column in from both of em
Really prefer not to share it with the entire world and the DB I look up against is just a backup on my own machine, so you wont be able to use the SQL database either so unsure how much the pbix file will help you if you cant boot it up against any database?
Anyways really willing to pay 50-100$ to get these relationships fixed, depending on how long time it take over skype.
So if you are using Import mode (vs. Direct Query) which you said you were, then the imported data is stored in the data model that comes with the PBIX. However, I understand that you don't want to share the data. Is it possible to create some obfuscated or dummy data that at least matches the structure and syntax?
Nah, it's to hard obfuscating all the data, even if I use a tool like SQL Data Generator it wont create the same issue as the same values / duplicates might not show up.. just tried=/ really think a skype session with payment will be the best