Forum Discussion
Resolver IFilters/Slicers/Relationships
I appreciate your input. I have solved my issues. I had made a bunch of SQL views in order to extract the info I wanted since I am not that great at Power Bi. This was creating issues since there were so many relationships and I could not figure out how to connect them. To fix this error, I decided it might be easier use formulas. I ended up creating a column that lists data as having issues or no issues, which is in the same table as the Thickness Issues and most of my other data. This eliminated my need to create all of these relationships and instead I am able to allow the user to choose whether to include or exclude data issues, and then filter in which data issues they want to see and this is all coming from the same table. I will say that part of the problem was that I had to create my own PK and FK to connect two of my tables. I did this by combining the "SampleNumber" and "ShiftDate" in SQL in order to create a view that contains unique values and connected them on that.
Super UserPlease provide sanitized sample data that fully covers your issue. If you paste the data into a table in your post or use one of the file services it will be easier to assist you. I cannot use screenshots of your source data.
Please show the expected outcome based on the sample data you provided. Screenshots of the expected outcome are ok.
https://community.powerbi.com/t5/Desktop/How-to-Get-Your-Question-Answered-Quickly/m-p/1447523
Resolver II appreciate your input. I have solved my issues. I had made a bunch of SQL views in order to extract the info I wanted since I am not that great at Power Bi. This was creating issues since there were so many relationships and I could not figure out how to connect them. To fix this error, I decided it might be easier use formulas. I ended up creating a column that lists data as having issues or no issues, which is in the same table as the Thickness Issues and most of my other data. This eliminated my need to create all of these relationships and instead I am able to allow the user to choose whether to include or exclude data issues, and then filter in which data issues they want to see and this is all coming from the same table. I will say that part of the problem was that I had to create my own PK and FK to connect two of my tables. I did this by combining the "SampleNumber" and "ShiftDate" in SQL in order to create a view that contains unique values and connected them on that.