Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredGet Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
Refresh crashes because of a duplicate in a 1:1 relationship, even though this doesn't cause an error in the data model. The user CAN delete the conection, refresh, and then re-add the connection with no probelm. The reason that this connection is ok is because one table contains unique values, even thought filtering is allowed in both directions. However because the filter direction is set to "both" the system thinks that both tables much have unique values, which is unnecessary. This means that automatic refresh is not possible and the the user must delete the connection in the data model, refresh, and then re-add the connection each time that the dashboard is refresh. This is a bug.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.