Forum Discussion

mattcarter865's avatar
mattcarter865
Helper I
4 years ago
Solved

Field Parameters - Error when converting from live connection to directquery

I know it's preview feature so there are bound to be bugs; That's why I'm bringing it up here.   I set up a Field Parameter list of measures in a shared published dataset. Then I create a thin repo...
Tips and Tricks
  • Anonymous's avatar
    Anonymous
    4 years ago

    Hi mattcarter865 ,

     

    Thanks for sharing.

     

    Best Regards,

    Jay

bhalicki's avatar
bhalicki
Helper V
1 year ago

Hi all,

Seems this is still an issue with PowerBi June 2025.  I no longer have access to Tabular Editor.  Hoping someone might be aware of a workaround that doesn't involve Tabular Editor?  I have raised a support incident to Microsoft either way.

Kind regards,

 

Ben.

agusmba's avatar
agusmba
Advocate III
1 year ago

First of all, thanks for replying to this thread. I had completely forgotten about this and today I needed to fix a composite model with this workaround. Serendipity.

 

As for your question, have you tried saving your report in project mode (with TMDL enabled)? I usually do that (in order to version it with git), and I see the extendedProperty ParameterMetadata in normal models. Maybe you can add it to your composite model that way (work on a copy of the report first).

 

This is how it looks like on the one I fixed today. I did it with TE, but I see the changes in the tmdl file after saving as project:

 

Note that external changes to the tmdl code are not reflected on an open report, you need to reopen it in order to see the changes. You could also try the new TDML view for live editing within PBIDesktop, but I haven't tried it.

  • bhalicki's avatar
    bhalicki
    Helper V
    1 year ago

     

     

    Hi agusmba ,

    Absolute legend!  I tried using the new TDML editor and this worked.

    The only requirement was to add the 'extendedProperty' option to the parameter field.
    Before:column Value
    dataType: string
    isHidden
    lineageTag: 39c0ff18-d51e-4b7d-aacd-742881dfae3f
    sourceLineageTag: 7a80ce5f-661c-4b34-a956-2a22137b3d6b
    dataCategory: Uncategorized
    summarizeBy: none
    sourceColumn: Value
    sortByColumn: SortOrder

    annotation SummarizationSetBy = User

    After:

    column Value
    dataType: string
    isHidden
    lineageTag: 39c0ff18-d51e-4b7d-aacd-742881dfae3f
    sourceLineageTag: 7a80ce5f-661c-4b34-a956-2a22137b3d6b
    dataCategory: Uncategorized
    summarizeBy: none
    sourceColumn: Value
    sortByColumn: SortOrder

    extendedProperty ParameterMetadata = {"version":3,"kind":2}

    annotation SummarizationSetBy = User


    After applying the changes, the parameter was recognised correctly.

    I ended up raising this to Microsoft support.  This was the response:

    We have checked with our team and found that this error occurs when a report with field parameters is renamed or changed, and the live connection is switched to direct query.

     

    This is expected behavior as the field parameters do not work in Direct Query mode.

    Users can re-create the field parameters locally on the model as a workaround.

    Please check the document below:

    Use report readers to change visuals (preview) - Power BI | Microsoft Learn

     

    As it is a limitation, it would not be possible to check this issue with our product team.

    So, we request you to please post your idea in the idea forum.

     

    To post an idea for future development

    https://community.fabric.microsoft.com/t5/Fabric-Ideas/idb-p/fbc_ideas


    For anyone who comes across this issue, just add the extendedProperty option.

    Kind regards,

    Ben.

    agusmba