Dataverse link to Fabric. Choice fields not available

[MattBrennan]

Hi,

I’ve linked Dataverse tables to Fabric through Power Apps using the Link to Microsoft Fabric option under Analyze and can see the tables within the Lakehouse. When performing a query against one of the tables, I can see a difference, which appears to be the choice fields not being available in tables within the Lakehouse.

The example

Table: Opportunity

Field: Rating AKA oportunityratingcodename

If I analyse in Power BI the table and fields as I see them in Power Apps are the same and data values show correctly. There are some issues identified with a solution for display the values of these in Power Bi, however this is slightly different ( link

).

I could recreate these downstream from the Lakehouse using case statement or similar, but this is repetition and should a new rating be required a change in 2 places would occur.

If anyone has experienced this before and can either explain why this occurs or suggest a solution for surfacing those choice fields within the Lakehouse I’d greatly appreciate your input.

Thanks

Matt

[Hofpower]

Hi @MattBrennan 

I can relate to your topic. I also wondered that there is no out-of-the-box solution to easily dereference optionsets in the tables. Maybe I can help you with that topic - nevertheless be aware that I am not with MSFT and so this is no "official" information but my observations.

The optionsets are actually also synced to your lakehouse via the metadata tables (also pushed in delta format) OptionsetMetadata, GlobalOptionsetMetadata, StateMetadata and StatusMetadata. So it is possible to create views or some kind of ETL-Jobs (pipeline-activity, spark-notebook, sp in warehouse, ...) that join your data with the metadata tables and thus reconstruct the desired readable table with labels (which business users need in the end). So you don't actually need to use case statements that need to be maintained whenever a new option is possible but nevertheless such views etc. need to be created somehow. 

Since I didn't find a package to create such objects automatically I tried myself on it - so maybe check out my repo on this problem and feel free to try it out or contribute. Be aware that this is not well tested at the moment and still in a stage where I would not recommend a use in production. 

If you found any other solution for your problem that works for you feel free to share your approach. 

Best Regards
Martin

[MattBrennan]

The issue is currently under investigation by the team at Microsoft support. I will post an update once I receive one.

Matt

[Anonymous]

Hi @MattBrennan ,

Thanks for using Fabric Community. The best course of action is to open a support ticket and have our support team take a closer look at it.

Please reach out to our support team so they can do a more thorough investigation on why this it is happening: Link 

After creating a Support ticket please provide the ticket number as it would help us to track for more information.

Hope this helps. Please let us know if you have any other queries.

[Anonymous]

Hi @MattBrennan ,

We haven’t heard from you on the last response and was just checking back to see if you got a chance to open a support ticket.
After creating a Support ticket please provide the ticket number as it would help us to track for more information.

Thanks