Forum Discussion
Filters automatically applying depending on what is selected
Hi, I currently have a dashboard set up and need help with my filters. I have two sheets. Combined dispatches and standard cost. When a user selects what project definition (from the combined dispatches sheet) they would like to look at using the tile slicer, i want the engine spec (from the standard cost sheet) to automatically apply. the combined dispatches sheet has the project definition and engine spec whereas the standard cost sheet only has the engine spec. i have relationships for the engine spec set up using a DIM Engine Spec table as there was a many to many relationship without it.
Hi Anonymous,
Thank you for reaching out to the Microsoft Fabric Forum Community. and Thanks to burakkaragoz for prompt and helpful response.
To ensure that selecting a Project Definition from the Combined Dispatches sheet automatically filters the related Engine Spec in the Standard Cost sheet, you need to use a common Dim Engine Spec table to resolve the many-to-many relationship. Both Combined Dispatches and Standard Cost tables should have one-to-many relationships with this Dim Engine Spec table. Since there's no direct link from Project Definition to Standard Cost, you can use a DAX approach like TREATAS to pass the filtered Engine Spec values from Combined Dispatches to Standard Cost.
If you found this response helpful, please consider marking it as the accepted solution and giving it a thumbs-up so it can assist others in the community as well.
Best regards,
Prasanna Kumar
5 Replies
- burakkaragoz
Super User
Hi Anonymous ,
In addition to the great points already mentioned, one thing that often gets overlooked in CSV import scenarios — especially when dealing with schema mismatches or silent failures — is explicit schema binding during import.
Here’s what I’d suggest:
Use a staging table
Before importing directly into your target table, import the CSV into a staging table with all columns defined as VARCHAR(MAX). This helps isolate data issues without triggering type or constraint errors.Validate and transform
Once the data is in the staging table, use SQL to:- Check for nulls or unexpected formats
- Trim whitespace
- Convert data types explicitly
Use MERGE or UPSERT logic
When moving data from staging to the target table, use a MERGE statement to handle inserts and updates in one go. This gives you full control over how existing records are updated.Log errors
Wrap your import logic in a TRY-CATCH block and log any failed rows to a separate error table. This makes debugging much easier.
Also, if you're using a tool or script to automate this, make sure it’s not silently skipping rows due to encoding issues (e.g., UTF-8 BOM) or delimiter mismatches.
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
translation and formatting supported by AI Hi Anonymous,
Thank you for reaching out to the Microsoft Fabric Forum Community. and Thanks to burakkaragoz for prompt and helpful response.
To ensure that selecting a Project Definition from the Combined Dispatches sheet automatically filters the related Engine Spec in the Standard Cost sheet, you need to use a common Dim Engine Spec table to resolve the many-to-many relationship. Both Combined Dispatches and Standard Cost tables should have one-to-many relationships with this Dim Engine Spec table. Since there's no direct link from Project Definition to Standard Cost, you can use a DAX approach like TREATAS to pass the filtered Engine Spec values from Combined Dispatches to Standard Cost.
If you found this response helpful, please consider marking it as the accepted solution and giving it a thumbs-up so it can assist others in the community as well.
Best regards,
Prasanna Kumar
Hi Anonymous,
Just a gentle reminder has your issue been resolved? If so, we’d be grateful if you could mark the solution that worked as Accepted Solution, or feel free to share your own if you found a different fix.
This not only closes the loop on your query but also helps others in the community solve similar issues faster.
Thank you for your time and feedback!
Best,
Prasanna Kumar
Hi Anonymous,
Just a gentle reminder has your issue been resolved? If so, feel free to share the solution that worked for you, or let us know if you found a different fix.This helps close the loop on your query and supports others in the community who might face similar challenges.
Thank you for your time and feedback!
Best regards,
Prasanna Kumar
