Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreWe've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
Hi,
I am trying to find a correct and efficient way to copy the Field Parameters from an existing PIBX (in Desktop 2.145 64-bit, July 2025) to a new empty PBIX file (in Onpremises-Remote Server). In the Onpremises-Remote Server version, one cannot use the Tabular Editor tool.
Also, I am unable to see the Field Parameters in Transform Data, of the already-completed Desktop version (from where I could copy them over to the new PBIX of Onpremises (Remote Server) version). It is only showing the Tables themselves:
Kindly advise how I can copy over the Field Parameters.
Regards
Solved! Go to Solution.
Thankyou, @lbendlin for your response.
Hi @F_Reh,
We appreciate your inquiry through the Microsoft Fabric Community Forum.
Based on our understanding, Field Parameters in Power BI are not limited to DAX tables. They also include additional semantic model metadata such as ParameterMetadata, grouping, and hidden columns. Therefore, when you copy only the DAX into a New Table, it becomes a regular calculated table. As a result, it appears as a composition instead of behaving as a single slicer ready field.
In on-premises or remote server environments where Tabular Editor is not available, one possible approach is to recreate the Field Parameter using Modeling. Then, select New Parameter and choose Fields. After that, replace the auto-generated DAX with your original parameter DAX. This method preserves the required metadata and restores the correct slicer behavior.
Please find the screenshots and the PBIX files attached below:
Additionally, please refer to the link below:
Use report readers to change visuals - Power BI | Microsoft Learn
We hope the information provided helps resolve the issue. Should you have any further queries, please feel free to contact the Microsoft Fabric community.
Thank you.
Thankyou, @lbendlin for your response.
Hi @F_Reh,
We appreciate your inquiry through the Microsoft Fabric Community Forum.
Based on our understanding, Field Parameters in Power BI are not limited to DAX tables. They also include additional semantic model metadata such as ParameterMetadata, grouping, and hidden columns. Therefore, when you copy only the DAX into a New Table, it becomes a regular calculated table. As a result, it appears as a composition instead of behaving as a single slicer ready field.
In on-premises or remote server environments where Tabular Editor is not available, one possible approach is to recreate the Field Parameter using Modeling. Then, select New Parameter and choose Fields. After that, replace the auto-generated DAX with your original parameter DAX. This method preserves the required metadata and restores the correct slicer behavior.
Please find the screenshots and the PBIX files attached below:
Additionally, please refer to the link below:
Use report readers to change visuals - Power BI | Microsoft Learn
We hope the information provided helps resolve the issue. Should you have any further queries, please feel free to contact the Microsoft Fabric community.
Thank you.
That's what I thought...I tried copying the Field parameter's DAX and using that to create New Table, but the Data Pane is showing like this "composition" :
It should appear like below - a single Field - which I simply copy in to the "Well" of the Slicer
Can you use TMDL view? Parameters are not really different from regular table definitions.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 1 |