Fabric is Generally Available. Browse Fabric Presentations. Work towards your Fabric certification with the Cloud Skills Challenge.
hi guys ,
I have a data like below
Project | Proj Code | Creation Date | Won Date | Lost Date | Creation FY | Creation FY Month No. | Creation Month | Won Fy | Won Month | Won FY Month No. | Status |
Proj1 | 0001 | 26 March 2019 | 18 April 2019 | 2018-2019 | 12 | March | 2019-2020 | April | 1 | Won | |
Proj2 | 0002 | 24 September 2019 | 1 october 2019 | 2019-2020 | 6 | September | 2019-2020 | October | 7 | Won |
Now to i have to show total projects in different statuses over current fiscal year's months.So below are the measures i have used
This year won projects=
Solved! Go to Solution.
From the data you've provided, it seems like you're trying to count the number of projects that have been won in the current fiscal year. The DAX measure you've written is designed to do just that.
However, the issue you're facing is that when you combine this measure with the "Won Month" column in a chart, it's showing "March" even though it's not present in the data.
The first thing that comes to mind is that there might be an issue with the way the data is being filtered or visualized. Here are a few things to consider:
- The data you've provided does have a "March" in the "Creation Month" column for Proj1. Even though this isn't the "Won Month", it's possible that there's some overlap or confusion in the way the data is being visualized. Ensure that the chart is strictly using the "Won Month" column and not any other month column.
- The FILTER function in your measure is filtering the data based on the fiscal year and the status. It's possible that there's other data in your 'Pipeline Master' table that has a "Won Month" of March but isn't shown in the sample you've provided. You might want to check the entire dataset to ensure there's no such entry.
- Another thing to consider is the way the months are sorted or visualized in the chart. Sometimes, visuals might have default sorting or grouping that can cause unexpected results. Ensure that the chart is sorted by the "Won FY Month No." column to get the months in the correct order.
- Lastly, it's always a good idea to check for any relationships or interactions with other tables or visuals in your Power BI report. Sometimes, slicers or other filters can cause unexpected behavior in visuals.
In summary, while your DAX measure seems correct for the task at hand, the issue might be with the way the data is visualized or with some unseen data in your table. Double-check the entire dataset, ensure the chart is using the right columns, and check for any other interactions in your report. Hope this helps!
From the data you've provided, it seems like you're trying to count the number of projects that have been won in the current fiscal year. The DAX measure you've written is designed to do just that.
However, the issue you're facing is that when you combine this measure with the "Won Month" column in a chart, it's showing "March" even though it's not present in the data.
The first thing that comes to mind is that there might be an issue with the way the data is being filtered or visualized. Here are a few things to consider:
- The data you've provided does have a "March" in the "Creation Month" column for Proj1. Even though this isn't the "Won Month", it's possible that there's some overlap or confusion in the way the data is being visualized. Ensure that the chart is strictly using the "Won Month" column and not any other month column.
- The FILTER function in your measure is filtering the data based on the fiscal year and the status. It's possible that there's other data in your 'Pipeline Master' table that has a "Won Month" of March but isn't shown in the sample you've provided. You might want to check the entire dataset to ensure there's no such entry.
- Another thing to consider is the way the months are sorted or visualized in the chart. Sometimes, visuals might have default sorting or grouping that can cause unexpected results. Ensure that the chart is sorted by the "Won FY Month No." column to get the months in the correct order.
- Lastly, it's always a good idea to check for any relationships or interactions with other tables or visuals in your Power BI report. Sometimes, slicers or other filters can cause unexpected behavior in visuals.
In summary, while your DAX measure seems correct for the task at hand, the issue might be with the way the data is visualized or with some unseen data in your table. Double-check the entire dataset, ensure the chart is using the right columns, and check for any other interactions in your report. Hope this helps!
Check out the November 2023 Power BI update to learn about new features.
Read the latest Fabric Community announcements, including updates on Power BI, Synapse, Data Factory and Data Activator.