Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
Given this setup, is there any way I can group this data by the co ID? I have other tables that I cannot merge or create relationships to because my main dataset can have a co ID more than once depending on other factors, but my aim isn't to get rid of the other fields because I still need them:
Hi @Anonymous
I'm not clear what you need. You can create calculated measures that can perform SUM, COUNT, AVERAGE type calculations over a group of rows that belong to a particluar co ID. Is that what you mean?
@Phil_Seamark When trying to create a relationship between these two tables, I'm stopped because my CService dataset will have ID's appear more than once. Both fields from both tables are the same data I'm attempting to link on:
@Anonymous,
Add a calculated table and then build relationships.
@v-chuncz-msft This is nice but all it does is return distinct values from my 'Cservice' dataset. I need my 'CService' dataset to link with my 'EMS Survey' dataset while still being able to use my start and end dates from 'CService'. The 'co' field from 'Cservice' is the same as the 'New ID' field in my 'EMS Survey' dataset. I can create a relationship between 'EMS Survey' and 'Table' of the distinct co values, but I still need access to other fields within 'CService':
User | Count |
---|---|
124 | |
108 | |
99 | |
62 | |
62 |
User | Count |
---|---|
137 | |
115 | |
102 | |
71 | |
61 |