Forum Discussion
Unexpected Error - A Tasks exceptions were not observed
Hi Guys, sorry I'm pretty new at this, but I've come across this error when trying to create a relationship between 2 tables... I've tried restarting and tried creating a new pbix, neither changed the outcome... does anyone have any advice they could offer please and thank you?
9 Replies
- Greg_Deckler
Community Champion
Wow, that's a unique error. I'd send a frown. Do you have unique values in one of those tables? Are the columns the same data types? How many rows are we talking?
- twittrerNew Member
doubtful on the unique values
added a table to match up transaction dates to the week number that it falls in, linking the data table to the "week number" table causes the error... date-types match in each table, range of dates in the created table goes both before and past the transaction dates in the other table...
all good, have sent a "frown", cheers ;)- v-huizhn-msft
Microsoft Employee
Hi twittrer,
If you want to create a relationship between 2 tables, at least one column in one of the tables must contain unique values. There are only many-one and one-one relationship in Power BI. More details, please review this article: https://docs.microsoft.com/en-us/power-bi/desktop-create-and-manage-relationships.
Best Regards,
Angelia
- bathnesresearchRegular Visitor
Yup, getting this one too. This was for a 1:many relationship from a summarised table.
Copied to csv and there were some very odd behavours, including some characters which absolutely weren't in the raw data - bodged a text file together for this purpose and added it as a completely new table and it's behaving normally.
This was fine as we're just prototyping, but this will be a real pain if it is persistent
- AnonymousNot applicable
I'm getting the same error, version December 2018. Anybody have an answer yet?
- AnonymousNot applicable
I am getting the same error. The 2 tables are on the Azure SQL cloud.
One of the tables has the PK unique values for the 1:m relationship. - AnonymousNot applicable
I am getting the same error. The 2 tables are on the Azure SQL cloud.
One of the tables has the PK unique values for the 1:m relationship. - AnonymousNot applicable
I was facing a similar issue. I was working on Virtual Machine - after restarting/rebooting the machine and upgrading to the newest version solved the problem for me. Hope this helps!