Model - Field properties not showing when added a Direct Query Table and saving the file/reopening

[steverely]

Action:

- A have a model with imported tables

- I added a direct query Table

- I still could change the field properties in the model for all tables

- I saved the file and closed it

- I reopened the file

Issue: 

- I can't see the properties anymore for the fields except only for tables, hierarchies and the fields within a hierarchie

Example below: I click on Medewerker Email and the properties stayed on the table Medewerker properties

[steverely]

When afterwords adding a new table the Field Properties become available again but after saving & closing the initial issue remains

[v-cazheng-msft]

Hi @steverely,

May I know whether you still have this issue? Are you using the latest version of Power BI Desktop(2.105.1143.0 64-bit, May 2022, Download Microsoft Power BI Desktop from Official Microsoft Download Center)? If you try later or try with an older version, will you see the same issue(Download Microsoft Power BI Desktop from Official Microsoft Download Center)?

Best Regards,

Community Support Team _ Caiyun

[steverely]

Hi,

My current version :  2.105.1143.0 64-bit (mei 2022)

Greetings

Steve

[pk_Ross]

I have this issue as well, originally in the May 2022 version and now I'm on the June 2022 version. - 2.106.582.0 64 bit. It's particularly frustrating, as I'm prototyping binding parameters for dynamic M queries, and these are only accessible through the properties panel. It's not quite clear to me what triggers the situation where the properties panel goes off the rails, but there's definitely an issue.

[RenatoD]

I have exactly the same problem as pk_Ross... and I have tried the same things. I am on the June 2022 version, but it was doing it on the May 2022 version as well.  Have not figured out a workaround yet. 

[redwoods]

I have the same problems as pd_Ross and RenatoD.  I'm running 64 bit June 2022 version.  I was building up about 10 direct query data tables over a course of a week.  Each day I would save and close the file.  Each day I opened it, the field properties would show up as usual.  But today, I opened the same file and the field properties do not show up.  The dynamic parameter binding still works.  I change a parameter selection and the direct query fetches the new data as expected.  However, I can not edit the data model now.  

I was able to create a direct query with dynamic parameter binding in a new file, replicating the first set of data model in the original.  Field properties were available as usual.  So it seems there is something going on with the save and open of the file over time that seems break the field property display.  

Very interested in seeing a fix soon or some workaround.  

[redwoods]

After I deleted parameters and lists that were not used as dynamic parameter in direct queries, I now see the field properties again.  

[pk_Ross]

Yes, I think Redwoods pinpointed the issue and the temporary workaround. It seems the issue is caused by having a combination of parameters in the model where some are used in dynamic parameters and others are not used in dynamic parameters (and by the way, it's still occurring in the July 2022 version).

In my models I use standard parameters for the server and database name to allow for easy repointing from development to production. These are not used in the dynamic M queries. When I removed these parameters, hard coding the references into the queries - leaving only parameters that are used in dynamic M queries - the field properties are once again displaying. 

@v-cazheng-msft - it should be pretty straightforward to replicate these conditions to confirm the problem. Although it's a relief to know there's a workaround, it's clearly not great to be forced to not use 'non-dynamic' parameters when making use of this feature.

[RenatoD]

Thanks @pk_Ross I can confirm it is still happening in the July 2022 version as well. I did exactly what you did to have parameters for Server / Database. Some of the pbix's have 15-20 different queries... so I don't want to change that. One workaround that does work sometimes is adding a new query to another table. I am not convinced that your workaround will work 100% of the time based on what I have seen. I thought my workaround was working fine, up until it stopped working... Then the only workaround that worked was open an new empty report, then copy / paste from one report into the other.  This is a horrible/nasty bug, and really needs to be fixed. Based on other comments I found on the forum this has been around a while... it isn't new. 

[nixonba2]

The bug still exists in version 2.120.963.0 64-bit (August, 2023). I was not getting results with the above mentioned workarounds so I was trying various things, and I'm not 100% sure what did it, but refreshing all the stale previews ("Preview was last refreshed more than x days ago...") in the Power Query Editor is the last thing I tried before I noticed it was working again.

It's been over a year since the last update on this issue - please give it some attention, @v-cazheng-msft.